
BYOB New inbox in every project
Paddle Payments Integration
Paddle handles tax and merchant-of-record duties, which makes it a strong fit for SaaS billing. BYOB generates the checkout and webhook code that turns your pricing page into working subscriptions.
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 wires Paddle into generated apps: server routes build inline or hosted checkout payloads using Paddle price IDs, Paddle.js opens checkout in the browser, and a signed webhook updates subscription state in your database. Products and prices are reconciled through the Paddle API, while your project owns billing records.
Merchant of record, in plain terms
Paddle is not just a payment gateway. As merchant of record it becomes the seller of record for the transaction, handling sales tax, VAT, invoicing, and much of the compliance work that otherwise falls on a small team. That changes what your app must do: you still show prices and provide a checkout, but Paddle owns the tax and receipt layer. For founders selling across many countries, that offload is usually the main reason to choose Paddle over a raw processor.
Products and prices come from your account
Checkout needs real Paddle objects, not placeholders. BYOB reconciles them with your PADDLE_API_KEY: it lists existing products and prices first, then creates only what is missing, keyed by your catalog. Each plan maps to a pri_. price id stored in project environment variables. Reruns are idempotent, so adding a plan does not duplicate the catalog. Paddle treats sandbox and production as separate environments, and BYOB keeps their ids apart.
Inline checkout versus hosted checkout
Generated apps can support both Paddle checkout modes. Inline mode fetches a server-built payload and opens checkout inside your page, so the buyer never leaves your product. Hosted mode returns a provider URL and redirects the browser there, which can simplify compliance and localization. The server validates the requested plan key in both cases, and the browser is never allowed to pass an arbitrary price id. After payment, checkout returns to a success page for feedback.
Webhooks are the source of truth
A checkout success screen proves the user came back, not that money moved. The generated webhook route verifies the Paddle-Signature header with your webhook secret, rejects invalid payloads, and writes each event idempotently to a durable events table. Only paid or active events grant entitlement: completion evidence is a paid transaction or an activated subscription, while a merely created subscription records provider contact without unlocking paid features.
Subscriptions and entitlement state
Monthly and annual plans map to Paddle recurring prices, and each webhook updates a subscription record tied to the signed-in user. Because server-rendered session objects can be stale right after a webhook, generated account and pricing pages re-read the latest billing state from the database rather than trusting the session alone. When a subscription renews, upgrades, past-due, or cancels, the entitlement summary is recalculated from the stored plan mapping built from your price ids.
Sandbox first, then production
Paddle sandbox and production are fully separate. Run sandbox first with sandbox credentials, sandbox price ids, and a sandbox client token, then point a notification setting at the published deployment URL and send a simulator event to prove delivery. Going live means a production API key, production price ids, a production client token, and a production webhook secret, each reconciled and verified against the live domain. Never carry sandbox object ids into production.
An honest scope note
BYOB's managed payment integrations are Paddle and Razorpay. There is no built-in Stripe checkout flow, so if you prefer Stripe you write that wiring yourself in server routes. BYOB also does not run Paddle's provider setup inside your repository; reconciliation happens at the platform level, and your project owns the checkout endpoint, the webhook handler, and the billing tables it reads and writes.
FAQ
Frequently Asked Questions
BYOB's managed payment integrations are Paddle and Razorpay. You can call Stripe from generated server routes, but you own that wiring rather than getting a managed Stripe checkout.
You do. The merchant account, API key, and webhook secret stay with you; BYOB uses your key to reconcile products and prices.
Signed webhook events update a durable order or subscription table. The success page is feedback only; entitlement comes from webhook-backed state.
Paddle checkout expects a pri_. price id. Passing a pro_. product id causes errors, so generated payloads validate the prefix before opening checkout.
Yes. Use Paddle sandbox with a notification setting pointed at a reachable webhook URL, then send a simulator event to confirm a signed paid event reaches your app.
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.