Operate AOS Hub
AOS Hub hosts AOS package registries and binary caches. It provides a web console for people, an HTTP API for automation, and the Git- and Nix-compatible surfaces consumed by AOS tools.
The same application is available in two forms:
| Deployment | State | Storage | Best fit |
|---|---|---|---|
| Native server | Local SQLite | Local filesystem or S3-compatible storage | AOS systems, private infrastructure, and deployments where you operate the host |
| Cloudflare Worker | SQLite in a Durable Object | R2, with KV as a session/hot-state cache | Cloudflare-operated deployment with edge-cached assets and public facade reads |
Both forms serve the web interface, HTTP API, registry facade, and managed
publish path. Native deployments also expose direct database
administration through aos-hub. Worker deployments are administered through
the web/API surface and the aos-hub worker deployment commands.
The Worker does not make every Hub request edge-local. Static assets and
cacheable public facade reads can be served at the edge. Other requests run in
resource-affine control, tenant, registry, or cache execution objects; those
objects send only short transactions to the single authoritative HubDb
SQLite object. Cross-resource constraints remain atomic, while request parsing,
response construction, and provider I/O no longer serialize behind unrelated
resources.
#Start here
- Run a local Hub creates a signed demo registry and gets a working server on localhost.
- Use the web interface covers browsing, sign-in, and the management console.
- Set up a delivery destination connects existing CDN and storage infrastructure through reviewed setup, verification, and activation.
- Use the API covers transport, authentication, and stable endpoint patterns.
- Choose the right CLI distinguishes local operator commands from the remote API client.
- Trust an internal AOS Hub deployment defines signing authority, client bootstrap, hosted-key tradeoffs, access boundaries, and recovery.
- Operate an AOS package registry covers producer keys, releases, uploads, channels, and incident response.
- Deploy the native server covers initialization, service configuration, storage, backup, and monitoring.
- Operate AOS Hub in production covers topology, TLS, identity, recovery, storage retention, monitoring, upgrades, and incidents.
- Deploy to Cloudflare covers the packaged installer, resources, secrets, updates, domains, email, and observability.