Skip to content

FAQ

A product company you run by typing: describe an idea, and a plan agent and a build agent turn it into a live app — on your own Cloudflare account.

No. You describe outcomes in plain language; the agents write the code and commit it to your repository, where it’s there if you or a developer ever want it. See How Typillar works.

On your Cloudflare account — real production infrastructure you own, not a preview hosted by Typillar. See What you own.

In your GitHub repository, as ordinary commits. See Connect GitHub.

Everything keeps running. The project is on your Cloudflare account, the code is in your GitHub repo, and the data is in your databases. There’s nothing to export — it’s already yours.

A flat monthly price sized by how many projects you keep live: Free (1 live project), Starter (up to 5), Pro (up to 20), and Enterprise (unlimited, with SSO and an SLA). Building, previewing, and teammates carry no charge, and because inference and hosting run on your own Cloudflare account, nothing you ship carries usage fees. Each plan does cap how many projects it holds and how many agent runs an hour you may run — see Plans & billing.

Yes. Invite people into your organization and they build against the same connected accounts — owners manage the accounts and billing, members build.

No. Typillar runs zero inference on its servers. Every token is generated on your own Cloudflare account — on Workers AI, or on a frontier model reached through your Cloudflare AI Gateway. See Zero inference on our servers.

What you ask for is built directly — you don’t pre-approve your own requests — but the agent asks you in the thread whenever a decision is yours to make, and nothing goes to a live URL until you say ship. See Tickets & the thread.

Cloudflare access is for building and running your project; GitHub access is for committing code to a repo you choose. Both are granted by OAuth and revocable at any time. If your app takes payments, you also paste in a Stripe secret key — that one goes straight into a Secrets Store in your own Cloudflare account, so Typillar keeps its address and never the key. See Permissions & access.

Connection tokens are encrypted at rest (AES‑GCM) and never stored in plain text. You can rotate or remove them at any time. A key you paste for another service is not stored here at all — it goes into your own Cloudflare Secrets Store. See Your data & secrets.

Yes, two ways: restore the code to any earlier version, or roll back a live deployment to take it offline. Both are one action, both are non-destructive, and both are anchored to your commit and deployment history. See Deploys & rollback.

Follow the Quickstart — sign in, connect Cloudflare and GitHub, type your first idea, and ship.

Signed in, the console’s Help pane opens a thread with us, with your plan and the project you name attached. If you can’t get in at all, email support@typillar.com. Security reports go to security@typillar.com instead — see Security for what to include.