AI Prototype to Production Developer

An AI-powered conflict-resolution platform is looking for an experienced Node.js/Express developer to productionize our working prototype (Claude API integration already built). Scope includes migrating SQLite to Supabase/PostgreSQL, implementing auth and Stripe pay-as-you-go billing, building an admin panel, and setting up CI/CD on Render - all while keeping our proprietary methodology and API keys strictly server-side. This is a 2–4 week, NDA-protected engagement; all code and deliverables are work-for-hire. Full scope is as below: Context: Shanti AI is an AI-powered conflict-resolution platform grounded in a proprietary methodology. A fully working Node.js/Express prototype exists with Anthropic API integration. The developer’s job is to extend and productionize this codebase and not rebuild it. Tech Stack: Backend: Node.js v22+ with Express Database: Supabase / PostgreSQL: migration from existing SQLite Frontend: Vanilla HTML / CSS / JavaScript (React acceptable for admin UI only) AI / LLM: Anthropic Claude API: claude-sonnet-4-6/5.0; server-side proxy only Payments: Stripe (global): pay-as-you-go token wallet model Hosting: Render, the existing render yaml blueprint must be used CI/CD: GitHub Actions: push-to-deploy with staging environment Email: Production SMTP provider: SendGrid, Postmark, or AWS SES Secrets: Environment variables only: never in client code, git history, or logs Architecture principle: The Anthropic API key and the UCRF master prompt must remain server-side at all times. The frontend must never hold, proxy, or display these. SCOPE: 1. User-facing application • Migrate data layer to Supabase/PostgreSQL, preserving all existing schema, logic, and case ledger without data loss. • Implement email-verified registration and login, registration form, email verification link, login, session persistence (30-day), and an auth-gate modal that preserves the user’s query on login. • Harden the existing backend: rate limiting on all API endpoints, input sanitization, structured server-side logging (no conflict content in logs), and error handling that never leaks stack traces to the client. • Wire Stripe pay-as-you-go billing: new users receive a free credit balance on registration (equivalent to 5USD roughly); tokens for each call are counted, multiplied by a configurable markup rate, and deducted from the user’s balance in real time. • Build the top-up flow: when a user’s balance falls below a threshold, show a blocking prompt with a Stripe Checkout link; on successful payment, credit the balance immediately via Stripe webhook. • Display the user’s remaining balance and per-query cost estimate on the chat interface so users understand their consumption transparently. • Preserve and extend all existing features: 7-phase UCRF pipeline with streaming, web search tool loop, multilingual support, voice-to-text input, PDF export, and thumbs-up/down feedback widget. Admin panel • Admin login: a separate, password-protected admin route inaccessible to regular users. • User management: searchable user list showing email, registration date, current balance, total spend, and query count; ability to adjust balance, suspend, or delete a user. • Financial dashboard: total revenue, total token cost, gross margin, and a per-user financial history (top-ups, deductions, dates). • Usage analytics: daily active users, queries per day, conflict domain distribution (interpersonal/organizational/geopolitical), average session length, and feedback rating breakdown. • Chat audit: read-only access to any user’s session transcripts for quality review (conflict content is not stored beyond the session; only session metadata is accessible). Infrastructure and delivery • Set up staging and production environments on Render from the existing render.yaml blueprint; staging environment must be live and accessible to the founder. • Configure GitHub Actions CI/CD pipeline: automated linting, tests, and deploy-on-merge to staging; manual promote-to-production step. • Provide a production SMTP transactional email setup (SendGrid, Postmark, or AWS SES) with email templates for verification, welcome, and low-balance alert. Stripe billing model detail The billing model is pay-as-you-go (token wallet), not a subscription. No monthly plans at this stage. Token counting: Token for Anthropic API per call, accumulated server-side per user Cost calculation: Tokens used × cost-per-token × configurable markup multiplier (set in admin panel) Free credit on signup: Configurable amount (e.g. equivalent to USD5 queries) applied automatically on registration Top-up flow: User tops up via Stripe Checkout in preset amounts (minimum USD10); balance credited on webhook confirmation Low-balance gate: Before each query, check balance. If below threshold, block the request and show a top-up prompt Stripe gateway: Stripe only; EU/US/global. IP protection and engagement terms • NDA + IP Assignment Agreement. • All code, documentation, and deliverables are work-for-hire and the sole property of Pramod Bhatt / Shanti AI. The developer acquires no rights to any deliverable. • The UCRF master prompt and framework materials will be shared after NDA signing, on a need-to-know basis only. They must never appear in client-side code, logs, or git history. • Conflict content submitted by users is sensitive personal data. It must not be stored beyond the active session. Only session metadata (timestamps, token counts, feedback ratings) may be persisted. • Developer must confirm in writing that they will not use Shanti’s codebase, master prompt, or UCRF frameworks in any other product or engagement. • The Render account and Supabase project must be registered under the founder’s credentials from Day 1. The developer is granted only contributor access. Timeline: 2 to 4 weeks What will be provided • Full Node.js / Express source code, README, and architecture flow diagram (under NDA). • Anthropic API account and key (server-side use only). • Domain registrar and DNS access for shanti.ai. • SMTP / email provider credentials or budget to configure a new account. • The proprietary framework materials (under NDA, for integration reference only). • Single point of contact for all decisions, with prompt feedback on pull requests and staging demos.