Choosing how to run Silex

Silex runs in several ways. Pick the one that matches what you're doing — testing, hosting for clients, contributing code, or integrating Silex into a larger Node.js project.

Comparison

Method	Best for	Works offline	All plugins included	CLI	GrapesJS plugins	11ty plugins	11ty build
Online — v3.silex.me	Getting started, no setup	No	Yes	No	Not yet (roadmap)	Yes	Included
Docker — silexlabs/silex	Single-site, simple self-hosting	Yes	No	No	Partial	Yes	Manual
Docker — silexlabs/silex-platform	Self-hosting like v3.silex.me (dashboard + plugins)	Yes	Yes	No	Yes	Yes	Manual
CapRover one-click	Easy deploy on an existing CapRover instance	Yes	No	No	No	No	Manual
npx @silexlabs/silex	Quick CLI test, integration in scripts	Yes	No	Yes	No	No	Manual
npm install @silexlabs/silex	Embed Silex in a Node.js project	Yes	No	No	No	Yes	Manual
Run from source	Contributing code to Silex	Yes	Yes	Yes	Yes	Yes	Manual
Silex Desktop	Offline desktop app	Yes	Yes	No	Yes	Yes	Included

Tip: if you just want to use Silex, the online instance is enough. Self-hosting is only worth it for security/compliance constraints, custom plugins, or air-gapped environments.

Recommendations

• Use Silex → v3.silex.me.
• Self-host for clients with the full feature set → Docker with silexlabs/silex-platform. Same image as v3.silex.me.
• Self-host minimal single-site → Docker with silexlabs/silex. No dashboard, no plugins.
• Embed in a Node.js app → npm install @silexlabs/silex.
• Contribute code → run from source. See the contribute guide.

Requirements

All Node-based options need Node.js 18+. GitLab connector requires GitLab 16+ if you self-host GitLab.

Platform support

OS	Docker	npx/npm	Tested by
Linux (Fedora)	✓	✓	@lexoyo
macOS	community-tested	community-tested	—
Windows	community-tested	community-tested	—

If you run Silex on macOS or Windows and want to claim a row, open a PR.