Cloud Console Built and live
Cloud Console is a small shared service like Google Cloud Tasks and Cloud Scheduler, on Cloudflare's free plan, with no card on the account. A project puts HTTP tasks into named queues and runs jobs on a schedule. The console calls each target URL, retries what fails, and logs every failed attempt.
FlowDeck runs on it: its timers and background work are tasks and scheduled jobs here. Any other project can use it the same way, with its own queues, jobs, keys and secrets.
Project info: six documents
Each for a different reader; Project info says which to read first.
Runs as
One Worker
Scheduled by
One cron trigger, every minute
Durable Objects
One per queue, one per job
Console pages
24
It all runs on Workers Free: one Worker, one D1 database, SQLite-backed Durable Objects, static assets for the pages, and one cron trigger. The pages are served without running the Worker. The Durable Objects' free limits that the budget counts on (about 100,000 requests and 13,000 GB-s a day, and 5 GB stored) are not confirmed: nobody has checked them against Cloudflare yet.
Who uses it, and how
People, on the console pages
They sign in, then work in each project as far as their permissions allow.
- They come in only when an admin invites them. There is no public sign-up.
- They sign in with Google. A passkey works too, for 30 days after a sign-in with Google or the password. One break-glass admin signs in with a password and an authenticator code instead of Google.
- Admins may do everything. A member gets permissions per project, ticked one by one: read, create, update, delete, pause, run, keys and secrets. The Viewer, Editor and Manager presets only tick the boxes.
- Queues and jobs are made and changed only here, never in an app's code.
Apps, with an API key
An app calls /v1 with its project's API key, Authorization: Bearer cck_....
- A key belongs to one project and reaches only that project. It is shown once, kept only as a keyed hash, and can be revoked.
- With it an app creates, reads and deletes tasks, and turns its project's maintenance switch on or off.
- FlowDeck adds its tasks this way. When the console refuses one (over the daily quota, say), FlowDeck runs the job itself; a task with a delay is logged and dropped instead.
The main parts
| Part | What it does | Where on the console |
|---|---|---|
| Task queues | Named queues of HTTP tasks, each with a rate, a limit on calls at once, and retry settings. A task is any method to a public http or https URL, with headers, a body and an auth header, and may wait up to 30 days. Failed tasks stay 7 days to be retried, and their attempts can be inspected. | Queues, the Queue page, Create a task |
| Scheduled jobs | A unix-cron schedule in a time zone. A job calls a URL or adds a task to a queue, with its own retries, an attempt deadline, and a rule for a run that is still going when the next is due. | Jobs, the Job page, Create a job |
| Uptime checks | A job of its own kind: a GET or HEAD on a schedule that expects a status range (200 to 399 by default), at most a set latency, and optionally a text in the answer. It keeps its last 100 results and shows uptime for 24 hours and 7 days. | Jobs, the Job page's Results |
| Alerts | By email and to a Google Chat webhook: a task failed for good, a job or check failing and then recovered, a queue's backlog. At most one of a kind per queue or job every 10 minutes. A project's quiet hours can hold them until the window ends. | Alerts |
| Quotas | Each project's task creations, job runs and retries are capped per UTC day: 5,000 by default, up to 1,000,000, or off. Near a free-plan limit (80%) low-priority queues are held and the admins alerted; over it, every queue is held and new tasks and runs are refused until the next UTC day. | Usage |
| Maintenance | A switch per project and one for the whole console, for a deploy or a migration. While one is on, tasks are still accepted and wait, and scheduled runs are skipped and logged. Every page shows a banner. | Projects; an app can switch its own project with its key |
| Backups | Once a day the console's D1 database is dumped, sealed, signed and uploaded to a B2 bucket that keeps each file 29 days. The admins are mailed when a backup fails or the newest is over 26 hours old. | Usage, Backups (admins) |
| Export and import | A project's settings as one JSON file: queues, jobs, alerts, the quota, and secrets and service accounts by name only. An import is previewed first; it makes and changes, and never deletes. A sample file can be downloaded. | Export and import |
| Tasks from a file | Up to 50 tasks into a queue from one JSON file, all checked before any is made, in one request. A sample file can be downloaded. | Create a task, From a file |
Also on the console: the Dashboard, the first page after sign-in, with failures, backlogs, the slowest jobs, success rates, the day's free-plan use and when the cron last ran; a daily summary email for whoever turns it on; warnings before an API key or secret expires, with Rotate; dead-letter queues for tasks that fail for good; the People page for invitations and permissions; and the audit log of every change.
Choices that shape it
- It behaves like Cloud Tasks and Cloud Scheduler: every HTTP method, any public URL, headers, a body and an auth header; named queues with rate and retry settings; jobs with a cron, a time zone and retries.
- Queues and jobs are made and managed only on the console pages, not in code.
- It has its own users, by invitation. Cloudflare Zero Trust needs a card, so it is out.
- It uses no Cloudflare Queues. The engine is the console's own: a Durable Object per queue and per job.
- All the business logic is in the Worker. The pages show what the API answers and send what people typed.
- It is shared by any project, and lives in its own repo.
- Out of scope: pull queues, App Engine and Pub/Sub targets, regions, paid-plan features and a public sign-up.
In this write-up
/v1 calls an app makes with its key, and how FlowDeck uses them.
Project infoSix documents: the screen flow, annotated screens, journeys, a clickable prototype, the style guide and the manual.
Write-ups
- Tasks from a file, and sample files · how it works, 22 Oct 2026
Cloud Console, as it is on main. 22 Oct 2026.