Orunbase-managed Cloudflare
Orunbase-managed Cloudflare gives your account a real Cloudflare account that Orunbase owns and runs. There is nothing to sign up for and no token to paste. Baselines deploy to it exactly as they deploy to your own Cloudflare account, and your Workers serve on its workers.dev subdomain, named after the workspace that connected it: a workspace called lumen-pay serves on lumen-pay.workers.dev. If Cloudflare already has that name, a short suffix is added (lumen-pay-x7k2.workers.dev). A brand-new name can take a few minutes before it serves.
Each managed account belongs to one Orunbase account only. It is never shared with another customer.
Use it
- When you build a baseline: in Build with, choose Orunbase-managed Cloudflare, then Use it. The new connection is picked for that build.
- From Integrations → Cloudflare: the connect dialog shows the managed choice first, then the option to use your own account.
Your own Cloudflare connection stays the default wherever you have one, because a managed account costs credits.
Your plan sets how many managed accounts you can hold: Free 1, Pro 2, Business 5, Enterprise unlimited.
What it costs
A managed account is paid for in credits:
| Credits | |
|---|---|
| Each day the account is yours | 33 |
| Each million Workers requests beyond 10 million a month | 60 |
| Each million CPU-milliseconds beyond 30 million a month | 2 |
The first 10 million requests and 30 million CPU-milliseconds each month are included in the daily fee. Usage is measured every hour. It appears in your credit history as Managed Cloudflare, and on the connection's page as Credits this month.
The monthly cap
On the connection's Overview tab you can set a monthly cap in credits. When this month's credits reach it, the account pauses until the month turns, or until you raise or remove the cap.
For their first week, new managed accounts are also limited to 500 credits, unless your account is on a paid plan. Paid plans have no first-week limit.
When an account pauses
A managed account pauses when:
- your account runs out of credits;
- it reaches your monthly cap, or the first-week limit (without a paid plan);
- Orunbase support pauses it, for example after an abuse report.
While it is paused, your Workers' workers.dev and preview URLs are turned off, custom domains and routes are detached, their cron schedules stop, and nothing new can deploy. Nothing is deleted.
It serves again within two minutes of the reason going away: credits added, the cap raised, a move to a paid plan (for the first-week limit), or the month turning. A support pause is lifted by support.
Disconnecting
Disconnecting gives the Cloudflare account back to Orunbase. A day later it is emptied. Every Worker, custom domain, domain, Pages project, D1 database, KV namespace, Hyperdrive config, R2 bucket and token in it is deleted, and its workers.dev URLs stop working. Copy anything you need before you disconnect, or ask support for an export.
Custom domains
To serve on your own domain, open the connection's Overview tab and add the domain under Custom domains, for example example.com. Orunbase adds it to your managed account and shows the two Cloudflare name servers to set at your registrar.
Once your registrar points at them, the domain is active. From then on, Workers custom domains and DNS edits (the dns-edit template) work on it as they do on your own Cloudflare account.
A managed account can hold up to 5 domains. Removing a domain deletes it, and its DNS records, from the account.
While the account is paused, your custom domains and routes are detached too. They are put back when it serves again.
Not included
- A Cloudflare dashboard login. You work with the account through Orunbase.