One workspace. Every product.
TillDev is the umbrella for a family of developer products that share one account, one dashboard, and one CLI. Add a product to your workspace and it shows up alongside the others — no separate signup, no second bill, no context switch. TillPulse, TillAuth and TillShield are generally available today; more of the stack is on the way.
The products
Observability — errors, performance, release health
› Read the docsAuth — sign-in, sessions, MFA, SSO for your users
› Read the docsManaged KV, queues, pub/sub
› Get notifiedReactive security — detection, rules, incidents
› Read the docsHow it fits together
Everything hangs off your organization. Invite your team once and they have access to every product you enable. Sign in and you land on your TillDev home — a product-neutral hub — then move between products from the switcher in the top-left of the dashboard, or with the ⌘K command palette.
Domains
The split isn't “one domain per product” — it's one domain per audience.
You — the developer — run every product from the control plane at tilldev.dev (this dashboard) and the tilldev CLI. Each product also answers to a vanity subdomain there — auth.tilldev.dev, pulse.tilldev.dev — but they all resolve to the same workspace. TillPulse, TillCache and the rest live only here: they're developer tools, so they never show a page to your end-users.
Your users only ever meet a product that renders pages to them. Today that's TillAuth — its hosted sign-in lives under tilldev.app, addressed by tenant, not by product: <your-app>.tilldev.app (or your own custom domain). A login screen shouldn't leak our product names, so there's no auth. in the URL your users see. Any future product with an end-user surface joins the same tenant host on a path.
The CLI
Anything you can do in the dashboard, you can do from the terminal with the tilldev CLI:
npm i -g @tilldev/cli tilldev login tilldev pulse projects # observability tilldev auth apps # authentication tilldev pulse ask "error rate today?"