Silex

Visual static site builder, honestly reviewed. No marketing fluff, just what you get when you own your own tools.

TL;DR

• What it is: Open-source (AGPL-3.0) visual website builder for static sites — think Webflow, but the output is standard HTML/CSS, the source code is on GitHub, and there’s no vendor controlling your files or your bill [README].
• Who it’s for: Freelance web designers, small web agencies, WordPress developers who want to ditch the theme layer, and no-code developers who’ve outgrown Wix or Squarespace but don’t want to touch code [README][website].
• Cost savings: Webflow’s paid plans start at $14/mo and climb to $200+/mo for CMS-heavy sites. Silex self-hosted runs on a $5–10/mo VPS. The online hosted version (v3.silex.me) is free, though it requires a GitLab account for file storage [README][website].
• Key strength: AGPL license with a non-profit copyright holder — no investors, no exit strategy, no subscription model, no enshittification risk. The README says “free forever” and the governance structure backs it up [README][website].
• Key weakness: Significantly smaller community than Webflow, Wix, or even WordPress. The desktop app and some features are still in crowdfunding. With 2,733 GitHub stars and ~1,124 active users per week, this is a niche tool for people who know what they want [README][website].

---

What is Silex

Silex is a drag-and-drop visual editor that outputs standard HTML, CSS, and JavaScript — no proprietary format, no lock-in. You design visually, export clean files, host anywhere. The project has been running since 2009, which makes it one of the oldest continuous no-code web builders in existence [README].

The editor itself is built on GrapesJS, a mature open-source page builder component. On top of that, Silex layers CMS connectivity (WordPress via GraphQL, Strapi, Squidex, Supabase, or any GraphQL API), static site generation via 11ty, and a plugin system for server and client extensions in JavaScript and TypeScript [README].

What actually makes it different from Wix or Squarespace is the output fidelity and the ownership model. Wix generates proprietary markup that you can’t export and host elsewhere — you’re renting a slot on their infrastructure indefinitely. Silex outputs standard HTML. Everything you build is yours, in formats any web host understands [README][website].

The non-profit angle is real and worth taking seriously. Silex is maintained by Silex Labs, a French non-profit with public finances on OpenCollective and no Contributor License Agreement — meaning the AGPL license can’t be changed by any future acquirer or investor, because there’s no investor and no exit strategy [website][README]. That’s not a marketing promise; it’s a structural commitment backed by French non-profit law.

As of this review, Silex sits at 2,733 GitHub stars and reports 22,887 accounts created, with 1,124 active users per week and 297 new users per week on the hosted version [website].

---

Why people choose it

Independent third-party review data was not available in the sources gathered for this article. The analysis below is drawn from primary sources: the GitHub README, the official website, and quoted testimonials on the website.

The two quotes the Silex README and homepage lean on most are direct: “The only open source alternative to Webflow.” and “The most powerful and graphically precise website builder that I have experienced.” [README][website]. Neither has a named source attached, which is worth noting — they’re presented as user quotes without attribution to a platform or person.

The positioning makes sense on paper. Webflow’s business model is:

• You design in their visual editor.
• You host on their platform (or pay for CMS export).
• If Webflow raises prices, changes terms, or shuts down, your site is tied to their infrastructure.

Silex’s answer is: design the same way, get files you own, host anywhere. For a freelancer or small agency building client sites, the math matters — not just monthly cost, but the ongoing dependency risk [README][website].

The practical use cases the website and README emphasize most:

Web agencies — visual workflow for client work, static output that scales without scaling infrastructure, no per-site licensing.

WordPress developers — use Silex as the visual frontend layer, pull content from WP via GraphQL, skip the theme system entirely. This is a genuinely interesting hybrid: you keep WordPress as the content layer (which clients often already know) while getting a proper visual builder on the presentation side [README].

Freelance designers — build client sites visually, deliver standard HTML files, invoice once and walk away. No client dependency on a platform you’re licensing for them [website].

---

Features

Based on the README and website scrape:

Visual editor:

• Drag-and-drop page building via GrapesJS — full HTML, CSS, and JavaScript access in the editor [README]
• “Graphically precise” is how the website describes it — CSS grid, flexbox, and custom CSS are all accessible, not abstracted away [README]
• SEO tools: meta tags, Open Graph settings, per-page configuration [README]
• Templates (currently in crowdfunding — 4 templates funded at €189/€2,000 as of the scrape) [website]

CMS and data integration:

• WordPress (via GraphQL), Strapi, Squidex, Supabase, or any GraphQL API [README][website]
• Bind components to dynamic data that clients can edit through their CMS [website]
• 11ty integration for generating static sites from Silex templates [README]

Deployment and output:

• Output is standard HTML/CSS — no proprietary format [README]
• Self-hosting: Docker, Node.js (npx @silexlabs/silex), CapRover one-click, YunoHost, Elest.io [README]
• Hosted online at v3.silex.me (requires GitLab account for storage) [README]
• Desktop app in development (Tauri-based, Windows/macOS/Linux, offline-first) — currently in crowdfunding at €0/€2,000 [website]
• CI/CD workflow via 11ty for deploying generated static sites [README]

Extensibility:

• Plugin system: server and client plugins in JS/TS [README]
• GrapesJS plugin ecosystem is available since Silex builds on it [README]

AI (in development):

• Desktop app will include “built-in MCP server” and AI integration — this is listed as coming soon, not shipped [README][website]

What’s not there (yet):

• The desktop app is crowdfunding at zero contributors as of the website scrape [website]
• Template library is minimal and also crowdfunding [website]
• No visual ecommerce — this is a static site builder, not a Shopify alternative [README]

---

Pricing: SaaS vs self-hosted math

Silex: Free. All features, AGPL license, no premium tier, no usage limits mentioned [README][website]. The hosted version at v3.silex.me is free with a GitLab account. Self-hosting is free software. The project funds itself via OpenCollective donations and feature crowdfunding campaigns [website].

Webflow for comparison:

• Basic: $14/mo (no CMS)
• CMS: $23/mo (up to 2,000 CMS items)
• Business: $39/mo (10,000 items)
• Enterprise: custom pricing (seats, SSO, compliance)
• Hosting is included but mandatory — you can’t export and host elsewhere without paying for the CMS export plan

Wix for comparison:

• Light: $17/mo
• Core: $29/mo
• Business: $36/mo
• Business Elite: $159/mo
• Same lock-in model — no meaningful export

Squarespace for comparison:

• Personal: $16/mo
• Business: $23/mo
• Commerce: $28–$52/mo

For a freelancer managing 10 client sites on Webflow, that’s $140–$390/mo in platform fees, every month, forever. With Silex, the marginal cost of adding a client site is: nothing. You deploy on shared hosting or a VPS, charge the client once, and stop paying as the portfolio grows [README][website].

Concrete math: a freelancer with 10 client sites on Webflow CMS plans ($23/mo × 10 = $230/mo) could migrate to Silex self-hosted on a $10/mo VPS. That’s $220/mo saved, $2,640/year. The trade-off is that you absorb the deployment work instead of Webflow absorbing it.

Caveat: the “self-hosted” calculus assumes you can manage a Linux VPS, or that you’re willing to pay someone once to set it up. If you’re a pure designer with zero server comfort, v3.silex.me is the path — and it’s also free, with the trade-off that your files live in your GitLab account [README].

---

Deployment reality check

Easiest path (online): Go to v3.silex.me, log in with GitLab, start building. Files are stored in your GitLab repo. No server management [README]. This is the right starting point for anyone not sure they need self-hosting.

Self-hosted via Node.js:

npx @silexlabs/silex

Then open http://localhost:6805. That’s the full self-hosted deployment for a local environment [README]. For a production server, you’ll need a reverse proxy and domain.

Self-hosted via Docker: Docker Compose setup, documented in the repository. Standard deployment with Caddy or nginx for HTTPS [README].

One-click options: CapRover and YunoHost are listed as supported deployment targets — both reduce Linux management burden significantly [README].

What can go sideways:

• GitLab dependency on the hosted version. The free online version stores your files in GitLab. If you don’t have a GitLab account or prefer not to use it, self-hosting is your path.
• Feature gaps from crowdfunding. The desktop app (offline mode, local files) and the template library are currently in community fundraising. The desktop crowdfunding has raised €0 of €2,000 target. Features listed as “under development” on the website should not be treated as available [website].
• Small community means fewer tutorials. With ~1,100 active users/week, you’re not going to find the same density of YouTube guides and Stack Overflow answers as you would for Webflow or WordPress. The official forums at community.silex.me and the documentation at docs.silex.me are your primary resources [README].
• GrapesJS edge cases. Silex is built on GrapesJS. GrapesJS is well-maintained, but it’s a third-party dependency — bugs in GrapesJS can surface in Silex and vice versa. This is standard open-source dependency risk.

Realistic setup time for a technical user: 30–60 minutes to a working self-hosted instance. For the hosted version on v3.silex.me: 10–15 minutes including GitLab auth. Desktop app: not yet available for stable use [website].

---

Pros and cons

Pros

• AGPL + non-profit copyright holder. This is a structural guarantee, not a marketing promise. No CLA, no investor pressure, no “we reserved the right to re-license” escape hatch. The AGPL license stays AGPL [README][website].
• Standard HTML/CSS output. Files you can open in any text editor, host on any server, and move without asking permission [README].
• Free, all features included. No paid tier, no seat limits, no per-site licensing [README][website].
• GrapesJS foundation. Building on an established, maintained editor component rather than a custom-built canvas means better stability and compatibility with the GrapesJS plugin ecosystem [README].
• CMS integration that makes sense. The WordPress + GraphQL approach lets you separate the editing experience (WordPress) from the visual design layer (Silex), which is a better architecture than either pure WordPress themes or a locked-in CMS builder [README][website].
• 15+ years of continuous operation. Started in 2009, still actively maintained. That’s unusual longevity for an open-source no-code tool [README].
• CI/CD + 11ty workflow. For developers who want to treat website content as code — static generation, version control, automated deployment — the 11ty integration provides that path [README].

Cons

• Small user base. 1,124 active users/week is a small number. That means fewer plugins, fewer third-party integrations, fewer tutorials, and fewer people to answer your questions in the community forums [website].
• Desktop app and templates are not shipped. Both are listed as “features under development” with crowdfunding campaigns. The desktop app has raised €0. Don’t buy Silex for features that aren’t there yet [website].
• AGPL has real implications. AGPL means if you build a web service with Silex’s code and expose it to users, you must release your modifications under AGPL. For freelancers hosting client sites this doesn’t matter. For developers building a SaaS product on top of Silex, consult a lawyer before you ship [README].
• No template library to speak of. Webflow has hundreds of templates. Silex has a crowdfunding campaign for 4 templates, at 11 contributors and €189/€2,000 raised [website]. You’re starting from scratch or from the GrapesJS baseline.
• AI features are future tense. The MCP server and AI integration are tied to the desktop app, which isn’t available yet [README][website].
• No ecommerce. Static site builder means you’d need to integrate an external service (Snipcart, Shopify Buy Button) for transactions. This is a design limitation, not a bug.
• Storage dependency on GitLab for the hosted version. If GitLab changes terms or access, v3.silex.me users’ stored sites are affected [README].

---

Who should use this / who shouldn’t

Use Silex if:

• You’re a freelance web designer or small agency building static sites for clients and you want to stop paying $20–40/mo per site to Webflow.
• You care deeply about vendor independence — you want files you own in formats that don’t require any specific platform to open or serve.
• You’re a WordPress developer looking for a better visual frontend layer that can pull content via GraphQL without being locked to WordPress themes.
• You’re comfortable with a basic self-hosted setup (Docker or a $5 VPS) or you’re fine using the GitLab-backed hosted version.
• You believe in the non-profit, free-software model and you’re willing to use a smaller community in exchange for structural guarantees about the software’s future.

Skip it (pick Webflow) if:

• You need a rich template library to start from and you need it today.
• You’re building client sites and your clients expect the same handholding CMS experience Webflow provides out of the box.
• You need ecommerce without integration work.
• Your team has zero tolerance for any setup complexity.

Skip it (pick WordPress + Elementor or Divi) if:

• Your client already runs WordPress and expects to edit content in WordPress’s admin.
• You need a massive plugin ecosystem for specific functionality (booking, memberships, directories).
• You want a 10-minute install on shared hosting.

Skip it (pick Publii or Hugo) if:

• You’re a developer who doesn’t need a visual editor and just wants a fast static site generator.
• You’re comfortable with templating languages and want more control than a visual editor gives you.

---

Alternatives worth considering

• Webflow — the obvious commercial comparison. More polished, larger template library, better CMS for non-technical clients, but closed-source SaaS with per-site pricing that scales painfully. The anti-pattern Silex is built to avoid.
• WordPress + Elementor or Divi — if your clients are already in WordPress and want to stay there, a visual page builder on top of WordPress is the path of least resistance. More maintenance overhead, but a massive support community.
• Builder.io — another visual builder with CMS integration and static generation. Commercial SaaS, not self-hostable, but a more polished product with better AI tooling in the current moment.
• Publii — desktop-first static site generator with a visual editor. Self-hosted, no server needed (files on your laptop), active development. More limited visual fidelity than Silex but simpler workflow for simple sites.
• Pinegrow — desktop visual editor for HTML/CSS/Bootstrap/Tailwind. One-time license (~$79–$149), no subscription, standard HTML output. More developer-oriented than Silex.
• Tilda — freemium visual builder, proprietary, good design defaults, not self-hostable. Easier onboarding than Silex, harder exit.
• GrapesJS directly — since Silex is built on GrapesJS, developers building a custom visual editor into their own product can use GrapesJS without Silex. Silex is the opinionated product layer on top.

For a freelancer or agency choosing between Silex and Webflow, the decision reduces to: do you want to pay per site forever, or invest a few hours in setup and own your stack? If the answer is own your stack, Silex is currently the only serious open-source answer to that question in the visual builder category.

---

Bottom line

Silex is the most structurally sound option in the open-source visual website builder category — not because it’s the most feature-rich (it isn’t), but because the governance model actually matches the “free forever” promise. A French non-profit holds the copyright, there’s no CLA, and there’s no investor alignment pointing toward a paid tier that doesn’t exist yet. That matters in a category where “open-source” tools have a long history of pivoting to aggressive commercial licensing once they have enough users to monetize.

The practical trade-offs are real: smaller community than any commercial alternative, a template library that’s barely funded, and a desktop app that’s still raising money. If you need something polished and complete today, Webflow or even a WordPress page builder will get you there faster. If you’re building a freelance practice or small agency and you want to own your toolchain without a recurring per-site bill that doubles every two years, Silex is worth the setup afternoon. At 2,733 GitHub stars and 15+ years of operation, it’s not going anywhere.

---

Sources

1. Silex GitHub README — github.com — https://github.com/silexlabs/silex
2. Silex Official Website — silex.me — https://silex.me/
3. Silex Hosted Application — v3.silex.me — https://v3.silex.me/
4. Silex Documentation — docs.silex.me — https://docs.silex.me
5. Silex Labs OpenCollective (project finances) — opencollective.com — https://opencollective.com/silex
6. Silex Roadmap — roadmap.silex.me — https://roadmap.silex.me/posts/3/silex-desktop