Architecture
This is a bird’s-eye view of how Typillar fits together. You don’t need it to use the product, but it’s useful for understanding the trust boundary and where things run.
The two halves
Section titled “The two halves”Typillar is split across a boundary that mirrors the ownership model:
- The control plane (Typillar’s side). The plan agent, the build agent, and the orchestration that runs the build loop — turning requests into tickets, dispatching builds, relaying its questions back to you, and recording history.
- Your infrastructure (your side). Your Cloudflare account runs the project and the inference; your GitHub repository holds the source. This is where execution and storage happen.
The control plane coordinates; your infrastructure executes and stores. Typillar hosts neither your project nor your data.
What runs where
Section titled “What runs where”| Concern | Lives in |
|---|---|
| Agents & orchestration | Typillar control plane |
| Inference (planning, codegen) | Your own Cloudflare Workers AI |
| The deployed project | Your Cloudflare account (Workers, D1, Durable Objects) |
| Source & history | Your GitHub repository |
| Connection tokens (Cloudflare / GitHub) | Encrypted at rest (AES‑GCM) in the control plane |
Built on Cloudflare
Section titled “Built on Cloudflare”Both Typillar’s own surfaces and the projects it builds run on Cloudflare’s edge platform — Workers for compute, D1 for relational data, Durable Objects for stateful and coordinated work. Building on the same platform it deploys to is what lets Typillar provision exactly what a feature needs and ship it to a real URL quickly.
The connections that tie it together
Section titled “The connections that tie it together”Two OAuth connections bridge the two halves:
- Cloudflare — so the control plane can build and run your project on your account. See Connect Cloudflare.
- GitHub — so generated code is committed to your repository. See Connect GitHub.
Both are revocable at any time from either side — see Permissions & access.