Skip to main content
Korve deploys full-stack apps to your-app.korve.app with managed Postgres, object storage, logs, custom domains, and budgets out of the box — plus a platform agent that diagnoses failed deploys for you. It is built agents-first. Every capability ships on four surfaces that speak the same typed API, with identical permissions and identical behavior:
  1. API — https://api.korve.dev, described by a public spec at GET /v1/spec. See the API reference.
  2. CLI — the korve binary. Every API operation a key can call maps to exactly one command (a tested parity guarantee). See the CLI reference.
  3. MCP — https://mcp.korve.dev/mcp, two tools: search the API and execute code against it. See MCP setup.
  4. Dashboard — the convenience layer at korve.dev for the things humans prefer to click.
Anything you can click, an agent can call. If your agent can read this page, it can run your infrastructure — start with agent onboarding.

​
How Korve is built

  • Paid-only, usage-based. No free tier, no seats. You pay for what you run, metered against a public rate card to the cent, with a $5/month platform minimum credited against usage.
  • One spec, one enforcement point. Auth, roles, and billing gates are declared per operation and enforced once in the API layer. The dashboard, CLI, and MCP inherit identical behavior — there is no surface with secret extra powers.
  • Declarative when you want it. Describe projects, environment, and domains in a manifest and apply it. The platform reconciles and never deletes anything you didn’t ask it to.
  • Self-healing by default. Failed deploys can be diagnosed by the platform agent, which returns a structured cause and suggested fix.

​
Runtime classes

Every project picks one of two runtime classes at creation: See Deploys for what each class expects from your code.

​
Next steps