Slater Webflow tooling with editor-led proof. Visit ↗
BYOB New inbox in every project
BYOB CLI and MCP
The BYOB dashboard is not the only way to work. The BYOB CLI installs a local byob command, and BYOB's MCP tools expose the same project operations to any capable client, so terminal users and coding agents can stay inside their own environment.
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.
TD
Team Tasks
Shared task tracking
Today4
Done11
Streak6d
Open live app ↗
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.
Refrakt Photography-led page with striking imagery. Visit ↗
Buy Me a Coffee Creator funding with a friendly, simple pitch. Visit ↗
Discord Community chat with bold, playful branding. Visit ↗
ISO Meet Hiring platform with a direct value prop. Visit ↗
Conflux Feedback tool with a clear all-in-one pitch. Visit ↗
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
Code
Act mode TodoPage.svelte
schema.ts
1
<script lang='ts'>2
type Task = { id: string; title: string; done: boolean
}3
let tasks = $state<Task[]>([])4
5
function toggleTask(id: string) {6
task.done = !task.done // just added by BYOB7
}8
</script> main · 0 problems Preview ready
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
B BYOB AI
Chat Act
Your prompt
“Build a todo app for beginners”
Build plan
80%- Task list UI + empty state
- Add + toggle actions
- Progress summary…
Add due dates and filter by done…
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
Live preview
/TD
Team Tasks
Shared task tracking
Progress 2 of 3 done
- Wireframe landing page
- Task list component
- Responsive polish + QA
Ask BYOB to refine
Deployed · SvelteKit · SSL on
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
npmnpx -y byob-cli codex installApprove 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
$0
$1 = 100 credits
Pro
$25
2,000+ credits/mo
Max
$79
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 →Number of pages: 5
Traditional agency estimate
$5,750 upfront
Yearly maintenance
~$1,150 / year
BYOB estimate
~$45 in credits
BYOB builds the same site from one prompt and hosts it on the edge. Planning estimates, not quotes.
See BYOB plansView full pricing
Need white-label and SSO? Talk to us →
The BYOB CLI is an npm package that exposes project lifecycle, database, git, deploy, analytics and domain operations as terminal commands. BYOB also provides MCP tools over a local stdio server or a hosted connection, letting MCP-capable agents run the same operations on your project.
A command line for the things you would click
The CLI ships as an npm package that installs a local byob command. You can run it once with npx or install it globally, then work against your account and projects without opening a browser. It is not a thin wrapper around a single action: it authenticates with the same account you use in the dashboard and exposes the operations that make up a project's life. For developers who prefer a terminal, that is the difference between borrowing the interface and owning the workflow.
A wide command surface
Aliases cover the main lifecycle: status, context, start, stop, restart, cleanup and deploy. Beyond that, database commands inspect status and schema, run read-only queries and apply migrations; git commands read logs and diffs; domain commands manage hostnames; and analytics, environment, testing and export commands round out the set. Calling a specific tool directly is also supported, so anything the platform exposes can be reached without learning a bespoke subcommand first.
Two ways to speak MCP
BYOB supports both hosted and local MCP connections. Hosted clients such as ChatGPT, Claude, Codex or a custom OAuth-capable app use the dashboard connection flow. A local client starts the stdio server through a standard command, arguments and environment block, which is the shape most MCP hosts already expect. Either way, project targeting is explicit: configure one server entry per project so a tool call cannot silently apply to the wrong project.
Account scope before project scope
Some operations belong to the account rather than one project. You can check account status, inspect the account tool list, and create a project from a brief before selecting it for editing. After that, project-scoped commands name the target with a project id, and the CLI does not persist a hidden current project that a later command might inherit by accident. That explicitness is slightly more typing but far less risk when you operate several projects from one machine.
Built for automation
Turning on persistent JSON output makes responses stable and machine-readable, with a one-command override when you want human output for a single call. A heartbeat and version command let a script confirm the CLI is alive and current, and account or project tool listings can be captured for discovery. Because the output is structured, a shell script or worker can branch on success and error codes instead of scraping prose from a chat response.
Guardrails and privacy
The CLI is powerful on purpose, but it is not an unrestricted remote shell. Environment tools report whether a key exists without revealing its value, and commands that execute code use an allowlisted build, check, lint and test facade rather than arbitrary shell access. Local telemetry is redacted and can be disabled, and credentials are meant to stay out of chat, logs and config. The aim is automation you can run confidently, not a second set of unguarded admin keys lying around.
FAQ
Frequently Asked Questions
What is the BYOB CLI?
An npm-distributed command line that authenticates with your BYOB account and exposes project lifecycle, database, git, deploy, analytics and domain operations from the terminal.
Do I need Codex to use the MCP server?
No. BYOB supports a hosted connection for OAuth-capable clients and a local stdio server for any host that accepts a command, arguments and environment entry.
Does the CLI expose a raw remote shell?
No. Commands use an allowlisted build, check, lint and test facade, and arbitrary shell execution is not exposed through the agent surface.
How does authentication work?
An OAuth device flow approves the CLI against your account, and the token is stored locally so later commands reuse it.
Can I use the CLI inside scripts?
Yes. Persistent JSON mode plus per-command overrides make output stable enough to parse and automate.
Can I turn off telemetry?
Yes. Diagnostic logging is local and redacted, and both local and remote telemetry can be disabled from the CLI.
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.