Skip to content

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.

Typillar is split across a boundary that mirrors the ownership model:

  • The control plane (Typillar’s side). The always-on product-manager agent, the builder agents, and the orchestration that runs the build loop — proposing tickets, holding the approval gate, dispatching builds, and recording history.
  • Your infrastructure (your side). Your Cloudflare account runs the product 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 product nor your data.

ConcernLives in
Agents & orchestrationTypillar control plane
Inference (planning, codegen)Your Cloudflare Workers AI or your provider key
The deployed productYour Cloudflare account (Workers, D1, Durable Objects)
Source & historyYour GitHub repository
Connection tokens & model keysEncrypted at rest (AES‑GCM) in the control plane

Both Typillar’s own surfaces and the products 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.

Two OAuth connections bridge the two halves:

  • Cloudflare — so the control plane can build and run your product 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.