Choose infrastructure
Choose a provider preset or connect Hot Updater to your existing backend.
Choose your infrastructure
Choose where your OTA metadata, bundles, and update server will run. Start with an account your team already operates. An agent can inspect the app and existing resources before asking for an unresolved provider or deployment target.
Hot Updater's provider presets provision resources in your cloud account. You own those resources. A custom server lets you compose the database, storage, framework and hosting in an existing backend.
Choose a path
| Path | Resources | Use it when | Catalog delivery |
|---|---|---|---|
| Cloudflare | D1, R2, Worker | You want the supplied Worker deployment or already use Cloudflare. | Shared cache in front of Worker execution. |
| Supabase | Postgres, Storage, Edge Function | You want the supplied Supabase deployment or already operate a Supabase project. | Direct Edge Function URL; each check invokes the Function. |
| Firebase | Firestore, Storage, Function | You want the supplied Firebase deployment or already operate a Firebase project. | Direct Function URL; each check invokes the Function. |
| AWS | DynamoDB, S3, Lambda@Edge, CloudFront | You want the supplied AWS deployment and use AWS accounts and IAM. | CloudFront shared catalog cache. |
| Custom server | Your database, storage and host | You need to use your own ORM, server framework or deployment process. | Depends on your hosting and cache configuration. |
All paths use the same Release Catalog protocol. A provider preset runs the official server plugins, Insights, API keys, and Remote Config; a custom server runs the ones you choose. Shared cache behavior differs by provider; a successful origin-only deployment does not imply a shared CDN cache hit. Each provider guide documents its resource, access and operating requirements.
Set up a provider preset
- Install packages, including your app's build adapter and the chosen provider package.
- Open the provider guide above and choose AI agent or Terminal. An agent discovers or creates resources; interactive init walks you through the provider's supported choices.
- Record the verified client base URL and the location of the client API key. Continue with Set up your app.
- Test an OTA update in a release build and verify the changed code runs after restart.
For an agent-assisted setup, install the Hot Updater skill and ask it to inspect the project, prepare the chosen provider, wire the app, and complete that verification. Account login, missing access, billing activation and unresolved deployment choices may need your input. Resource IDs and settings that the agent can inspect are part of setup work.
Use an existing backend
Follow the custom-server quick start for one complete Hono, SQLite and R2 example, or use the custom-server overview to select the adapter, framework and host that fit your stack.
A custom server requires schema setup, an explicit client access policy and
protected admin routes. Its CLI connection uses standaloneRepository, and
lists the server's plugins; the server itself uses a direct database adapter.
Storage and database adapters can be selected independently; see
Adapters and Plugins.
Add operations after the first update
The Console is a separate operator interface. After the app successfully receives an update, use the Console guide for local management or host the Console with the same provider resources. For a signed deployment, configure bundle signing before building the native app that will verify those signatures.