Webstudio Website Builder
Webflow locks your sites on its infrastructure. You pay per project, per seat, and clean code export is not really an option. Webstudio is an open source visual builder that generates static HTML/CSS. Your sites, your code, your hosting. Bunker runs it for you in Europe.
Why Webstudio?
Webstudio gives you direct access to every CSS property. Webflow puts abstractions between you and the browser. Webstudio doesn't.
- Full CSS: every CSS property is accessible, no abstraction layer between you and the browser
- Headless CMS integrations: Strapi, WordPress, Notion, Airtable, Contentful, Sanity, and a dozen others
- Static sites: the builder publishes pure HTML/CSS/JS, served by Nginx. No heavy runtime on the visitor side
- No lock-in: the generated code is yours, exportable at any time
- AGPL-3.0: the source code is auditable and the project cannot become proprietary
Here's how the pieces fit together:
How it compares
| Criteria | Bunker | Webflow | Wix | WordPress.com | Framer |
|---|---|---|---|---|---|
| Open source | Yes (AGPLv3) | No | No | Partially | No |
| Sovereign hosting | Yes (Europe) | No (USA) | No (USA) | No (USA) | No (USA) |
| Full CSS | Yes | Partial | No | Via theme | Partial |
| Headless CMS | 15+ integrations | Proprietary | Proprietary | REST API | No |
| HTML/CSS export | Yes | Limited | No | No | No |
| Per-project pricing | No | Yes (from $14/mo) | Yes | Yes | Yes |
| Per-seat pricing | No | Yes | No | No | Yes |
| Unlimited sites | Yes | No | No | No | No |
What actually matters here
The source code is AGPL-3.0. You can audit it, modify it, redistribute it. If Bunker disappears tomorrow, you get your data back and reinstall Webstudio elsewhere. That's the whole point.
No per-project or per-seat pricing either. You pay for infrastructure, not for how many sites you build on it.
Published sites are static HTML/CSS served by Nginx. Fast load times, no JavaScript framework on the visitor side, good for SEO.
You keep control
Your data stays portable:
- HTML/CSS export: every published site is a set of static files you can retrieve
- PostgreSQL database: your projects live in a standard database, exportable using
pg_dump - S3 storage: your assets (images, files) are in MinIO, S3-compatible, so they're migratable to any S3 storage
- AGPL-3.0 license: the code stays free, no risk of proprietary closure
Why Bunker instead of self-hosting?
Installing Webstudio yourself means managing 6 coordinated services. It's doable, but it's a lot of moving parts:
| Aspect | Self-hosting | Bunker |
|---|---|---|
| PostgreSQL | Install and maintain | Managed |
| MinIO (S3 storage) | Configure | Pre-configured |
| Wildcard DNS | 3 zones to configure | Configured |
| Wildcard TLS | Certificates to renew | Automatic |
| Nginx (published sites) | Configure | Included |
| Backups | Set up | Automatic |
| Updates | Monitor | Applied |
| 24/7 monitoring | Build | Included |
The annoying part is wildcard DNS and TLS. Webstudio needs three domain zones with wildcard certificates: one for the builder, one for previews, one for published sites. On Bunker, that's handled out of the box. No ops tickets, no manual cert renewal :)
Quick start
1. Deploy from the console
- Go to console.getbunker.net
- Create your account or log in
- Deploy Webstudio from the service catalog
- A few minutes later, the builder is accessible
2. Create your first site
- Open the builder at the URL provided
- Start from a template or a blank page
- Drag and drop components, then edit styles directly in the CSS panel
- Preview in real time on the canvas
3. Publish
- Click Publish
- The publisher generates static HTML/CSS/JS files
- Nginx serves the site immediately on your domain
CMS integrations and dynamic pages
Connecting a headless CMS
Webstudio natively supports a bunch of content sources:
- Strapi, WordPress, Contentful, Sanity (for structured content)
- Notion, Airtable, Baserow (for spreadsheet-style data)
- Supabase, Hygraph, Directus (for custom backends)
Content is injected into visual components via bindings. When the CMS is updated, a re-publish is all it takes.
Dynamic pages
You can generate pages from your CMS data. Product pages from Strapi, blog posts from WordPress, listings from Airtable. Each CMS entry produces a static page with its own URL.
Forms
Forms are built-in. Submissions can be sent via webhook to any backend, or stored directly in Webstudio.
Tips
- Structure your components as reusables from the start. The builder supports it natively and you'll thank yourself later
- Use CMS integrations for any content that changes regularly
- Publish on a custom domain for SEO
- Export your PostgreSQL data regularly using
pg_dumpas an extra backup - Test your pages on mobile directly in the builder (responsive mode is built-in)