How this studio runs.
The tooling behind the sheets — infrastructure, pipeline and AI practice. Written for the people who ask "wait, who hosts all this?"
Self-hosted, on purpose
The whole portfolio runs on studio-operated hardware — containerized apps, git-push deploys, tunneled behind a CDN. No hyperscaler bill, no black boxes, and every outage is ours to own and fix.
- HOSTING
- Self-hosted · own hardware
- DEPLOY
- git push → CI → build → prod
- EDGE
- Cloudflare tunnels · HTTPS only
- BACKUPS
- Nightly · 3-2-1 · restore-tested
Models draft, humans decide
Every product embeds an LLM pipeline, and the studio itself is built with agentic coding tools. The rule is the same at both levels: AI produces the draft, a professional signs it off. Engine changes ship only after the eval suite passes.
- ENGINES
- LLM pipelines · retrieval · rules
- QUALITY
- Eval suite on every change
- BUILD
- Agentic coding · human review
- RULE
- Draft ≠ verdict
The sheet you're reading
draftedby.com is built like the products: drafted, evaluated, shipped from the same pipeline. No ads, no third-party trackers, cookieless analytics.
- TYPE
- Archivo · IBM Plex Mono
- STACK
- Next.js · self-hosted
- ANALYTICS
- Cookieless · self-hosted
- MOTION
- Respects reduced-motion
Questions about the setup — or want the longer war stories? The contact sheet reaches the people who run it.
Start a sheet