How this studio runs.
The infrastructure, deployment process and model-review rules behind the portfolio.
Studio-operated infrastructure
The portfolio runs as containerized applications on hardware operated by the studio. Git pushes trigger builds and deployments, while Cloudflare provides the public edge.
- 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
The AI-assisted products combine language models with retrieval and fixed rules. Engine changes are released only after their evaluation suites pass. In the lesson-planning and retirement products, teachers and advisers review the results they use.
- ENGINES
- LLM pipelines · retrieval · rules
- QUALITY
- Eval suite on every change
- BUILD
- Agentic coding · human review
- RULE
- Draft ≠ verdict
This website
draftedby.com is a Next.js site hosted on the same infrastructure as the portfolio. It has no ads or advertising trackers. Visits are measured with self-hosted, cookieless Umami analytics.
- TYPE
- Archivo · IBM Plex Mono
- STACK
- Next.js · self-hosted
- ANALYTICS
- Cookieless · self-hosted
- MOTION
- Respects reduced-motion
Questions about the infrastructure or release process go directly to the people who run them.
Contact the studio