How Byoi works under the hood
How Byoi separates app, Git, administrative database, AI, and deployment, for developers and agents deciding whether to trust it with a project.
updated 2026-07-10
Byoi architecture exists to keep user projects in Git, reduce data custody, and give developers control over AI, context, and configuration.
Core thesis
Byoi does not try to own the project. The app organizes the workflow; content lives in the user Git repository; AI keys stay encrypted in the administrative database; project configuration is versioned.
Layers
The product layer is a Next.js application. The execution layer runs on Cloudflare Workers through OpenNext. The database is PostgreSQL/Neon with Drizzle and stores only administrative data: identity, session, billing, project links, Git connection, and encrypted secrets.
GitProvider
Every Git operation goes through a provider interface. Product logic does not depend directly on GitHub SDKs, URLs, or internal shapes. In V1, GitHub is the implementation; other providers enter only when real demand exists.
Source of truth
Cards, decisions, knowledge, context, prototypes, allowed assets, and byoi.config.json live in the user Git repository. The database may store operational metadata and derived cache, but it does not become the project source.
User repository
A Byoi project is a user-owned Git repository. The app creates and organizes files, but the user can review commits, edit outside the product, clone locally, and use any tool compatible with Git and Markdown.
Customization
The workflow comes from versioned configuration: board columns, card types, preferences, and routing rules. Invalid config falls back to safe defaults per section without breaking runtime.
AI
AI is treated as a proposal. The product assembles context, calls the configured provider, and shows model/key usage. Relevant repository writes require explicit user action.
Deployment
The public domain is byoi.app. Production deploy uses GitHub Actions triggered by v* tags, OpenNext build, and Wrangler publication to Cloudflare Workers.
Frequently asked questions
Does Byoi need to copy my whole repository to work
No. The app reads and writes files on demand, when you open a screen or take an action. The administrative database stores operational metadata and derived cache, but the user Git repository remains the source of truth for the project.
Why does Byoi use Git instead of its own project database
Because Git already solves versioning, history, and portability. Storing cards, decisions, and context as committed Markdown means the project stays useful and auditable outside Byoi, and any coding agent already knows how to read a Git repository.