Skip to content

Choosing how to run Silex

Silex runs in several ways. Pick the one that matches what you are doing: testing, hosting for clients, contributing code, or running an offline desktop app (Silex Desktop is currently in early alpha).

Comparison

Method Best for Works offline Full SaaS (dashboard + connectors) GrapesJS plugins 11ty build
Online, v3.silex.me Getting started, no setup No Yes Built-in Included
Silex Desktop (alpha) Offline, single user, no account Yes No (single-user editor) Built-in Included
Docker (build from source) Self-hosting a full instance Yes Yes Built-in Manual
CapRover one-click Quick deploy on an existing CapRover Yes Yes Built-in Manual
Run from source with Node.js Self-hosting and contributing Yes Yes Built-in Manual

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

How Silex is packaged now

Silex is a monorepo, and the app is a single Node.js package. There is no separate @silexlabs/silex-platform package and no global command line tool anymore. To self-host, you clone the repository and build it (with Node.js directly, or inside Docker). The build produces the editor and the server, and the default configuration is the full SaaS (multi-site dashboard, onboarding, and connectors).

The GrapesJS plugins (fonts, symbols, data source, and more) are built into the editor from source, so every install includes them.

Recommendations

Requirements

All Node-based options need Node.js 20+ and pnpm (the project uses pnpm via corepack). The GitLab connector requires GitLab 16+ if you self-host GitLab.

Platform support

OS Docker Node from source Tested by
Linux (Fedora) Yes Yes @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 pull request.

Edit this page on GitLab