Deploy the Platform on Render

Help the user deploy their application through the Render dashboard. Prepare the repository, guide the Blueprint setup, and verify the authenticated application. Read AGENTS.md, render.yaml, and the application's settings. Use the current Render Blueprint docs when dashboard details are uncertain.

1. Prepare the GitHub repository

Inspect the Git remotes, branch, and application changes. Reuse the user's repository if one exists. Otherwise, establish the GitHub owner, repository name, and visibility, then help create it using the available GitHub integration or gh repo create. Use a private repository unless the user wants it public.

Preserve the template remote as upstream when making the user's repository origin. Review the files to publish, exclude credentials and local artifacts, commit the application, and push the intended deployment branch. Verify that the pushed branch includes the user's agents, Dockerfile, and root render.yaml. Help the user grant Render's GitHub connection access to this repository. The Blueprint creates an AgentOS project and Production environment. Set projects[0].name to the user's application name before pushing if they want a different project name.

2. Deploy the Blueprint

Identify the intended Render workspace and any existing deployment. Reuse its Blueprint, API service, and database when present; continue to configuration below. For a new deployment, guide the user through Render:

1. Choose New → Blueprint and connect their GitHub repository.
2. Select the deployment branch and root render.yaml.
3. Enter OPENAI_API_KEY and set RUNTIME_ENV to dev for initial setup.
4. Review the resources and billing, then choose Deploy Blueprint.
5. Wait for the API to become live and copy its public HTTPS URL.

Start with the Blueprint's one always-on API instance with 1 CPU and 2 GB RAM (1c-2g) and PostgreSQL 18 database. Confirm both use Virginia (region: virginia) before deploying. Preserve the database references. Initial setup runs without authentication; continue directly to securing the application below. For an existing secured deployment, keep RUNTIME_ENV=prd.

3. Configure access

At os.agno.com, create a Live connection using the Render URL. In Settings → OS Security, enable Token-Based Authorization (JWT) and copy the public verification key.

In the Render API service's Environment settings, configure:

Have the user enter secrets directly in Render. Preserve existing working settings, including JWT_JWKS_FILE when used for verification. Choose Save, rebuild, and deploy, inspect startup logs, and verify the AgentOS connection once the API is healthy. RUNTIME_ENV uses sync: false, so later Blueprint syncs preserve its dashboard value.

For browser MCP access, set MCP_CONNECT_SECRET to a securely generated random secret, save and deploy, then connect the client to <AGENTOS_URL>/mcp. The user enters that secret on the consent page. Preserve an existing secret during updates and never print credentials. Coding clients can use uvx agno connect --url <AGENTOS_URL>.

4. Verify the application

Complete setup only after the production redeploy passes these checks:

• RUNTIME_ENV=prd is deployed, /health succeeds, and /docs loads.
• /agents rejects unauthenticated requests; an authenticated request succeeds within the user's permissions, and the AgentOS UI connects.
• If MCP is configured, an unauthenticated initialization POST rejects access and the intended client connects with authentication. A plain GET /mcp is not an auth test.

Production has its own database. Ingest any required documents there before testing knowledge-dependent agents. Claim success only for behavior actually verified.

5. Confirm the project and hand over

Open the project created by the Blueprint and verify that its Production environment contains both the API service and PostgreSQL database. The Blueprint manages the project, environment, and resources together.

Hand over the live URL, project/environment, Blueprint link, and verification results so the user knows where to manage the application.

Updating the application

Push code to the connected branch and check the resulting deploy. If auto-deploy is disabled, choose Manual Deploy → Deploy latest commit. Edit production settings in Environment and save and deploy. Keep infrastructure changes in render.yaml; Blueprint sync can overwrite conflicting dashboard settings. Preserve the database and saved application state during updates.

When requested, follow sandboxes for hosted coding agent execution and durable checkpoints, or scaling for replicas.