Connect Cloudflare

Cloudflare is where your project actually runs. Connecting it is what lets Typillar deploy Workers, create databases, and give your project a live URL. You connect through Cloudflare’s own OAuth screen, and you can revoke at any time.

Cloudflare is the only connection Typillar requires. Everything else — GitHub, payments — is optional and can wait.

How to connect

Open the console and choose Connect Cloudflare.
You’re sent to Cloudflare’s authorization screen, hosted by Cloudflare — you approve the connection there, not in Typillar.
After you approve, you’re returned to the console with Cloudflare connected.

Don’t have a Cloudflare account yet? You don’t need to go make one first — that same authorization screen has a Sign up link that carries the connection with it, so signing up there drops you back in the console already connected.

Typillar never sees your Cloudflare password. The connection is an OAuth grant that Cloudflare issues and that you can withdraw.

Access is granted incrementally

The first connect grants a baseline: enough to deploy your project, run the agent’s model, and read the live app’s request counts for the console. It includes no storage access at all.

The first time a feature actually needs more — a database (D1), file storage (R2), search (Vectorize), email, or a custom domain — Typillar sends you back to the same Cloudflare screen to grant that one permission. The console shows a Grant Cloudflare access to… step when it happens. Nothing is asked for before it’s needed, so expect that screen more than once over the life of a project.

Every scope, baseline and incremental, is listed in Permissions & access.

What the connection is used for

Deploying your project to Cloudflare Workers.
Provisioning resources a feature needs — D1 databases, R2 buckets, Vectorize indexes, Durable Objects, scheduled (cron) triggers.
Publishing live URLs for what it builds.
Running inference — the agent’s model, on your own account.
Reading the live app’s request and error counts, so the console can show you traffic without sending you to the Cloudflare dashboard.

Everything Typillar creates lives in your account, visible in your own Cloudflare dashboard, and remains yours if you disconnect.

Which account

If the connection can reach only one Cloudflare account, that is the one Typillar uses. If it can reach several, Typillar does not pick for you — the connection lands with no account chosen and Settings → Connections asks which one. Nothing builds or ships until you answer, because that choice decides whose account holds your product and whose bill it lands on.

Once projects are deployed, connecting a different account is refused, and the message names the projects in the way. Those projects live in the first account — switching would leave them running somewhere Typillar can no longer reach, manage or roll back. Archive or roll them back first, then connect the other account. Reconnecting the same account is always fine: that is what happens every time you grant a new permission, and it never disturbs the choice you made.

What Cloudflare’s free plan gives you

Because your project runs on your account, Cloudflare’s plan sets what your project can do — separately from your Typillar plan, which only counts how many projects you keep live. A free Cloudflare account is a real account, and the whole loop works on one: build, preview, ship, a live URL, databases, files, search, scheduled jobs, realtime, queues.

What the Workers Free plan bounds:

	Workers Free	Workers Paid (from $5/mo)
Requests to your app	100,000 / day	10M / month, then metered
CPU per request	10 ms	30M CPU-ms / month included
Build model inference	10,000 Workers AI neurons / day	Same allowance, then metered
Worker size	3 MB compressed	10 MB compressed
Heavyweight coder models	—	GLM-5.2, Kimi K2.7 Code
Sending email	—	Email send

Two consequences worth knowing before you start:

The daily inference allowance is the one you’ll meet first. 10,000 neurons is roughly a build or two a day. Nothing breaks — Typillar tells you the allowance is spent and that it refills tomorrow — but if you plan to build in a sitting, enable Workers Paid first.
Two models are simply not served on the free plan. GLM-5.2 and Kimi K2.7 Code need Workers Paid; the default, GPT-OSS 120B, does not. See Models.

An app that only receives mail is fine on the free plan — it’s sending that Cloudflare puts behind Workers Paid.

Two capabilities also carry their own Cloudflare subscription, on any plan: Files and Assets need R2 enabled once in your dashboard, and Video bills through Cloudflare Stream, which has no free tier. Typillar tells you when a capability needs one, at the moment it needs it — nothing is required up front.

What it is not used for

It is not a way for Typillar to host your project on its own infrastructure — there is none; your project runs on your account.
It is not a licence to touch the rest of your account. Typillar writes only to the resources it created and recorded itself; anything it did not create, it refuses to write to. See Permissions & access.
It is not a proxy for your app. Visitors hit your Worker directly — your app’s runtime traffic never passes through Typillar. What the console reads back (records, files, traffic numbers) it reads on your behalf, with your token, at the moment you open those panes, and keeps no copy. See Your data & secrets.

How to disconnect

You can revoke Typillar’s access two ways, and either is sufficient:

From Typillar — Settings → Connections → Disconnect next to Cloudflare. Typillar deletes its copy of your token and stops building and shipping.
From Cloudflare — remove the authorization from your Cloudflare account’s connected-apps settings. This also invalidates the token itself.

Revoking access stops Typillar from making further changes. Anything already deployed keeps running, because it lives in your account — disconnecting Typillar doesn’t tear down your project.