Use ermahgerd to run your applications while the platform operator maintains the servers, runtime, and backing services. You manage your organizations, application code, data, team, and provider credentials.
The managed offering is currently an invitation-only private alpha for design partners. It runs in one region without automatic replication or failover. Plan for maintenance interruptions and keep independent copies of important application data. The published service measurements are operational signals, not a contractual uptime or latency commitment.
Accept your invitation
- Open the private invitation link sent to you by the operator. The email address is fixed by that invitation.
- Choose a display name and password, or sign in as the invited account if you already have one.
- Create your first organization. Each organization has its own members, resources, tokens, and usage allowances; new organizations start on Free.
An invitation from an organization owner joins that organization only. It does not grant permission to create organizations. Ask the operator for customer access if you also need to create your own.
Your starting points
| Destination | Use it for |
|---|---|
| Tenant console | Organizations, resources, team, tokens, usage, and application telemetry |
| Platform status | Platform-owned service health |
| Application guides | Wrangler deployment, bindings, and application behavior |
Use the Worker URL shown in the console to reach a deployed application. Copy your organization’s S3 endpoint from Data → Storage. These addresses are specific to your organization; another customer’s hostname is not a template you need to adapt manually.
Prepare to deploy
Create a read-write API token under Management → API tokens and copy the organization ID from its overview. Ask the operator for the deployment API connection supplied for your alpha account, then follow Connect Wrangler.
The current managed installation keeps its deployment API on a private listener. A console login and API token do not by themselves establish network access to it. Deployment connectivity is arranged with the operator during onboarding; there is no published, generally accessible Wrangler API hostname or Cloudflare OAuth login for this installation.
Manage your organization
Invite colleagues from Management → Team and send them the invitation link. Use Usage & limits to inspect allowances and usage. Organization owners can select Free or Standard; no billing is implemented. Platform support can adjust individual limits without changing your selected tier.
Open a Worker’s Observability tab for invocations, failures, HTTP or background activity, and logs. Provider costs for AI remain on your own OpenAI, Anthropic, or Fireworks account. See Use the console, Organizations and access, and Usage and quotas.
Domains and application access
The service supplies HTTPS URLs for your Workers and S3 endpoint. A new Worker hostname may take a short time to acquire its certificate after deployment. Custom domains are not currently supported; creating a CNAME does not create a Worker route or certificate.
Workers with an HTTP interface are public unless you configure Application Access or authentication in the application. The photo workflow illustrates this: protect the upload studio while leaving the gallery public. Your organization role does not grant platform administrator access.