
BYOB New inbox in every project
Environment Variables in
Every real app eventually needs a value that should not sit in the source: a connections key, data storage URL, a webhook secret. splits those values into four environment modules, and BYOB gives them a home that survives from preview to published app.
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 →
exposes four environment modules: static and dynamic, each with private and public variants. Private values stay server-side, while public values must use the PUBLIC_ prefix and reach the browser. In BYOB you add keys through the project's environment settings, so the same code runs in preview and production with values supplied per environment.
The four $env modules
organises environment access along two axes. Static values are inlined at build time, which allows dead-code elimination but means a change requires a rebuild. Dynamic values are read at runtime, which suits secrets injected by the host and variables whose names are decided later. Crossing those with private and public yields four modules. Server files may import any of them; client files may only import the two public ones. Choosing the right module is mostly a question of whether the value is secret and whether it changes between publishings, so start there before reaching for a specific import.
The PUBLIC_ prefix, and why it matters
Only variables whose names begin with a configurable prefix, PUBLIC_ by default, are visible to browser code. Everything else is treated as private and discarded from public modules. This single rule is what keeps a service-role key out of a bundle. The common failure is the reverse: adding PUBLIC_ to a secret to make an import work, which ships that secret to every visitor. Treat the prefix as a security boundary rather than a naming convention. If a value is something only the server needs, it should never carry the prefix, no matter how convenient that would be.
Static versus dynamic loading
Static modules inline values during the build and give the bundler a chance to trim unused code. They are the better default for configuration that is fixed at publish time, such as a public project URL or an app name. Dynamic modules read the environment when the server starts or the request runs, which is useful for values supplied by the host or for constructing variable names at runtime. The trade-off is weight: dynamic public values are sent to the browser on every request, so prefer the static public module unless a value genuinely changes without a republish.
Adding secrets to a BYOB project
In BYOB, environment values belong to the project, not to your local machine or the chat. When the code you are building needs a key, the editor asks for it through a secure form rather than writing a placeholder into a file. Agents are expected to check which keys already exist before requesting them, and to avoid pasting secret values into prompts, logs or screenshots. Rotating a credential is then a settings change rather than a code edit. Because values are attached to the project, a later publish reuses the same configuration instead of depending on someone's local environment.
Preview, publish and parity
The point of centralising environment values is that preview and production behave the same. The application code imports a named value and does not care where it came from, so promoting a project does not require editing source. That is also the limit worth planning for: a binding that only exists once published, such as a storage bucket or managed data storage, cannot be exercised identically in a preview. Keep the code the same and supply the missing pieces per environment. Treat a published run as the place to confirm integrations, and the preview as the place to confirm the code path.
Mistakes that leak secrets
A small set of errors accounts for most exposure. Prefixing a secret with PUBLIC_ sends it to the browser. Committing a real.env file puts credentials in version history, where deleting the file later does not remove them from old commits. Writing placeholder values such as your_key_here creates confusing failures that look like code bugs. Importing a private module inside a component is caught at build time, which is a feature: it stops the mistake before publishing. The safe pattern is simple: secrets without the public prefix, imported only in server files, kept out of version control and supplied per environment.
FAQ
Frequently Asked Questions
Static values are inlined at build time; dynamic values are read at runtime, which suits host-injected secrets.
Only public ones whose names start with PUBLIC_. Everything else is server-only.
Use the project's secure environment form for the keys the code imports; do not paste values into chat or source files.
Prefer the $env modules. They work across SSR and the client and enforce the public/private boundary.
Static environment values are inlined at build time, so the dev server usually needs a restart.
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.