Skip to main content

​
Deployment

​
Application deployment

The app is designed for Vercel with pnpm build as the production build command.

​
App checklist

  1. Set every canonical environment variable from Environment Variables.
  2. Confirm the deployed contract addresses in lib/constants.ts and the NEXT_PUBLIC_* contract variables match.
  3. Verify Supabase service credentials are present for protected API routes and realtime reads.
  4. Verify Bridge keys and webhook secret are set before enabling employee KYC, card, or off-ramp flows.
  5. Verify REMLO_AGENT_PRIVATE_KEY and MPP_SECRET_KEY before enabling machine-paid write flows.

​
Post-deploy checks

SurfaceWhat to verify
Public site/, /pricing, /docs, /about, /contact, /press, /status, /legal/terms, /legal/privacy
Auth/login, /register, /invite/[token], /kyc/[token]
Employer app/dashboard, /dashboard/team, /dashboard/payroll/new, /dashboard/treasury, /dashboard/treasury/deposit, /dashboard/cards, /dashboard/settings, /dashboard/api-access, /dashboard/demo
Employee app/portal, /portal/payments, /portal/card, /portal/card/activate, /portal/wallet, /portal/settings, /portal/settings/offramp
Admin app/admin, /admin/employers, /admin/compliance, /admin/monitoring
MPPConfirm 402 challenges and successful receipts on the twelve endpoints
WebhooksConfirm Bridge and Tempo webhook signatures verify correctly

​
Mintlify deployment

Mintlify uses docs.json as the site configuration file. In this repository, docs.json stays at the repo root while the MDX pages and docs-only SVG assets live under the docs/ directory.

​
How Mintlify should be wired

  1. Connect the repository to Mintlify through the Mintlify GitHub app.
  2. Keep docs.json in the repository root. Mintlify reads it as the site blueprint.
  3. Keep the docs pages, reference content, and docs brand assets under docs/.
  4. Push changes to the connected branch. Mintlify rebuilds the docs site from the committed MDX files.
  5. Use preview deployments for branch review when you need layout or copy approval before merge.

​
What this docs bundle includes

  • Product overview and system architecture
  • Full route inventory for public, auth, employer, and employee pages
  • Internal REST API reference
  • Full MPP endpoint reference
  • Webhook and demo-agent reference
  • Contract, Bridge, Privy, and environment documentation

​
Contract deployment

The Foundry scripts in contracts/ target Tempo Moderato. The current deployed addresses baked into lib/constants.ts are documented again in Contracts.

​
Suggested release gate

Do not call the deployment complete until all of the following are true:
  1. pnpm build passes.
  2. pnpm exec tsc --noEmit passes.
  3. The public legal pages resolve without an auth redirect.
  4. The login screen links for Terms and Privacy resolve to the correct public pages.
  5. The MPP pricing page matches the backend charges.
  6. The Bridge and Tempo webhooks accept signed requests in the deployed environment.