Websites and apps
Every new project picks a stack before the first generation. The selector sits next to the model picker on the prompt.
| Stack | Label in the app | Use it for |
|---|---|---|
| Next.js | Website | Marketing sites, landing pages, local business pages, menus |
| Vite | Application | Interactive apps, dashboards, tools that run in the browser |
Default for a blank prompt is Vite. Change it before you send if you are building a public website.
Next.js websites
Next.js projects are generated as static sites. The HTML is built ahead of time, so crawlers see real page content — titles, copy, links — without waiting on a client-only render.
That is the right choice when you care about Google, sharing previews, or a site that should load as HTML first. Restaurant menus, agency landing pages, and small business sites almost always belong here.
You still edit the result in the same workspace. Publishing and custom domains work the same way as Vite.
Vite applications
Vite projects are for product-like UIs: logged-in tools, editors, or apps that are not meant to rank as a brochure. They preview and publish like any other Bunstation project, but they are not the static-HTML path.
If you started on Vite and you actually needed a marketing site, clone is not a stack switch. Create a new Next.js project and point the prompt at the same brief.
What does not change
- Chat, preview, media, env vars, and Cloud are available on both stacks
- Publish still gives you a
*.bunstation.appURL - Cloud still attaches Postgres, endpoints, and crons to the project
Pick the stack for the job, then write a prompt that matches it.