Skip to content

Glossary

A short reference for the terms that come up throughout these docs.

A worker in Typillar’s control plane. The planning agent turns your requests into scoped tickets; the build agent builds them. See Agents & the control plane.

README.md, a real file in your app and in your repo: what the product is, who it’s for, what it does, and — under Non-goals — what it deliberately will not do. Both agents write it and carry it in every turn, and it survives compaction, so it’s what they fall back on when the conversation is trimmed. It is rendered on Overview and never shipped with your live app. See The Plan tab.

The repeating sequence at the heart of Typillar: idea → build → ship. See The build loop.

A typed platform feature the agent can add to a built app — Data, File uploads, Project assets, Email, AI, Payments, Usage limits, Analytics, Realtime, Calls, Scheduled jobs, Background jobs, Workflows, API connections, Webhooks, PDFs & images, Video, Push notifications, Bot protection, Sign-in and Teams. Most serve /api/_* in your own Cloudflare account; Sign-in adds ready-made pages and /api/me. The agent turns one on when you ask for a feature that needs it. See Capabilities.

The part Typillar owns and runs: the agents and the orchestration that drive the loop. It coordinates work but does not host your project or store your data. See Architecture.

A live release of your project to your Cloudflare account, published at a real URL and recorded in your history. Every deployment is reversible. See Deploys & rollback.

What you type to start or extend a project — a plain sentence. An idea is not a thing Typillar stores: it becomes a ticket the agent can build, and the ticket keeps your original words as its origin. See How Typillar works.

The model work — reasoning and code generation — that powers the agents. It runs on your side (your own Cloudflare Workers AI), never on Typillar’s servers. See Zero inference on our servers.

A person in your organization. Teammates are free — there is no per-seat fee. See Organizations & teams.

The tenancy unit that owns your projects, connected accounts, and billing. You get one by default (solo); invite people and it becomes a shared team. See Organizations & teams.

The deliberate division of responsibility: you own the account, repo, data, and inference; Typillar owns the agents and the control plane. See What you own.

A billing tier — Free, Starter, Pro, or Enterprise — sized by how many projects you keep live, and carrying a project count and an hourly build cap alongside it. (Not to be confused with the Plan tab, where the planning agent shapes work into tickets.) See Plans & billing.

What you build and ship with Typillar — a site, an app, or a service — together with its repository, Cloudflare resources, data, and full history. Billing is sized by how many projects you keep live in production. See Your first project.

To put a build live in production — a deployment at a real URL on your Cloudflare account. One action, and reversible. See Deploys & rollback.

The two ways to undo, and they act on different things. Restore returns your app to an earlier version — it moves the code, and is what the project.reverted event reports. Roll back takes a live Deployment off its URL; the code is untouched, and it reports as project.rolled_back. Both are one action and non-destructive. See Deploys & rollback.

A concrete, scoped, named unit of work created from your plain-language request. It builds directly; the agent asks you in the thread if a decision is genuinely yours to make. See Tickets & the thread.

Cloudflare’s hosted-model service, billed through your Cloudflare account — the model the build agent runs inference on, on your side.