Skip to content
Super 1.7.0 is production-ready — transactional installs with automatic rollback, cron runtime caps (kill_after_secs), and panic-free input handling. See what’s new →
Documentation Center
Editions
Feature Matrix

Feature Matrix

FeatureOSSLicensed
Core Process Management
Start/stop/restart, autorestart, multi-process programs (numprocs)		✅✅
Dependency Orchestration✅✅
Atomic OTA Updates✅✅
Health Checks (TCP/HTTP)✅✅
Log Rotation & Streaming✅✅
Prometheus Metrics
Basic scrape in OSS; plugin metrics when licensed		✅✅
Historical Logs API✅✅
System Stats API✅✅
Event reactions ([[event_hooks]])✅
local scripts or webhook POST (command or url)		✅
same hooks; optional notify alongside
Cron Scheduled Tasks✅✅
Web Dashboard
Process list, logs, stack editor, license page — embedded in OSS superd		✅✅
API authentication
OSS: single admin Bearer (auth_secret); Licensed: multi-user Access Tokens (security)		✅✅
RBAC (User Roles)
security plugin (required for licensed startup)		❌✅
Audit Logging
security plugin (required for licensed startup)		❌✅
Linux Cgroups Isolation
isolation plugin (Linux only)		❌✅
Alerting
notify plugin: IM templates, multi-channel routing, storm suppression		❌✅
Dashboard Pro extensions
Tokens UI, Notification Settings, process hot-reload (ui plugin; needs peer plugins)		❌✅
LicenseMITCommercial

Same superd and super binaries for both columns — Licensed is OSS plus commercial plugins: drop plugins/*.so + [license].key in conf/super.toml to enable the right-hand column (see Editions).

To try, renew, or learn about the commercial plugin set, see Get Super Pro (free 90-day trial, optional ¥10/mo OSS sponsorship, license version coverage). Existing subscribers can also sign in to the Super Pro Portal.

Important

security is included with every subscription and is required for startup when [license].key is valid. RBAC, audit logs, and API token auth come from the security plugin. See Authentication.

Event hooks vs alerting

OSS has one reaction mechanism: [[event_hooks]] in super.toml — use command for local scripts or url for a basic webhook POST (raw event JSON). There is no separate “webhook notifications” row or config in OSS; webhook POST is an event hook.

Licensed alerting is the optional notify plugin (conf/notify.toml) — Slack/钉钉/Teams presets, channel routing, cooldown/batch, and inhibition rules. It listens to the same events; you can use both hooks and notify together.

Which setup do I need?

OSS

  • Personal projects, homelab, or local development.
  • Embedded Dashboard and optional single-secret API auth (loopback open by default; set auth_secret to turn auth on — required for non-loopback binds).
  • Trusted private network (VPN/VPC) with firewall in front of the API if you must expose the port.
  • No strict per-process CPU/memory enforcement.

Licensed

  • security.so + auth_secret — required for any licensed startup (included with subscription). auth_secret bootstraps Access Tokens; Admins may explicitly disable it after creating an Admin token.
  • PaaS or shared hosting with cgroup isolation (isolation, Linux hosts only).
  • Production alerting (notify plugin) — IM/webhook channels and storm suppression; complements (does not replace) [[event_hooks]].
  • Dashboard Pro extensions (ui) — Tokens, Notification Settings, hot-reload when peer plugins load (shell already in OSS).
  • Regulated environments needing audit logs (security).
  • Exposing API/Dashboard beyond localhost — security is always loaded when licensed; configure bind and tokens accordingly.

Was this page helpful? Thanks for your feedback!

Still have questions? Open an issue or browse the source.