Connect Cloudflare
Cloudflare is where your product actually runs. Connecting it is what lets Typillar deploy Workers, create databases, and give your project a live URL. You connect once, through Cloudflare’s own OAuth screen, and you can revoke at any time.
How to connect
Section titled “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.
Typillar never sees your Cloudflare password. The connection is an OAuth grant that Cloudflare issues and that you can withdraw.
What the connection is used for
Section titled “What the connection is used for”- Deploying your product to Cloudflare Workers.
- Provisioning resources a feature needs — D1 databases, Durable Objects, scheduled (cron) triggers.
- Publishing live URLs for what it builds.
- Running inference on Workers AI, if you choose that option for models.
Everything Typillar creates lives in your account, visible in your own Cloudflare dashboard, and remains yours if you disconnect.
What it is not used for
Section titled “What it is not used for”- It is not used to read or move data out of your account into Typillar.
- It is not a way for Typillar to host your product on its own infrastructure — there is none; your product runs on your account.
For the full picture of scopes and the trust boundary, see Permissions & access.
How to disconnect
Section titled “How to disconnect”You can revoke Typillar’s access two ways, and either is sufficient:
- From Typillar — disconnect Cloudflare in the console.
- From Cloudflare — remove the authorization from your Cloudflare account’s connected-apps settings.
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 product.