Features

WebSummoner is a Selenium hub that launches every browser session in its own Docker container. This page expands the four pillars of the project — jump to what interests you, every section links to the related guides.

Lightning fast

WebSummoner is a single Go binary, roughly 10 MB, with no runtime dependencies — no JVM, no application server. Under load it consumes about 10× less memory than a Java-based Selenium hub, and sessions start as fast as Docker can spawn a container.

Every session gets an isolated, reproducible environment: an exact browser version pinned by your browsers configuration, disposable tmpfs, and per-container CPU/memory limits.

Related: Usage statistics for watching the hub under load · Recommended Docker settings for sizing -limit.

Easy installation

Two paths, both measured in minutes:

• Docker only — one docker run with a browsers.json mounted. See the quick start.
• Configuration Manager — cm websummoner start --vnc downloads the binary, pulls browser images, writes the config and starts everything.

Ready-made images exist for all major browsers — no manual browser or driver installs.

Related: Ecosystem: CM · Browser images.

Modern UI

WebSummoner UI shows every running session: the live browser screen over VNC, streaming logs, queued requests and per-browser usage — for one instance or a whole cluster.

Sessions can be named per test (name capability), recorded to H.264 video with sound, and their logs saved automatically.

Related: Video recording (with audio) · Capabilities reference.

Cluster ready

Run many instances behind GGR — the go-Grid-Router that load-balances Selenium sessions across WebSummoner nodes with per-user quotas. Statistics are exposed over HTTP for Telegraf/Prometheus-style monitoring pipelines.

Related: Ecosystem: GGR · Migrating from Selenoid.