
BYOB New inbox in every project
Git and GitHub Integration
AI-generated code still deserves real version control. Every BYOB project is a Git repository, so changes are commits you can inspect, compare and restore rather than opaque edits made behind a prompt.
Runs on the stack you trust
Prompt to product
From one-line brief to finished app.
Compare the one-line brief with what BYOB ships. Real layout, data, and deploy status, editable from the same workspace.
Team Tasks
Shared task tracking
Drag the handle. Or focus it and use the arrow keys.
Get inspired
Sites like this, live today.
Real sites that do it well. Build something like this with BYOB.






Fresh from the community
See what builders ship, or start from an example.
Live workspace
Code, chat, and preview in one place.
The workspace is built for repeated product work, not disposable demos. Every generated file stays inspectable, every change is visible, and every follow-up can target the exact part of the app you care about.
01 · EDITOR
Generated code, ready to edit.
Every file BYOB writes stays visible and editable. Follow-ups target the exact lines you care about instead of regenerating from scratch.
- Added lines highlighted the moment they land
<script lang='ts'>type Task = { id: string; title: string; done: boolean
}let tasks = $state<Task[]>([])function toggleTask(id: string) {task.done = !task.done // just added by BYOB}</script>02 · AI COMMAND
Plan, build, and refine in one chat.
Describe the outcome once. BYOB turns it into a build plan, implements it step by step, and keeps every change visible while you iterate.
- Build plan with live progress you can inspect
Your prompt
“Build a todo app for beginners”
Build plan
80%- Task list UI + empty state
- Add + toggle actions
- Progress summary…
03 · LIVE PREVIEW
See every change the second it lands.
The preview updates as BYOB works, with deploy status attached, so the path from edit to production stays inspectable.
- Real app state, not a static mockup
Team Tasks
Shared task tracking
- Wireframe landing page
- Task list component
- Responsive polish + QA
Prompt to app
From first prompt to a workspace you can ship.
Start conversationally, approve the shape, let Tool Mode implement, then refine and deploy from the same workspace.
- 01 Describe the product Start with the outcome, audience, and any constraints. BYOB turns the idea into a practical build plan.
- 02 Shape the UX Review the proposed flows, screens, data needs, and visual direction before code starts moving.
- 03 Generate the app Tool Mode writes SvelteKit code, connects integrations, and keeps each change visible in preview.
- 04 Test and refine Ask for edits, roll back when needed, run checks, and keep the project editable instead of disposable.
- 05 Deploy Ship the finished app, connect domains, and keep iterating from the same workspace.
Agent and backend
Code with your agent, ship with a real backend.
Connect Codex, Claude Code, or Antigravity to your project, then store data and ship to production without leaving the workspace.
- Approve project access from BYOB
- Installs the byob command
- Preview, deploy, git diff, DNS, credits, and code tools
npx -y byob-cli codex install Approve only the projects your agent can touch, then read context, edit files, inspect diffs, test previews, and roll back from your terminal.
- 1
- prompt to start
- 3
- live panes
- 24/7
- edge preview
Loved by builders
Rated 4.9/5 by developers and founders using BYOB to move from idea to shipped product.
Built for shipping
The parts that usually slow you down are already here.
BYOB handles product planning, implementation, preview, testing, database work, and deployment from one focused interface, with coding-agent access and production analytics when you want to keep working from your own terminal.
This part is hands-on. The cards drift until you touch them. Drag to rearrange, or press and hold one to feel it push back.
Agent integrations
Give Codex, Claude Code, or Antigravity scoped access through BYOB CLI or Agent MCP. Your agent reads context, edits code, tests previews, and deploys from your terminal.
Git history and diffs
Every change lands as a commit. Inspect history, compare diffs, and see exactly what changed since the last deploy.
Inbox in every project
Every project ships with an inbox. Collect messages, leads, and feedback from your app without wiring a third party.
Email sending built in
Send magic links, OTP codes, and transactional mail from your own sender address. Resend-backed, no SMTP setup.
Google and magic-link login
Offer Continue with Google plus passwordless email codes. Sessions and callbacks are handled.
Custom domains and SSL
Point your domain at BYOB with guided DNS checks. Certificates are automatic.
Visual editing
Click any element in the live preview and describe the change. Copy, spacing, color, behavior.
AI testing agent
Run full-site or feature checks and get implementation-level feedback you can apply in one step.
Version rollback
Step between saved states or redeploy a known commit when an experiment goes sideways.
One-click deploy
Builds publish to production hosting in one step. Deploys can auto-save the project state first.
Deployment analytics
Worker traffic, errors, CPU timing, subrequests, and custom-domain status from the workspace.
Supabase aware
Connect Supabase and BYOB reads schemas, drafts migrations, and generates types that match your app.
Team collaboration
Invite people in and keep sessions coordinated so work never overwrites work.
- Vision inputs
- Voice coding
- Project templates
- SEO-ready output
- Context tracking
- Model lock
Simple pricing
Start with credits, upgrade when usage is steady.
Pay as you go when you are exploring. Move to Pro or Max when BYOB becomes part of your regular build workflow.
Pay as you go
$1 = 100 credits
Pro
2,000+ credits/mo
Max
8,000+ credits/mo
Live estimator
What will your app cost?
Try the cost calculator. Drag the pages slider, toggle the options, and watch the agency quote vs BYOB update instantly.
Open full cost calculator →$5,750 upfront
~$1,150 / year
~$45 in credits
BYOB builds the same site from one prompt and hosts it on the edge. Planning estimates, not quotes.
See BYOB plansNeed white-label and SSO? Talk to us →
BYOB keeps every generated project in Git. You can list commits, diff any two refs, compare against the last deploy, restore a version or roll back a deployment, and issue project-scoped Git tokens for external access. Export the project to host it on GitHub.
Version history from the first prompt
BYOB does not keep your changes in a private database that only the builder understands. Each project lives in a Git repository, and work is captured as commits as you build, with periodic auto-commits on top of explicit saves. Deployment is tied to a specific commit, and a deploy records which commit went live. That last detail matters: because auto-commits continue, the newest commit is not automatically the deployed one, so the recorded deployment hash is the reliable reference.
Reading history without cloning
You do not need a local checkout to understand what changed. A log command returns recent commits, and a diff command compares any two references, including a shortcut that compares the currently deployed commit to the current head. Diff output comes in modes so a summary of changed files, a product-oriented view of meaningful hunks, or a fuller patch can be requested depending on whether you are skimming or auditing. Path filters and size caps keep large or generated files from swamping the output.
Two levels of rollback
Recovery works at two scopes. A version restore returns the project to a chosen commit, which is useful after an experiment or a bad AI edit. A deployment rollback goes further: it restores a version and redeploys it so the live site matches the code you selected. Together they make fast iteration safe, because undoing a change is a deliberate, recorded action rather than a scramble. The deployed commit hash is the anchor both operations rely on.
Project-scoped Git tokens
External tools sometimes need Git access without a full session. BYOB issues project-scoped personal access tokens with a readable name, a read or read-write scope, and an optional expiry defaulting to ninety days. The raw value is shown once at creation, then listed by prefix so it can be identified but not recovered, and revoked when it is no longer needed. That model suits automation and review tools while keeping credentials short-lived and narrowly scoped to one project.
Moving code to GitHub
BYOB's Git history is the project's own, but that does not make it a hosted GitHub mirror. To collaborate on GitHub, export the project or pull it through the CLI, then push it to a repository you control. There is no automatic two-way sync, and generic Git push from inside container tools is intentionally unavailable so the platform's own save and deploy flow stays authoritative. In practice this means GitHub is a destination you choose, not a live mirror that silently diverges.
Why Git matters more with AI
When a model can write dozens of files in one turn, review and recovery stop being optional. A commit-per-change history turns an AI edit into something a teammate can read as a diff, question, and revert. It also gives you a concrete artifact to point at during a review: this exact change, on this exact commit. Without version control, fast generation becomes fast breakage; with it, speed and accountability coexist.
FAQ
Frequently Asked Questions
Yes. Every generated project is stored as a Git repository, with commits captured as you work and periodic auto-commits on top of explicit saves.
Not as an automatic two-way sync. You move code to GitHub by exporting the project or pulling it with the CLI and pushing to a repository you own.
Use the Git history: inspect the diff, then restore an earlier version commit, or roll back a deployment to redeploy a known-good version.
Project-scoped access tokens for external diff and log tools, created with a read or read-write scope, shown once, optionally expiring, and revocable at any time.
It diffs the deployed commit against the current head, so you can see exactly what would ship in the next release.
No. Periodic auto-commits continue after deployment, so the recorded deployment commit is the reliable reference for what is live.
Build the first version today.
Start with one clear prompt. BYOB will help turn it into a product you can inspect, edit, test, and ship.