These guides apply to an organization on either managed ermahgerd or your own installation. You need an organization, permission to deploy, and a reachable deployment API. Start with Connect Wrangler.
Your first Worker
Deploy Workers covers code uploads, versions, rollback, secrets, and outbound connections. Use the console shows where to find resources and inspect a deployment. Application code enters through Wrangler; console pages help manage resources and running versions.
Add capabilities
| Need | Guide |
|---|---|
| Your own application hostname | Custom domains |
| Named state, SQL, alarms, RPC, or WebSockets | Durable Objects |
| Recurring background work | Schedules |
| Files, archives, and S3 access | Object storage |
| Relational queries and migrations | Databases |
| Small configuration values with expiration | Key-value |
| A static site or bundled frontend | Static assets |
| Asynchronous jobs and retries | Queues |
| Image renditions | Images |
| Your own inference provider and vector indexes | AI and vector search |
Run and manage applications
Use Worker observability to investigate traffic, background events, errors, and logs. Usage and quotas explains what consumes an allowance and what happens when a limit is reached. Organizations and access covers teams and API tokens. Application Access protects selected Worker hostnames with login and policy.
Copy resource IDs, Worker URLs, and S3 endpoints from your organization’s
console. Example names such as my-worker and media-assets are names you can
choose; they do not identify pre-existing resources in your account.
For account onboarding, return to Managed ermahgerd. To install the platform itself, use Self-hosting.