Skip to content

BYOB New inbox in every project

Fruitalytics Website Analytics

Most analytics tools force a choice between a heavy script and an empty dashboard. Fruitalytics is BYOB's first-party analytics layer: one install snippet, automatic capture, and a connections you can query for real funnel data.

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.

Paper website
Paper Minimal canvas product with crisp copy. Visit ↗
Nucleo website
Nucleo Icon library with a clean, focused page. Visit ↗
Mailchimp website
Mailchimp Email leader with benefit-led sections. Visit ↗
Typefully website
Typefully Creator tool with a sharp, simple pitch. Visit ↗
Postcards website
Postcards Email builder with clear template previews. Visit ↗
#paid website
#paid Creator marketplace with social proof up front. 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 →

Fruitalytics is first-party analytics for BYOB apps. A tokenless registration call returns an install snippet and credentials; the hosted analytics.js captures pageviews, errors, performance, scroll depth, and clicks automatically, while explicit track calls record the funnel events you read from a dashboard or connections.

Tokenless site registration

Getting started does not require generating a connections key first. A single registration call with the site name and allowed origins returns one-time install credentials and a ready-to-paste tracking snippet. That snippet already enables the default capture surface, so a generated app can start collecting meaningful data immediately. Plaintext credentials are returned once and stored as hashes by the service, so the install step is the moment to save them before they are out of reach.

What gets captured automatically

Once the script is on the page, a lot of product signal arrives without extra code. It records page_view on initial load and on client-side route changes, JavaScript errors and unhandled promise rejections, failed fetch and XHR calls, performance metrics including LCP and CLS, scroll depth at quarter milestones, outbound link and download clicks, and rage clicks. Together these answer whether a page loaded, stayed loaded, and held attention, before you write a single custom event.

Naming funnel events that stay useful

Autocapture tells you what happened broadly; named events tell you where a funnel leaks. Add explicit events in object-action form, such as signup_started, checkout_completed, or export_completed, and attach stable low-cardinality properties like funnel and step. Events can also be declared directly in markup with data attributes on buttons and sections, so a call-to-action can report its step without a JavaScript handler. Keeping names stable is what makes week-over-week comparisons trustworthy.

Privacy boundaries by design

Analytics is more useful when it is not collecting things it should not. Autocapture does not record input values, and diagnostics avoid request bodies and form values. URLs are stored without query strings or hashes. The event taxonomy guidance is to send stable keys rather than raw email addresses, names, phone numbers, message bodies, tokens, or payment details. That keeps funnel reporting useful while avoiding the sensitive data that turns an analytics tool into a liability.

Origins and custom domains

Tracking only works when the browser origin is registered for the site. Registration origins are plain http or https origins with no paths, wildcards, or credentials, and each site can hold several. That means localhost, a preview URL, and a live custom domain can all report to the same site. After registration, origins can be managed with the site-scoped admin token or the BYOB analytics commands, so adding a domain is a small config change rather than a new setup.

Reading the dashboard and connections

Data you never look at changes nothing. Registration returns a dashboard URL for humans, and the same data is available through a connections for agents and scripts: counts, recent events, and funnel results for the site. A read token scoped to that site is enough to query it, and an admin token can list across sites. Because the query surface is a connections, you can check conversion after a change without opening a browser or waiting on a report to refresh.

FAQ

Frequently Asked Questions

Do I need to paste a connections token to start?

No. Site self-registration is tokenless; the register call returns the snippet and install credentials, which you store in project environment variables.

Does Fruitalytics collect personal data?

Autocapture does not record input values, and diagnostics avoid request bodies and form values. URLs are stored without query strings or hashes.

What are automatic events?

page_view on load and route change, plus JavaScript errors, failed requests, performance metrics, scroll depth, outbound links, downloads, and rage clicks.

Can I track my own conversion funnel?

Yes. Call track with snake_case event names such as signup_started or checkout_completed and stable properties like funnel and step.

Will it work on a custom domain?

Yes, once that origin is in the site's allowlist. Custom domains work after being added to the registered origins.

Can I query the data programmatically?

Yes. A site-scoped read token returns counts, funnels, and recent events from the dashboard connections.

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.