1. Separate the services
The public Next.js marketing site receives demo requests. The separate UAgents application provides agent and organization APIs; execution depends on additional services.
- Marketing site: Next.js, optional PostgreSQL backup, Resend for requests.
- Application: Next.js 15, TypeScript, PostgreSQL/pgvector and configured identity.
- Runtime: separate agent execution, document-processing and scheduler/worker services as needed.
2. Prepare an environment
Use a dedicated development environment; do not reuse production secrets.
- Use Node.js and package-manager versions supported by the applicable repository.
- Provision the platform database and necessary extensions.
- Configure service URLs, credentials, storage and model-provider boundaries according to the platform source documentation.
3. Integrate safely
Avoid assuming an API route is a stable public contract before contract tests.
- Inspect the current API router, payload schema and authentication checks.
- Use tenant-scoped authorization and short-lived credentials where supported.
- Verify failure handling, retries, callbacks and audit records.
4. Verify production readiness
The reviewed platform disabled TypeScript/ESLint gating in its build configuration, and in-process schedulers are not reliable on ephemeral serverless workers.
- Run independent typechecking, linting, tests and the production build.
- Deploy background workers on durable infrastructure with explicit recovery controls.
- Review Docker executor privileges, tenancy, secrets and outbound connectivity.
Scope note: No API endpoint, SLA or security certification is promised by this guide. Validate the installed backend version and each deployed dependency before production use.