What this is: I'm the founder of a working AI SaaS platform (FastAPI/uvicorn backend, React/Vite frontend, deployed on AWS). The product pipeline is built and live! I need an experienced engineer to build the authentication, payments, and usage-entitlement layer that gates the product behind login and paid usage. You'll work against a runnable stub repository (real routes + data shapes, proprietary internals removed) - so you can build and test the full layer without ever touching the core IP, and afterwards - I will merge your work into the production app! Scope: • Auth (Clerk): signup/login, session lifecycle, backend session/JWT verification, inject a validated `user_id` into protected endpoints. • Payments (Stripe): Checkout for purchasing usage credits, plus a webhook that credits the user's ledger on successful payment. The webhook MUST be signature-verified, idempotent (Stripe retries-credit exactly once), and reconcilable (handle webhook-failed-but-payment-succeeded). • Entitlement ledger (the core): a credit balance per user with atomic check-and-decrement (two concurrent requests must never double-spend) on PostgreSQL. A `check_entitlement(user_id, ...)`gate that expensive endpoints call before doing paid work. • Server-side route gating: enforce entitlement on every paid endpoint (not just hidden in the UI); clean 401/402/403 responses. • Frontend integration (React): login/signup UI, buy-credits/checkout flow, balance display,graceful "out of credits" states, wired to the above. • Tests for the money-critical paths (webhook idempotency, atomic decrement, gating-bypass attempts). Stack you'll work with: Python 3.11, FastAPI, Pydantic, uvicorn (Linux). React + Vite, Tailwind. PostgreSQL. Clerk. Stripe. Who I'm looking for: Someone who has shipped this exact kind of system to production before. In your proposal, briefly tell me: 1. How you ensure Stripe webhook idempotency and handle reconciliation when a webhook fails but payment succeeded. 2. How you'd implement the atomic credit check-and-decrement so concurrent requests couldn't double-spend. 3. A relevant production system you've built (Stripe + auth + usage metering ideally). *I'd much rather a short, specific proposal - than a long generic one!* Working with me: I'm an engaged founder who genuinely enjoys building, and I want this to be a good experience for both of us! I'm responsive, communicate clearly, and I respect your expertise - because you're the specialist here,and I'm hiring you because you know this much better than I do! I'm not a micromanager and I'm not nitpicky - I just want the end results to be solid! I review in milestones, asking questions because I like understanding the work (not because I'm second-guessing you), and I make decisions quickly so you're never stuck waiting on me! The scope is already well-defined (detailed spec + a runnable stub repo on engagement), so you're not pricing around a vague, shifting target - it's a clean, bounded build. I care about getting the money-handling pieces right, and I'm betting you do too - if that resonates, I think we'll work well together! IP / engagement: A mutual NDA + IP-assignment (work-for-hire) before repo access. You build against stubs; you won't receive the proprietary pipeline. Work is milestone-based, fixed-bid preferred. To apply: Answer the three questions above + share 1-2 relevant examples, and ballpark your timeline and milestone structure (suggested: auth → payments+webhook → ledger+gating → frontend → tests/docs)!

Seeking a senior React Native engineer to improve performance of our eCommerce application containing 20,000+ machine parts. Current issues include: - Slow product list rendering - Search delays - Lag during scrolling - Occasional screen freezes - High memory consumption - Long initial app load times Tasks: - Analyze performance bottlenecks - Optimize FlatList and pagination - Improve API data handling - Optimize Redux state management - Reduce unnecessary component re-renders - Improve image loading performance This is a performance-focused project rather than new feature development. Required Experience: - React Native - TypeScript - React Profiler - Flipper - Redux Toolkit - Mobile app optimization

We are building an AI-powered hospitality assistant for full-service restaurants. The product helps guests find the right dishes, increases average check size automatically, and reduces pressure on staff during peak hours — all with zero hardware required. What we need: • Mobile-first web app — opens in the browser, no download required • AI conversation layer using OpenAI GPT-4o or Anthropic Claude API • Owner dashboard for menu management, daily priorities, and live order notifications • Multi-tenant architecture — each restaurant’s data is fully isolated • Real-time notifications between guest interface and staff • Multilingual support: English, Spanish, Arabic • Milestone-based payments with a functional demo at each stage • Full IP transfer on project completion Required: • Live web apps in your portfolio that are currently active • Hands-on experience with OpenAI or Anthropic APIs — name the project • Multi-tenant SaaS experience • Willingness to sign NDA and work-for-hire agreement before project start

# Job post — copy/paste into Upwork (or Contra/Fiverr Pro) **Title:** Launch a finished static website on Vercel + add Stripe/Tilopay payments and intake forms (small, well-defined project) **Category:** Web Development · Full Stack **Budget:** Fixed price, per milestone (see below) — please bid per milestone **Experience level:** Intermediate–Expert --- ## Description I have a **fully built and tested** magazine/advertising website for the Costa Rica travel market (TidesRight). The design and all 23 pages are DONE — built from a completed design prototype, verified working (all pages render, popups, search, filtering, and a 4-step advertiser signup wizard). The site is plain HTML/CSS/JavaScript (precompiled React, no build step required) sitting in a private GitHub repository, ready to serve as static files. I am not technical, so I need someone who communicates clearly and can own the plumbing end-to-end. A `DEVELOPER-BRIEF.md` in the repo explains the structure, and the repo also contains the full product specs (ad package pricing, form fields, approval flow). ### Milestone 0 — Go live (small, fast) - Fix/redo the Vercel project so the site serves from the repo's `main` branch (files are already at repo root; a fresh import should work with zero config — the current project got stuck on a bad first import) - Connect my custom domain - Confirm all pages load on desktop + mobile **Deliverable:** the site live on my domain. Est. a few hours. ### Milestone 1 — Real payments + advertiser intake (the core job) The site has an advertiser flow at `advertise.html` → `package.html`: package selection → payment → intake form → "submitted for approval" confirmation. Today the payment step is a demo (no real charge). Make it real, keeping the existing look: - Wire each package to real payments — **Stripe** (or **Tilopay** if we settle to a Costa Rica bank; advise me on the right choice for my situation). Packages: Standard $29/$79/$149 per month, Real Estate $99/$399/$899 per month (annual = 2 months free), plus a one-time SEO add-on from $49 - After successful payment, the advertiser fills the intake form (existing fields); submissions must be **saved** (database or a form service like Tally/Jotform) and **emailed to me** with the payment reference - I approve by replying/clicking; nothing goes live automatically - Failed/abandoned payments must not reach the form step **Deliverable:** I can watch a real test payment land and receive the intake submission. Est. 2–4 days. ### Milestone 2 (optional, later) — Admin dashboard Approval dashboard, auto-publish of approved ads, subscription management. Scope after M1 ships. ## What you get from me - Private GitHub repo access: finished site (`main`), full source + design-spec documents (`source` branch), `DEVELOPER-BRIEF.md` - Vercel account access (this project only), domain registrar access, and fast decisions ## Requirements - Shipped at least one real Stripe (or similar) payment integration — link me an example - Comfortable with static sites / vanilla JS (the site is precompiled React — no framework build needed; do NOT rebuild it) - Plain-English communication with a non-technical owner - Timezone overlap with Americas preferred ## To apply, answer these 3 questions 1. Link to a payment flow you built (live if possible). What did you use — Stripe Checkout, Payment Links, or custom? 2. For Milestone 1, would you recommend Stripe Payment Links + a form service, or a small custom backend? Why, in 3 sentences. 3. Your fixed price and turnaround for Milestone 0 and Milestone 1 separately. **Important:** the design is final. This job is plumbing (hosting, payments, forms, email) — not redesign, not a rebuild. Bids proposing to rebuild the site in another framework will be declined.

We're building a confidential, AI-native operating system for high-volume plaintiff-side litigation. This is not a generic legal chatbot. It's an operating system for litigation operations — and we already have a live law firm as the proving ground, a working visual prototype, a pitch deck, and a near-term demo deadline. We need a senior full-stack engineer who can take an existing prototype, schemas, prompts, and workflow package and turn it into a secure working demo, then a production-track MVP. The right person thinks like a product architect, engineer, and security operator at once — fast, but disciplined with confidential legal data. Required: React/Next.js, TypeScript, Node or Python/FastAPI, PostgreSQL, auth and role-based access control, OpenAI or comparable LLM APIs, structured JSON/schema outputs, secure file handling, PDF/export generation, GitHub workflows, and strong security discipline. Strong plus: Legaltech, plaintiff-side litigation, case management systems (Filevine, Litify, Clio, Salesforce, HighLevel), RAG/document extraction, audit logging, and SOC 2 / PII / regulated-data experience. Ground rules: NDA required. No public repos. No real client data in the demo — sanitized data only. No API keys in browser code. No external sharing or deployment without approval. First deliverable: A build-readiness report identifying what's mock, what's reusable, and what needs rebuilding, plus architecture, security risks, database plan, API integration path, and a 7–30 day build roadmap. The path: Paid 7-day build-readiness sprint → 30-day demo sprint → longer-term technical lead / founding engineer discussion. To apply, please include: A short note on why you're right for this project 2–3 relevant products you've built (links) GitHub or code samples, if available Your availability for a 7-day build-readiness sprint Your hourly rate, fixed sprint price, or contract-to-hire preference Remote acceptable. U.S.-based preferred; South Florida a plus.

Existing founder is looking for a full stack engineer to be the founding engineer at Socratix, an agentic AI powered data platform for sales teams connecting Zoom, Teams and other communication data together to drive insights and deals. Product is currently in MVP state and requires development to a SOC II production grade platform for early customers. Ideally, this role becomes full time as part of the founding team presenting to investors later in the year. Must have an understanding and appetite for startups and working in an unstructured environment with a build mentality. Part time is an option for Sr. experienced engineers who have the capacity to execute rapidly due to their experience. Equity and salary will be discussed. Founder is in NY, NJ, but open to locations. Remote role.

We are looking to do a new build of our patch bay label designer tool. Customers are currently able to pick their model of patch bay, add text labels, colorize, and group. They can then checkout and it creates print ready artwork for our team to produce. The UI is a bit clunky and there are some features we want to add such as an admin tool to add and edit labels. You can see the current tool here: https://create.traceaudio.com/

We're building a data-driven platform in the beauty/cosmetics space. We've already collected a very large volume of scraped product and brand data, and it's messy - inconsistent formats, duplicates, missing fields, mixed languages, and unreliable values. Your job is to turn that raw data into something clean and reliable, and to build the web application on top of it. This is not a quick gig. We're looking for someone to stay with us for roughly a year and grow with the product. What you'll be doing Building and maintaining a Next.js (App Router) front end and back end Designing and managing our Supabase setup (Postgres schema, RLS policies, auth, storage, edge functions) Cleaning, normalizing, and deduplicating large beauty datasets (this is a major part of the role) Building data pipelines to process and validate incoming scraped data Writing transformation/normalization logic (units, brand names, categories, ingredients, pricing, etc.) Setting up data-quality checks and monitoring Iterating on features with us as the product evolves You should have Strong production experience with Next.js and Supabase (please point to specific projects) Solid SQL/Postgres skills - not just ORMs Real experience cleaning and normalizing large, messy datasets (Python/pandas or similar is a plus) Comfort working with scraped data and all the inconsistencies it brings Good written English and reliable communication Ability to work independently and own your part of the product Nice to have Experience in e-commerce, catalog, or product-data projects Familiarity with data pipelines / ETL tooling Some ML/NLP experience for entity matching or text cleanup Budget We expect this to run around $4,000–$5,000 USD per month depending on experience and hours. This is a long-term commitment, so stability and quality matter more to us than the lowest rate. To apply, please include: Similar past work - links or short descriptions of Next.js + Supabase projects, and at least one data-cleaning/normalization project you've done. Your time zone and your typical available hours - we need to know there's reasonable overlap. Your expected monthly budget within the range above (or your rate if hourly). Applications that don't address all three points will not be considered. A short note on how you'd approach cleaning messy beauty product data is a big plus. We read every proposal carefully and respond quickly to strong candidates. Looking forward to working with you.

Forum Intelligence: Project Brief & Initial Rollout 1. Executive Summary & Objective Forum Intelligence is a beginning as a localized data retrieval, processing, and archiving system designed to scrape public municipal records and state legislative data for public oversight. The immediate objective is to build a functional, highly resilient prototype focused on the Tri-Cities region (Burbank, Glendale, and Pasadena, California). The system will autonomously ingest messy, unstructured municipal data (City Council meeting minutes, agendas, public notices, and legislative PDF text, recorded mp4), clean it, and make it fully searchable and queryable via a localized AI agentic framework. 2. Phase 1 Scope: The Tri-Cities Rollout Th engineer will be responsible for building two primary pillars: A. Resilient Scraper Bots • Target Ingestion: Monitor and pull data from Burbank, Glendale, and Pasadena municipal portals and California legislative feeds. • Data Types: Brittle HTML sites, heavily nested tables, public notices, legislative drafts, and massive unstructured PDF archives. • Requirements: The scraping architecture must be exceptionally robust, utilizing intelligent error handling, retry semantics, and pagination tracking to handle frequent municipal website layout changes without breaking the pipeline. B. Ingestion & Vector Pipeline • Parsing: Extracting clean text from poorly formatted documents and scanned PDFs. • Local RAG (Retrieval-Augmented Generation): Chunking and embedding the data locally into a vector database (e.g., pgvector, Chroma, or Milvus) to enable semantically accurate entity linking and contextual search. 3. Targeted Hardware Stack To ensure maximum data security, strict public oversight integrity, and predictable operational costs, Forum Intelligence is skipping commercial cloud APIs in favor of an on-premise, localized NVIDIA enterprise deployment. The production roadmap aligns precisely with the new computing patterns detailed in NVIDIA’s latest hardware roadmap: • Inference & Token Generation: Running local open-weight frontier models (e.g., Neotron 3 Ultra or Claude/Llama equivalents) optimized for reasoning and long-context tool use. • Compute & Orchestration: The backend infrastructure is architected around NVIDIA’s dedicated agentic architecture, utilizing high-instructions-per-clock (IPC) Vera CPUs paired with Vera Rubin GPUs. • Memory & Storage Processing: Utilizing NVIDIA’s unified memory fabric and data processing units (DPUs) for ultra-low latency context management, KV caching, and fast vector database retrieval. 4. Immediate Milestones for the Engineer 1. Architecture Design: Map out the database schema and local inference ingestion loop. 2. Tri-Cities Scraper Deployment: Write and deploy the initial automated bots for Burbank, Glendale, and Pasadena. 3. Local MVP Pipeline: Demonstrate a local RAG pipeline where a user can query the Tri-Cities scraped records and receive grounded answers with exact source attributions. The above was AI generated from months long conversations with Gemini. The goal is to prove the concept then roll out to LA County, state of CA, and then the country.

What Is Already Done Everything is built and ready. You are not designing or coding from scratch. You are deploying and connecting services. • 24 screens built in React — fully designed and coded • Complete Node.js backend server — all routes written • All payment logic written — just needs Square keys connected • AI agent integration written — just needs API key connected • Legal pages done — Privacy Policy and Terms of Service • App Store submission kit ready • Logo and brand assets ready • Developer notes with full instructions provided • Environment variables template with Square sandbox key pre-filled • All third party integration code provided with examples What I Need You To Do Website: • Push all code to private GitHub repository • Deploy React frontend to Vercel with my custom domain • Deploy Node.js backend to Railway • Set up Supabase database with all required tables • Connect Square API for all payment flows • Connect Google Sign In and Apple Sign In • Connect Daily.co for video calls • Connect Resend for email notifications • Connect Supabase Realtime for live messaging • Set up Expo push notifications • Set up Supabase Storage for file uploads • Test all Square payment flows in sandbox first • Switch to Square production after my approval • Get website fully live at my custom domain Mobile App: • Convert all 24 web screens to React Native using Expo • Test on both iPhone and Android • Submit to Apple App Store • Submit to Google Play Store Tech Stack • Frontend: React 18 • Mobile: React Native with Expo • Backend: Node.js with Express • Database: Supabase • Frontend hosting: Vercel • Backend hosting: Railway • Payments: Square API • AI: Anthropic Claude API • Video: Daily.co • Email: Resend • Auth: Google OAuth and Apple Sign In • Storage: Supabase Storage • Realtime: Supabase Realtime