
BYOB New inbox in every project
Restaurant Website Builder in Tokyo
A Tokyo restaurant site that fills tables: food photography, reviews, and frictionless booking.
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.






Local details
What to know before you build here
- Currency
- Japanese Yen (JPY ¥)
- Tax
- Consumption tax at 10%
- Payments
- Cards, PayPay
- Domain
- .jp
Japanese-first; detail and trust are decisive.
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 →
Yes—BYOB builds a Japanese-first restaurant website for Tokyo operators. You get editable seasonal menus, reservation requests, a mobile layout that matches how Tokyo diners browse, and room for English for visitors. Prices display in yen, consumption tax at 10% is easy to note, and you can point a.jp domain at the finished site.
Why Tokyo diners expect a Japanese-first website
Tokyo is a market where people research a restaurant long before they arrive, and the default expectation is a Japanese-language page. A site that opens in Japanese and names your neighbourhood—Shibuya, Nakameguro, Kagurazaka or Asakusa—reads as a genuine local business rather than a foreign template. English can sit beside it for inbound visitors, but Japanese should lead. BYOB lets you publish both from one project, so you are not maintaining two restaurants online.
Reservations, walk-ins and small dining rooms
Many Tokyo restaurants still take bookings by phone, but a large share of younger diners prefer to check availability online first. A short reservation request form captures a name, party size and preferred time without forcing anyone to call during service. For counter-seat places in Ebisu or Shinjuku, you can state plainly whether you take walk-ins, how long a seat is held and whether a reservation fee applies. That reduces phone interruptions and sets expectations before guests arrive.
Payments,.jp domains and local discovery
Tokyo diners carry cards and PayPay, and a growing number expect at least one cashless option at the table. List the payment methods you accept clearly near the top of your contact page, alongside your nearest station exit and opening hours. A.jp domain reinforces that you are a Japanese business, and Japanese page titles and descriptions help your site surface when someone searches for a cuisine plus a neighbourhood. BYOB keeps the technical setup out of your way so you can focus on the food.
FAQ
Frequently Asked Questions
It is strongly advisable. Most local searches happen in Japanese, and a Japanese-first page signals that you are a real Tokyo business. Adding an English layer for visitors is helpful, but Japanese should be the primary language on the page.
Yes. Menus are editable, so you can reflect seasonal dishes, lunch sets and price changes without a developer or a full redesign each time the kitchen updates its offering.
Japan applies consumption tax at 10% on most dining. State clearly whether your listed prices include that tax or whether it is added at payment, so guests are not surprised when the bill arrives.
Cards and PayPay cover most expectations, though some smaller venues remain cash-only. Whatever you accept, name it on your contact page to avoid confusion at the table.
A.jp domain supports a local impression and pairs naturally with Japanese-language content. You can connect it to your BYOB project so the finished site is reachable at an address diners recognise.
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.