Deploy to your Cloudflare account

Flary deploys into your Cloudflare account. You own the Worker, Durable Objects, D1 databases, R2 buckets, Queues, secrets, and stored data. Workers run the code; Durable Objects keep live state; D1, R2, and Queues provide storage and background work.

Hosted installer status

The browser installer is planned and is not in the current release. Use the CLI below. It signs in through Wrangler OAuth and deploys to the account you select.

Normal deployment

npx flary deploy

The command performs these steps:

1. Verify Wrangler OAuth and account access.
2. Build the project and generate the final Wrangler configuration.
3. Let Wrangler provision binding-only D1 and R2 resources and named Queues.
4. Upload required secrets from a temporary mode-0600 file.
5. Apply dashboard D1 migrations when the project is a dashboard.
6. Deploy and check /health and the dashboard setup route.
7. For a personal backend with a provider, call the example function with its generated bearer token.

For a generated agent backend, the same deployment can serve the typed API and the optional /widget.js Web Component. For a dashboard, it serves the ready React/WebSocket console. Flary Mail also provisions the mail resources described in the Quickstart.

The temporary secret file is always removed. Repeated setup and deployment reuse stable Worker and resource names. Setup never deletes a Worker, database, bucket, queue, credential, archive, or thread.

Check a project

npx flary doctor

Doctor checks Node, the package manager, Wrangler authentication, account selection, local required secrets, generated bindings, the dashboard migration file, optional Docker support, and deployed health when a URL is known.

Optional resources

Browser Run is added only when app.browser() is registered. Sandbox is added only when app.sandbox() is registered. Sandbox also needs a running Docker-compatible builder and a paid Workers plan.

If automatic provisioning is not supported by the selected account or plan, Wrangler reports the resource. Create only that resource manually, keep its binding name, and run flary deploy again.

Account and provider ownership

Cloudflare OAuth authorizes the account that owns the deployment. Google Gemini, OpenAI, and Anthropic API keys are BYOK secrets. Workers AI uses the connected Cloudflare account. The dashboard can authorize OpenAI Codex or Anthropic Claude subscriptions through provider OAuth; it stores those credentials in encrypted storage and uses them only when a trusted resolver selects the connection. See Providers and connections for the provider and MCP flows.