> ## Documentation Index
> Fetch the complete documentation index at: https://unkey.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Unkey is two separate products. Compute builds, deploys, and runs apps behind a gateway. API Management issues API keys, enforces rate limits, manages identities and permissions, and reports usage. Say which product a page belongs to; a reader can use either without the other.
> Every Unkey API endpoint is an HTTP POST to https://api.unkey.com/v2/{service}.{procedure} with a root key in the Authorization: Bearer header. Root keys are workspace scoped.
> Error codes have the form err:{system}:{category}:{specific} and each has a page at /errors/{system}/{category}/{specific}.
> The word environment means production or preview in Compute. Rate limiting has four meanings on this site; the glossary lists them.
# Compute
> Build, deploy, and run your app on Unkey, with or without API Management.
export const ProductLink = ({product, href, title, children}) => {
const productNames = {
compute: "Compute",
"api-management": "API Management",
platform: "Platform"
};
return
;
};
Compute takes a GitHub repository or a container image and turns it into a running app. You get a production and a preview environment, automatic domains, promote and rollback, and a gateway in front of every deployment.
## Get started
Connect a repository and let every push deploy.
Ship an image you built yourself, from the dashboard or the CLI.
What you need before you can deploy, and what each plan allows.
## Concepts
How projects, apps, and environments nest.
The thirteen lifecycle statuses, the build queue, and why a deployment fails.
Promote, roll back, stop, wake, and what happens on a timer.
Replicas, resource limits, health probes, and the autoscaler.
How regions are chosen, capped, and used for readiness and failover.
## Build
Automatic builds or your Dockerfile, the build queue, caching, failures.
Build context, the runtime contract, and the errors Unkey explains.
Use environment variables during the build without baking them in.
Install, connect, branch mapping, fork approval, and what Unkey writes back.
## Configure
Dockerfile, root directory, build command, watch paths, auto deploy.
Port, CPU, memory, disk, command, protocol, regions, replicas.
The probe that gates traffic and restarts unhealthy instances.
Kinds, limits, import, and the variables Unkey injects.
Per-instance and workspace ceilings, per plan.
Alerts and an optional stop on monthly usage spend.
The official SDKs wrap the whole Unkey API, so projects, apps, environments, deployments, domains, gateway policies, and the GitHub install flow are reachable from the same client you use for keys.