Skip to content

BYOB New inbox in every project

Export SvelteKit Code

A builder that holds your project hostage is a risk you only notice when you try to leave. BYOB generates ordinary SvelteKit files and lets you download the whole thing, so the app is yours the moment you want it.

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

Online
Today4
Done11
Streak6d
Open live app ↗
Prompt Product

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.

Vooma website
Vooma Logistics AI with a clear industry pitch. Visit ↗
Holocene website
Holocene Supply-chain page with calm, clear sections. Visit ↗
Outseta website
Outseta Membership platform with a launch-focused page. Visit ↗
Playground website
Playground Childcare software with a warm, direct hero. Visit ↗
ClickUp website
ClickUp Productivity suite with product-led sections. Visit ↗
Evernote website
Evernote Notes app with a memorable second-brain pitch. Visit ↗

Fresh from the community

See what builders ship, or start from an example.

View showcase →

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'>
2type Task = { id: string; title: string; done: boolean }
3let tasks = $state<Task[]>([])
4
5function toggleTask(id: string) {
6task.done = !task.done // just added by BYOB
7}
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

Online
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.

  1. 01 Describe the product Start with the outcome, audience, and any constraints. BYOB turns the idea into a practical build plan.
  2. 02 Shape the UX Review the proposed flows, screens, data needs, and visual direction before code starts moving.
  3. 03 Generate the app Tool Mode writes SvelteKit code, connects integrations, and keeps each change visible in preview.
  4. 04 Test and refine Ask for edits, roll back when needed, run checks, and keep the project editable instead of disposable.
  5. 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
npm
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.

Rated 4.9/5 by builders shipping with BYOB.

Start building
  • Clean SvelteKit code you own
  • One-click deploy + rollback
  • Pay as you go pricing

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

Popular

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 plans
View full pricing

Need white-label and SSO? Talk to us →

Exporting SvelteKit code from BYOB downloads your entire project as standard SvelteKit files you can run and host yourself. There is no proprietary runtime or hidden format, so the app keeps working outside BYOB. Secrets and platform-managed services such as storage and databases are reconfigured on the new host.

What the export contains

The download is the complete project tree: Svelte components, routes, server endpoints, Tailwind configuration, package manifest and configuration files. Nothing important is stripped out to force you back to the platform. Because the app was generated as real SvelteKit rather than interpreted at runtime, the export is not a conversion of your project into something exportable; it is the project. You can open it in any editor, run the same build, and expect the same pages. Reviewing the archive before you deploy is a useful sanity check that the source matches what you were previewing.

Standard SvelteKit, no hidden runtime

A project that only renders inside its authoring tool is not really portable. BYOB's output uses SvelteKit, Vite and Tailwind CSS, all of which are public, documented and widely understood. There is no custom interpreter that has to be present at runtime and no binary format that decodes your pages. If a developer joins the project, their existing SvelteKit knowledge applies immediately. If a framework release changes, you upgrade it like any dependency. The absence of a proprietary layer is the point: the app's usefulness does not depend on BYOB continuing to exist.

Running the exported project locally

After unzipping, install dependencies and start the development server the same way you would for any SvelteKit app. Routes you built render locally, and you can edit files with the tools you already prefer. Local development is where you produce a production build, run a type check or wire in your own test suite. Anything the hosted environment provided at request time, such as secrets or storage bindings, has to be supplied through environment variables or a local adapter first; the code expects configuration, not magic.

Hosting the export anywhere

The build output is a SvelteKit app, so it can run on any compatible host: a Node server, a container platform, or an edge provider such as Cloudflare. You are not limited to BYOB's hosting, and you do not need BYOB's permission to move. This matters for teams with existing infrastructure or strict data-residency rules. The trade-off is that deployment, certificates, DNS and scaling become your responsibility. Export gives you freedom and control; it does not also supply the managed convenience that publishing inside BYOB provides.

Reconnecting managed services

The code travels fully, but some services do not. Database connections, object-storage buckets, email sending, analytics and payment keys are configured per environment, and those values are deliberately not bundled into a downloadable archive. After exporting, you point the app at your own database or bucket and supply the relevant credentials. The application logic that talks to those services remains intact, so the work is configuration rather than rewriting. Knowing this in advance is the difference between a smooth migration and a surprise the first time a file upload or login fails on the new host.

Moving in and out of BYOB

Export is not a one-way door. The same CLI and Git integration that let you pull a project locally can bring work back to a BYOB workspace, and a repository can be connected so edits continue from either side. Teams often use this to let a developer work in a familiar editor while the rest of the team uses the hosted preview and visual tools. Because the source is the shared truth, there is no merge step between a platform version and a code version; both are editing the same SvelteKit project.

FAQ

Frequently Asked Questions

Can I export at any time?

Yes. The full project can be downloaded as an archive whenever you want, on any plan that includes export.

Will the exported app still work?

It is standard SvelteKit, so it builds and runs once you install dependencies and supply the configuration it needs.

Are my secrets included in the download?

No. Credentials and environment values are kept out of the archive and must be supplied on the host.

Can I keep using BYOB after exporting?

Yes. Export is not destructive; the project remains in your workspace and can be edited or re-imported.

Do I need to rewrite anything to self-host?

No rewriting. You reconfigure database, storage and other services for the new environment.

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.