Run Rungate in 60 seconds.
Rungate is Apache 2.0 open source and production-deployable today. Clone the repo, bring your own storage, point your agents at it. No registration, no step limits, no waitlist.
Self-host today
Pick whichever matches your environment. All three produce a running Rungate instance with the admin API on the port you choose.
# Clone + run (repo URL provided after early-access onboarding)
git clone <rungate-repo-url>
cd rungate
cp .env.example .env
# Edit .env: set RUNGATE_MASTER_KEY (generate 32 bytes), RUNGATE_PORT, etc.
docker compose up -d
# Bootstrap the first admin token
docker compose exec rungate npx tsx src/cli.ts tokens create \
--name "bootstrap" --scope admin Full setup including persistent storage, Railway/Fly deployment, TLS configuration, and the multi-member auth flow is in the self-host guide. The security page covers production considerations — encryption, token handling, responsible disclosure.
Or skip the ops and use the managed cloud.
Same code as self-host, zero ops. Free tier: 500 steps/month, 30 days retention. Early-access customers grandfather to today’s pricing. Signup is either agent-driven (paste a prompt and the agent creates your account) or a plain email magic-link flow.
Before you write any agent code
If you’re a human evaluating Rungate, the fastest path is to hand the job to your agent. The agent-native reference at /agents has code examples in Python, TypeScript, and curl; an OpenAPI spec at /openapi.json; and a copy-to-clipboard evaluation prompt. Paste the prompt into your preferred agent tool and it will integrate and self-assess.
Enterprise or regulated environment?
Rungate supports self-hosted Enterprise deployments with a commercial license, SSO (SAML, OIDC), compliance export, custom retention, and a dedicated support channel backed by SLA. Compliance roadmap and security posture are on the security page.
Contact sales