diff --git a/README.md b/README.md
index 4f3261aa..91d00899 100644
--- a/README.md
+++ b/README.md
@@ -41,28 +41,16 @@ It runs as a single container on your hardware and gives you a UI for the work y
A Sencho instance is autonomous. To manage another machine, you install a second Sencho on it and connect them with a long-lived API token; the primary dashboard then acts as an authenticated HTTP and WebSocket proxy across your fleet. Use TLS, a VPN, or a private network for any untrusted link. Each node still uses its local Docker socket (see Quick start), but Sencho does not require SSH and does not expose a remote Docker socket on the network. For nodes behind NAT or strict firewalls, the Pilot Agent establishes a single outbound WebSocket tunnel to the primary, so the remote host opens no inbound port at all.
-Most capabilities are free in the Community tier. A few advanced governance, security, and fleet-control features ship in the paid Admiral tier; pricing lives at [sencho.io/pricing](https://sencho.io/pricing).
-
-## What Sencho is not (yet)
-
-Sencho is a Docker Compose control plane focused on homelab and small-fleet operators. It is intentionally not:
-
-- A Kubernetes scheduler or replacement.
-- A reverse proxy. Front Sencho with your existing proxy (Caddy, Traefik, nginx) for TLS and authentication on the public edge.
-- A monitoring stack. Sencho surfaces container and host metrics in the dashboard but does not replace Prometheus, Grafana, or your existing alerting pipeline.
-- A CI / CD pipeline. Use webhooks, the API, or Git-sourced stacks to connect Sencho to your build system.
-
-See [KNOWN_LIMITATIONS.md](KNOWN_LIMITATIONS.md) for the current limitation list.
+Sencho is free, open-source software under AGPLv3. Everything below is included in the Community tier with unlimited nodes and users.
---
-**Tier coverage:** All bullets below are available in the free Community tier unless marked `(Admiral)`. Full breakdown at [sencho.io/pricing](https://sencho.io/pricing).
-
## Capabilities
### Stacks
- Full Compose lifecycle: create, deploy, restart, stop, pull
-- Monaco editor with diff preview before save and one-click rollback
+- Atomic deployments with automatic rollback on failure
+- Monaco editor with diff preview before save and one-click rollback to any prior deploy
- [Health-gated updates](https://docs.sencho.io/features/health-gated-updates) that hold a rollout until health checks pass, with stalled-update detection and in-app recovery
- [Git-sourced stacks](https://docs.sencho.io/features/git-sources) pulled and synced from any repository, with ordered multi-file Compose
- [File explorer](https://docs.sencho.io/features/stack-file-explorer) for compose, env, and supporting files, with move and rename across directories
@@ -74,7 +62,7 @@ See [KNOWN_LIMITATIONS.md](KNOWN_LIMITATIONS.md) for the current limitation list
- Aggregated [log search and stream](https://docs.sencho.io/features/global-observability) across every container in the fleet
- Live container stats, health checks, and image-update notifications on a configurable cadence, with links from each image to its registry and source
- Threshold alerts for CPU, memory, and network
-- Read-only [audit log](https://docs.sencho.io/features/audit-log) of every action **(Admiral)**
+- Read-only [audit log](https://docs.sencho.io/features/audit-log) of every action, with a 14-day recent-activity window
- [Network topology](https://docs.sencho.io/features/fleet-view) view of containers, networks, and nodes
- Documentation-drift flags when a [stack dossier](https://docs.sencho.io/features/stack-dossier) diverges from the running stack
@@ -82,6 +70,10 @@ See [KNOWN_LIMITATIONS.md](KNOWN_LIMITATIONS.md) for the current limitation list
- Multi-node management via authenticated HTTP and WebSocket proxy
- [Fleet view](https://docs.sencho.io/features/fleet-view) with grid and topology layouts
- [Fleet snapshots](https://docs.sencho.io/features/fleet-backups) of compose and env across the fleet
+- [Fleet Federation](https://docs.sencho.io/features/fleet-federation): cordon nodes and pin Blueprints to specific hosts
+- [Fleet Actions](https://docs.sencho.io/features/fleet-actions): bulk label operations, fleet-wide stop-by-label, and fleet-wide prune
+- [Fleet Dossier](https://docs.sencho.io/features/fleet-dossier): export the whole fleet as a single browsable Markdown archive
+- Node labels and grouping
- [Pilot Agent](https://docs.sencho.io/features/pilot-agent) for nodes behind NAT or strict firewalls
- Node compatibility checks before deploying
@@ -91,22 +83,20 @@ See [KNOWN_LIMITATIONS.md](KNOWN_LIMITATIONS.md) for the current limitation list
- [Scheduled operations](https://docs.sencho.io/features/scheduled-operations) on cron
- [Webhooks](https://docs.sencho.io/features/webhooks) on stack lifecycle events
- [Blueprints](https://docs.sencho.io/features/blueprint-model): declarative fleet templates with drift detection
-- Encrypted [Fleet Secrets](https://docs.sencho.io/features/fleet-secrets) pushed to labeled nodes **(Admiral)**
### Security
-- [SSO](https://docs.sencho.io/features/sso): custom OIDC, presets for Google, GitHub, and Okta, plus LDAP and Active Directory
+- [SSO](https://docs.sencho.io/features/sso): custom OIDC and presets for Google, GitHub, and Okta
- [Two-factor authentication](https://docs.sencho.io/features/two-factor-authentication) with TOTP and backup codes
-- [RBAC](https://docs.sencho.io/features/rbac) with admin (full control) and viewer (read-only) roles; deployer, node-admin, and auditor roles plus scoped permissions **(Admiral)**
+- [RBAC](https://docs.sencho.io/features/rbac) with admin (full control) and viewer (read-only) roles
- [Security overview](https://docs.sencho.io/features/security) with a chart-led scan summary, sortable images, and searchable scan history
-- [Vulnerability scanning](https://docs.sencho.io/features/vulnerability-scanning) via Trivy on every tier, with on-demand node-wide scans and VEX-based suppression; SARIF export and SBOM upload **(Admiral)**
+- [Vulnerability scanning](https://docs.sencho.io/features/vulnerability-scanning) via Trivy, with on-demand node-wide scans, VEX-based suppression, SARIF export, and SBOM upload
- [Compose network inspector](https://docs.sencho.io/features/compose-networking) with an exposure-intent guard for unintended published ports
-- Scan policy packs for reusable security rules **(Admiral)**
-- [Private registries](https://docs.sencho.io/features/private-registries) and [deploy enforcement](https://docs.sencho.io/features/deploy-enforcement) for non-compliant images **(Admiral)**
+- Scan policy packs for reusable security rules
+- [Private registries](https://docs.sencho.io/features/private-registries) for Docker Hub, GHCR, and custom registries, plus [deploy enforcement](https://docs.sencho.io/features/deploy-enforcement) for non-compliant images
- [API tokens](https://docs.sencho.io/features/api-tokens) for automation
### Operations
-- [Host console](https://docs.sencho.io/features/host-console) in the browser **(Admiral)**
-- Off-site stack archives via custom S3 (every tier) or [Sencho Cloud Backup](https://docs.sencho.io/operations/backup) **(Admiral)** for managed storage
+- Off-site stack archives via [custom S3-compatible storage](https://docs.sencho.io/operations/backup)
- [Notification routing](https://docs.sencho.io/features/alerts-notifications#notification-routing) to Slack, Discord, email, and webhooks
- [Global search](https://docs.sencho.io/features/global-search) across stacks, containers, and services
- [Resources view](https://docs.sencho.io/features/resources) for images, volumes, and networks with scoped prune actions
@@ -181,18 +171,27 @@ See the [multi-node guide](https://docs.sencho.io/features/multi-node) for the f
|---|---|
|  |  |
|  |  |
+|  |  |
+|  |  |
---
## Telemetry and data handling
-Sencho does not emit telemetry, analytics, or crash reports. The only outbound traffic is license validation against Lemon Squeezy, and only when a paid license key is activated. Community-tier instances make no outbound calls to Sencho-controlled endpoints. Stack metadata, container inventory, and user activity never leave your instance.
+Sencho does not emit telemetry, analytics, or crash reports, and makes no outbound calls to Sencho-controlled endpoints. Stack metadata, container inventory, and user activity never leave your instance.
+
+---
+
+## Admiral
+
+**Admiral** is Studio Saelix's paid business assurance plan on top of everything in Community: priority support, managed continuity (Sencho Cloud Backup), governance depth (advanced RBAC roles, LDAP / Active Directory, full audit log export and anomaly detection), and cross-node Fleet Sync policy replication. AWS ECR registry credentials currently require Admiral as well. See [sencho.io/pricing](https://sencho.io/pricing) for current plan details.
---
## Documentation, community, and license
- **Documentation:** [docs.sencho.io](https://docs.sencho.io)
+- **Known limitations:** [KNOWN_LIMITATIONS.md](KNOWN_LIMITATIONS.md)
- **If something breaks:** the [Recovery guide](https://docs.sencho.io/operations/recovery) covers getting back to a working state when Sencho, a deploy, sign-in, Docker, or a node fails.
- **Community:** [GitHub Discussions](https://github.com/studio-saelix/sencho/discussions)
- **Contributing:** [CONTRIBUTING.md](CONTRIBUTING.md)
diff --git a/docs/features/overview.mdx b/docs/features/overview.mdx
index 8fd48a0b..7ed5fca5 100644
--- a/docs/features/overview.mdx
+++ b/docs/features/overview.mdx
@@ -152,7 +152,7 @@ Track mutating actions across your Sencho instance with a searchable trail: who
## Fleet management
-
+
### Multi-node support
@@ -165,7 +165,7 @@ Add remote nodes behind NAT, residential networks, or corporate firewalls withou
### Sencho Mesh
-Connect containers across nodes by hostname over the Pilot tunnel so a multi-node fleet feels like one machine. Opt a stack into the mesh and its services become reachable from any other meshed stack at a stable hostname. Admiral. [Learn more →](/features/sencho-mesh)
+Connect containers across nodes by hostname over the Pilot tunnel so a multi-node fleet feels like one machine. Opt a stack into the mesh and its services become reachable from any other meshed stack at a stable hostname. Limited availability; requires Admiral when enabled on an instance. [Learn more →](/features/sencho-mesh)
### Fleet View
@@ -189,7 +189,7 @@ When several Sencho instances run as a fleet, the control instance is the source
### Fleet Secrets
-Centralized, encrypted, versioned env-var bundles you push to labeled nodes' stacks. Every save bumps a version, and every push records a per-node diff in the audit log using overlay merge semantics. Admiral. [Learn more →](/features/fleet-secrets)
+Centralized, encrypted, versioned env-var bundles you push to labeled nodes' stacks. Every save bumps a version, and every push records a per-node diff in the audit log using overlay merge semantics. Limited availability; requires Admiral and the admin role when enabled on an instance. [Learn more →](/features/fleet-secrets)
### Fleet-wide backups
@@ -205,7 +205,7 @@ When you manage nodes running different Sencho versions, the dashboard detects e
### Host console
-Open an interactive terminal on the host OS directly in the browser with full xterm.js emulation and color support. No SSH client required; admin-only. [Learn more →](/features/host-console)
+Open an interactive terminal on the host OS directly in the browser with full xterm.js emulation and color support. No SSH client required. Limited availability; requires Admiral and the admin role when enabled on an instance. [Learn more →](/features/host-console)
## Security and access
diff --git a/docs/images/dashboard-dark.png b/docs/images/dashboard-dark.png
index 8620fa5a..ad45baaa 100644
Binary files a/docs/images/dashboard-dark.png and b/docs/images/dashboard-dark.png differ
diff --git a/docs/images/dashboard-light.png b/docs/images/dashboard-light.png
index f2de7c82..33daebf2 100644
Binary files a/docs/images/dashboard-light.png and b/docs/images/dashboard-light.png differ
diff --git a/docs/images/editor.png b/docs/images/editor.png
index 97dde02c..a2bb5bad 100644
Binary files a/docs/images/editor.png and b/docs/images/editor.png differ
diff --git a/docs/images/fleet.png b/docs/images/fleet.png
index 649c5770..b3533363 100644
Binary files a/docs/images/fleet.png and b/docs/images/fleet.png differ
diff --git a/docs/images/logs.png b/docs/images/logs.png
index 6522fa13..0f45637b 100644
Binary files a/docs/images/logs.png and b/docs/images/logs.png differ
diff --git a/docs/images/overview/blueprint-deployments.png b/docs/images/overview/blueprint-deployments.png
new file mode 100644
index 00000000..2b938f9b
Binary files /dev/null and b/docs/images/overview/blueprint-deployments.png differ
diff --git a/docs/images/overview/compose-doctor.png b/docs/images/overview/compose-doctor.png
new file mode 100644
index 00000000..99cf8d26
Binary files /dev/null and b/docs/images/overview/compose-doctor.png differ
diff --git a/docs/images/overview/fleet-topology.png b/docs/images/overview/fleet-topology.png
index 55fa8257..b3533363 100644
Binary files a/docs/images/overview/fleet-topology.png and b/docs/images/overview/fleet-topology.png differ
diff --git a/docs/images/overview/scheduled-operations.png b/docs/images/overview/scheduled-operations.png
new file mode 100644
index 00000000..58945bd9
Binary files /dev/null and b/docs/images/overview/scheduled-operations.png differ
diff --git a/docs/images/overview/security-overview.png b/docs/images/overview/security-overview.png
index b5c836a9..508da2dd 100644
Binary files a/docs/images/overview/security-overview.png and b/docs/images/overview/security-overview.png differ
diff --git a/docs/images/stacks.png b/docs/images/stacks.png
index a7365d93..9ad8876a 100644
Binary files a/docs/images/stacks.png and b/docs/images/stacks.png differ