deploy-platform

Deploys an AgentOS platform to production using provider CLI scripts and verifies the live deployment.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/martin-cousseau/refund-arena --skill deploy-platform-martin-cousseau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-platform
Source: https://github.com/martin-cousseau/refund-arena/tree/main/backend/.agents/skills/deploy-platform
Command: npx skills add https://github.com/martin-cousseau/refund-arena --skill deploy-platform-martin-cousseau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Taking a locally-proven AgentOS platform to a live public URL involves many error-prone steps: provider authentication, environment configuration, JWT key setup, and post-deploy verification. This Skill orchestrates that entire deployment workflow so nothing is missed and no unauthenticated endpoint goes live. ## Core Features & Use Cases - Guided Deployment Workflow: Reads the deploy scripts and README, preflights the provider CLI and account, runs the up script, and handles first-deploy versus redeploy detection automatically. - JWT Security Setup: Walks through connecting os.agno.com Live, landing the JWT verification key, and syncing it so the platform boots with auth enabled. - Live Verification: Probes the public domain for /docs 200, /mcp 401 challenge, and /agents 401 to prove the deployment is secure before handover. - Use Case: You have an Agno AgentOS app running locally and want it live on a managed cloud provider with Postgres, a public domain, and token-based authorization, with clear redeploy, logs, and teardown instructions afterward. ## Quick Start Deploy this platform to production and verify it is live on its public URL.

Frequently Asked Questions about deploy-platform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an Agno AgentOS platform to production?▼

Run the deploy workflow which preflights the provider CLI, executes the up script to provision compute, Postgres, and a public domain, then completes the JWT key step and verifies the live URL. The skill detects first deploys versus redeploys automatically.

How do I redeploy an already live AgentOS deployment?▼

The workflow reads AGENTOS_URL from the production env and probes the domain; if it returns 200, it takes the redeploy path using redeploy.sh for code changes and env-sync.sh for config or secret changes, skipping the provisioning step.

Why does my AgentOS deployment fail to start on first deploy?▼

A keyless first deploy refusing to start is by design because auth is enabled and the app exits without a JWT verification key. Connect os.agno.com Live, copy the public key into JWT_VERIFICATION_KEY in .env.production, then run env-sync.sh.

How do I verify my deployed AgentOS platform is secure?▼

Probe the public domain: /docs should return 200, /mcp should return 401 with a WWW-Authenticate header, and /agents should return 401. A 200 on /mcp or /agents means the endpoint is open and must be fixed before handover.

Can I deploy AgentOS to my own Kubernetes cluster?▼

Yes, the owned-infrastructure mode supports deploying onto your own cluster. Set the JWT key before first boot, supply the public URL as AGENTOS_URL, and confirm the kubectl context points at the intended cluster before any mutation.