Web application
An application runtime, stable URL, environment variables, request logs, metrics, and a project budget.
Recipes
These are transparent architecture recipes, not one-click mystery boxes. Each one maps the application and its optional infrastructure to resources you can inspect, plan, apply, and export.
Choose the smallest recipe that matches the workload. Data services are included only when the recipe declares them.
An application runtime, stable URL, environment variables, request logs, metrics, and a project budget.
A web runtime plus explicitly provisioned Postgres, recovery policy, database insights, and object storage.
A queue with either a signed push consumer or pull workers, retries, message delays, and dead-letter handling.
A timezone-aware cron job targeting a signed application path or queue, with run history and retries.
A pull-request application environment, inherited access rule, and optional data resources chosen by the project.
A project with scoped agent authorization, an operator thread, approval-gated actions, and retained evidence.
Start from an architecture that names its runtime, resources, region choices, and expected meters.
See which resources would be created or changed before applying the manifest to a project.
Continue in the dashboard, CLI, API, MCP, or exported infrastructure manifest using the same resource model.
Executable starters
Each source directory includes application code, tests, a validated manifest, and exact local and deployment commands. Nothing provisions until you inspect and apply the plan.
A runnable Bun app with App Auth, tenant-scoped Postgres rows, object storage, recovery policy, and a safe browser/server credential boundary.
korve deploy . --project full-stack-saasAn organization-only internal app with exact health output, daily maintenance evidence, and approval-gated operator workflows.
korve deploy . --project agent-operated-toolA signed push consumer with caller-stable idempotency, retries, dead-letter handling, and a timezone-aware cron targeting the queue.
korve deploy . --project queue-cron-worker