Silex review: a free/libre website builder built on GrapesJS

What Silex is, and who it is for

Silex is a website builder you run, not a library you import. It wraps the GrapesJS engine in a complete application: a project workspace, hosting connectors, and a publication step that pushes the result to a host or a repository.

The audience is people who want the Webflow experience without Webflow's business model: agencies producing client sites, non-profits with no budget for per-site subscriptions, and organisations whose policy favours copyleft software maintained by an association rather than a venture-funded vendor. Silex Labs is a French non-profit, there is no contributor licence agreement, and the licensing is structured so that it cannot be relicensed later.

It is in this dataset because it appears on shortlists next to embeddable engines, and it is important to be clear that it answers a different question. If your product needs an editor inside it, Silex is the wrong layer and GrapesJS is the right one.

Architecture

Silex builds on GrapesJS, so the editing model — an iframe canvas, a component tree, a style manager — is inherited. What Silex adds is everything around it: the application shell, project management, and a connector interface that abstracts where files are stored and where sites are published.

That connector interface is the most interesting extension point for developers. Adding your own storage backend or publication target is a defined integration rather than a fork, which is how agencies wire Silex into their own hosting.

The relationship with GrapesJS also sets expectations for plugins: the underlying component and plugin model is familiar to anyone who has used the engine, but compatibility with arbitrary GrapesJS plugins is not guaranteed, because Silex has its own application-level assumptions.

Getting started

We did not run Silex as part of our hands-on benchmark, because it is an application rather than an npm-installable editor comparable with the others, and we do not publish code we have not executed. What we can state from primary sources: the silex-website-builder package has been on npm since April 2019, and the project publishes v3 with its own installation documentation.

For an evaluation, the honest advice is to run the hosted instance the project offers before deciding to self-host, because most of what distinguishes Silex is the application experience rather than the engine underneath it.

Strengths

A complete free builder. Not a toolkit — a working product with a publication workflow, at no cost.

Governance you can inspect. A non-profit steward, no CLA, and dual licensing designed to keep it free. For organisations that have been burned by a licence change, this is a substantive difference rather than a philosophical one.

Static publishing. Output goes to a host or a repository, so sites are portable and cheap to serve, with no runtime dependency on the builder.

Familiar engine underneath. Teams who know GrapesJS recognise the editing model immediately.

Connectors are a real extension point. Storage and publication targets are pluggable, which is what makes it viable for agencies with existing hosting.

Limitations

Not embeddable. This is the headline limitation for readers of this site. Silex is not designed to be mounted inside another application, and the copyleft licensing makes a commercial embed a question for your lawyers rather than your architects.

Copyleft licensing needs review. GPL-3.0 or MPL-2.0 is fine for many uses and a blocker for some. Compare with GrapesJS's BSD-3-Clause, which asks nothing of you.

Thin developer documentation. User-facing documentation is reasonable; connector and plugin documentation is thinner and version-specific details lag as v3 evolves.

A small ecosystem. A committed community, but plugin supply is limited and mostly produced by the maintainers.

No commercial support contract. For teams that need a contractual response time, a non-profit project is not the right procurement shape.

Pricing

Free software, no licence fee, no usage ceiling. An optional paid cloud instance funds the project, and donations go through the association. The cost of self-hosting is operational: someone patches it, someone runs the storage behind it, and someone answers when the editor is down.

If what you actually want is the engine inside your own product, GrapesJS is free of both the licence question and the application layer — Silex vs GrapesJS sets the two out side by side.