✦ Cloud for agent-built apps

Build it with an agent. Share it like a document.

Give your agent one typed API for the app and its infrastructure. Korve turns the result into a live URL with deploys, data, logs, and spend controls in one place.

Ship an app

acme-api — korve

One app, one control plane

The runtime and primitives stay together

Deploy the app, then add only the managed data and operations primitives it actually needs.

Code to a live URL

A deploy builds, releases, and routes your app to a stable korve.app URL. Connect a repo to ship every production push.

Managed Postgres

Provision the databases your app needs, in the environment and region you choose. Each credential is revealed once and stays isolated to that resource.

Object storage

Provision project-scoped or organization-shared buckets with signed uploads and downloads.

Logs & metrics

Structured logs, request metrics, filtering, and manual refresh in the same project workspace.

Budgets & spend guardrails

Set a monthly budget per project. A hard stop refuses new deploys past the limit while running workloads keep serving; without it, the budget alerts instead.

Custom domains

Point your domain at any project; certificates issue and renew automatically.

Agent-native

One contract your agent can actually operate

Claude Code, Codex, and Cursor can use the same typed operations through the dashboard, Rust CLI, API, MCP, and infrastructure as code. Discover once, automate without scraping.

One typed API, spec-first

Every capability is a typed endpoint with a published spec. Dashboard, CLI, and agents all call the same contract.

The korve CLI

Deploy, query logs, manage env vars, and check budgets from any shell — scriptable by you or by an agent.

MCP server built in

Connect your agent and it can deploy, diagnose, and fix projects directly — no scraping, no human glue.

korve.yamlInfrastructure as code

version: 1
organization: acme
projects:
  - name: Acme API
    slug: acme-api
    runtimeClass: scale-to-zero
    git: { repo: acme/api, ref: main }
    databases:
    - { name: primary, sku: db-s1, region: us-east }
    storage:
    - { name: uploads, region: enam }
    domains:
    - api.acme.com

✦ Platform agent

Failures come with a next step, not just a stack trace.

When a deploy fails, the platform agent reads the build, logs, and project state — then explains what broke and proposes a concrete next step.

deploy dpl_8f2a · acme-apifailed

✦ Diagnosis

Migration 0042_add_orders ran before 0041_create_users created the table it references. Reordering the migrations resolves the deploy.

- 0042_add_orders.sql

+ 0041_create_users.sql

+ 0042_add_orders.sql

✦ Review suggested fixOpen logs

Pricing

Usage-based, to the cent

$5/mo minimum, credited against usage. No seats, no tiers — every meter is public.

See the full rate card

$0.042/ hour

Always-on compute

Shared 1 vCPU / 2 GB, billed by the hour

$0.9/ million requests

Scale-to-zero

Runtime idles to $0; declared data resources bill separately

$0.06/ GB

Egress

Flat per-GB transfer out, no tiers

Give your agent a cloud it can operate.

Ship an app

No free tier. No seats. Pay for what you run.