mirror of
https://github.com/Studio-Saelix/sencho.git
synced 2026-08-11 19:26:56 +00:00
refactor: rename Personal Pro to Skipper and Team Pro to Admiral (#256)
Align paid tier names with Sencho's nautical identity. Internal variant
values ('personal'/'team') remain unchanged in code, database, and
Lemon Squeezy integration — only user-facing display names updated.
- Backend: requireTeamPro → requireAdmiral, TEAM_PRO_REQUIRED → ADMIRAL_REQUIRED
- Frontend: TeamProGate.tsx → AdmiralGate.tsx, TierBadge labels updated
- Website: PricingSection tier names and nautical descriptions
- Docs: all 11 affected pages renamed, nautical footnote added to licensing
This commit is contained in:
Anso
@@ -4,7 +4,7 @@ description: Generate scoped API tokens for CI/CD pipelines, scripts, and automa
|
||||
---
|
||||
|
||||
<Note>
|
||||
API Tokens require a Sencho **Team Pro** license. Personal Pro and Community Edition do not include this feature.
|
||||
API Tokens require a Sencho **Admiral** license. Skipper and Community Edition do not include this feature.
|
||||
</Note>
|
||||
|
||||
API tokens let you authenticate external tools - CI/CD pipelines, deployment scripts, monitoring integrations - without sharing user credentials. Each token is scoped to a specific permission level so you can follow the principle of least privilege.
|
||||
@@ -39,7 +39,7 @@ These restrictions ensure that API tokens cannot escalate privileges or modify t
|
||||
|
||||
## Creating a token
|
||||
|
||||
1. Open **Settings Hub** and navigate to the **API Tokens** tab (visible to Team Pro admins only).
|
||||
1. Open **Settings Hub** and navigate to the **API Tokens** tab (visible to Admiral admins only).
|
||||
2. Click **Create Token**.
|
||||
3. Enter a descriptive name (e.g., "GitHub Actions deploy"), select a permission scope, and optionally choose an expiration period (30, 60, 90 days, or 1 year). Tokens without an expiration must be revoked manually.
|
||||
4. Click **Create**. The raw token is displayed **once** - copy it immediately.
|
||||
|
||||
@@ -4,10 +4,10 @@ description: Track all mutating actions across your Sencho instance with a searc
|
||||
---
|
||||
|
||||
<Note>
|
||||
The Audit Log requires a Sencho **Team Pro** license. Personal Pro and Community Edition do not include this feature.
|
||||
The Audit Log requires a Sencho **Admiral** license. Skipper and Community Edition do not include this feature.
|
||||
</Note>
|
||||
|
||||
Sencho Team Pro records every mutating action (deploy, stop, delete, settings changes, user management) with full attribution. The audit log answers the question every team eventually asks: **"Who changed what, and when?"**
|
||||
Sencho Admiral records every mutating action (deploy, stop, delete, settings changes, user management) with full attribution. The audit log answers the question every team eventually asks: **"Who changed what, and when?"**
|
||||
|
||||
## What gets logged
|
||||
|
||||
@@ -36,7 +36,7 @@ Every `POST`, `PUT`, `DELETE`, and `PATCH` request to the Sencho API is automati
|
||||
|
||||
## Viewing the audit log
|
||||
|
||||
Navigate to the **Audit** tab in the sidebar (visible to Team Pro admins only).
|
||||
Navigate to the **Audit** tab in the sidebar (visible to Admiral admins only).
|
||||
|
||||
<Frame>
|
||||
<img src="/images/audit-log.png" alt="Audit Log view showing a timeline of actions" />
|
||||
|
||||
@@ -5,19 +5,23 @@ description: How Sencho Pro licensing works - trials, activation, and subscripti
|
||||
|
||||
Sencho uses an open-core model. The **Community** tier is free forever with unlimited nodes. **Pro** unlocks advanced features like fleet management, RBAC, webhooks, atomic deployments, and fleet-wide backups.
|
||||
|
||||
<Tip>
|
||||
*Our tier names are inspired by the meaning of Sencho (船長) — because you're the captain of your container fleet.*
|
||||
</Tip>
|
||||
|
||||
## Plans
|
||||
|
||||
| Tier | Price | Accounts |
|
||||
|------|-------|----------|
|
||||
| **Community** | Free | 1 admin |
|
||||
| **Personal Pro** | $7.99/month, $69.99/year, or $249 lifetime | 1 admin + 3 viewers |
|
||||
| **Team Pro** | $49.99/month, $499.99/year, or $1,499 lifetime | Unlimited |
|
||||
| **Skipper** | $7.99/month, $69.99/year, or $249 lifetime | 1 admin + 3 viewers |
|
||||
| **Admiral** | $49.99/month, $499.99/year, or $1,499 lifetime | Unlimited |
|
||||
|
||||
Lifetime pricing is an early-adopter offer available for a limited time only.
|
||||
|
||||
## Free trial
|
||||
|
||||
Every new Sencho installation starts with a **14-day Personal Pro trial** - no license key or credit card required. Personal Pro features like fleet management, RBAC viewer accounts, webhooks, and atomic deployments are unlocked during the trial so you can evaluate them with your real infrastructure. Team Pro features (SSO, audit log, unlimited accounts) require a Team Pro license.
|
||||
Every new Sencho installation starts with a **14-day Skipper trial** - no license key or credit card required. Skipper features like fleet management, RBAC viewer accounts, webhooks, and atomic deployments are unlocked during the trial so you can evaluate them with your real infrastructure. Admiral features (SSO, audit log, unlimited accounts) require an Admiral license.
|
||||
|
||||
When the trial expires, Sencho automatically reverts to the Community tier. No data is lost.
|
||||
|
||||
@@ -25,14 +29,14 @@ When the trial expires, Sencho automatically reverts to the Community tier. No d
|
||||
|
||||
You can upgrade directly from **Settings > License** in your Sencho dashboard. The upgrade cards shown depend on your current tier:
|
||||
|
||||
- **Community users** see both **Personal Pro** and **Team Pro** options with feature highlights and direct checkout links.
|
||||
- **Personal Pro users** see a **Team Pro** upgrade card for when you need unlimited accounts.
|
||||
- **Team Pro users** are on the highest tier - no upgrade cards are shown.
|
||||
- **Community users** see both **Skipper** and **Admiral** options with feature highlights and direct checkout links.
|
||||
- **Skipper users** see an **Admiral** upgrade card for when you need unlimited accounts.
|
||||
- **Admiral users** are on the highest tier - no upgrade cards are shown.
|
||||
|
||||
Clicking an upgrade button opens the Lemon Squeezy checkout in a new tab. After completing the purchase, you'll receive a license key by email.
|
||||
|
||||
<Frame>
|
||||
<img src="/images/license-settings.png" alt="License settings showing upgrade cards for Personal Pro and Team Pro" />
|
||||
<img src="/images/license-settings.png" alt="License settings showing upgrade cards for Skipper and Admiral" />
|
||||
</Frame>
|
||||
|
||||
## Activating your license
|
||||
|
||||
@@ -69,11 +69,11 @@ Create point-in-time snapshots of every compose file and environment file across
|
||||
|
||||
## Private registries
|
||||
|
||||
Store credentials for private Docker registries - Docker Hub organizations, GHCR, AWS ECR, and self-hosted registries. Sencho injects them automatically during deploy and pull operations. ECR short-lived tokens are refreshed on every operation. Team Pro only. [Learn more →](/features/private-registries)
|
||||
Store credentials for private Docker registries - Docker Hub organizations, GHCR, AWS ECR, and self-hosted registries. Sencho injects them automatically during deploy and pull operations. ECR short-lived tokens are refreshed on every operation. Admiral only. [Learn more →](/features/private-registries)
|
||||
|
||||
## Audit log
|
||||
|
||||
Track every mutating action across your Sencho instance with a searchable audit trail. See who deployed, stopped, deleted, or changed settings - with timestamps, user attribution, and node context. Team Pro only. [Learn more →](/features/audit-log)
|
||||
Track every mutating action across your Sencho instance with a searchable audit trail. See who deployed, stopped, deleted, or changed settings - with timestamps, user attribution, and node context. Admiral only. [Learn more →](/features/audit-log)
|
||||
|
||||
## Licensing & billing
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ description: Store credentials for private Docker registries so Sencho can autom
|
||||
---
|
||||
|
||||
<Note>
|
||||
Private Registry Management requires a Sencho **Team Pro** license. Personal Pro and Community Edition do not include this feature.
|
||||
Private Registry Management requires a Sencho **Admiral** license. Skipper and Community Edition do not include this feature.
|
||||
</Note>
|
||||
|
||||
Sencho can store credentials for your private Docker registries and inject them automatically whenever it runs `docker compose pull` or `docker compose up`. This means your stacks can reference private images without needing to manually `docker login` on the host.
|
||||
@@ -20,7 +20,7 @@ Sencho can store credentials for your private Docker registries and inject them
|
||||
|
||||
## Adding a registry
|
||||
|
||||
1. Open **Settings Hub** and navigate to the **Registries** tab (visible to Team Pro admins only).
|
||||
1. Open **Settings Hub** and navigate to the **Registries** tab (visible to Admiral admins only).
|
||||
2. Click **Add Registry**.
|
||||
3. Select the registry type. The URL field auto-fills with the standard endpoint for Docker Hub and GHCR.
|
||||
4. Enter a descriptive name, the registry URL, and your credentials.
|
||||
@@ -107,7 +107,7 @@ AWS ECR uses short-lived authentication tokens (valid for 12 hours) derived from
|
||||
- **No persistent Docker login** - Credentials are written to a temporary file for the duration of each operation and immediately deleted afterward.
|
||||
- **Secrets never exposed** - The API never returns decrypted secrets. The UI shows only whether a secret is stored.
|
||||
- **Audit trail** - Registry create, update, and delete operations are recorded in the [Audit Log](/features/audit-log).
|
||||
- **Admin-only access** - Only admin users with a Team Pro license can manage registry credentials.
|
||||
- **Admin-only access** - Only admin users with a Admiral license can manage registry credentials.
|
||||
|
||||
## Multi-node behavior
|
||||
|
||||
|
||||
+11
-11
@@ -4,10 +4,10 @@ description: Role-based access control for Sencho - manage admin, viewer, deploy
|
||||
---
|
||||
|
||||
<Note>
|
||||
Multi-user support requires a Sencho Pro license. Community Edition supports a single admin account only. Intermediate roles (Deployer, Node Admin) and scoped permissions require **Team Pro**.
|
||||
Multi-user support requires a Sencho Pro license. Community Edition supports a single admin account only. Intermediate roles (Deployer, Node Admin) and scoped permissions require **Admiral**.
|
||||
</Note>
|
||||
|
||||
Sencho supports role-based access control with four distinct roles. The classic **Admin** and **Viewer** roles are available on all Pro tiers, while **Deployer** and **Node Admin** are exclusive to Team Pro and support scoped permissions per stack or node.
|
||||
Sencho supports role-based access control with four distinct roles. The classic **Admin** and **Viewer** roles are available on all Pro tiers, while **Deployer** and **Node Admin** are exclusive to Admiral and support scoped permissions per stack or node.
|
||||
|
||||
## Roles
|
||||
|
||||
@@ -15,8 +15,8 @@ Sencho supports role-based access control with four distinct roles. The classic
|
||||
|------|-------------|------|
|
||||
| **Admin** | Full access to all features — deploy, edit, manage users, configure nodes, and more | Pro |
|
||||
| **Viewer** | Read-only access to dashboards, logs, stats, and file contents | Pro |
|
||||
| **Deployer** | Can deploy, restart, stop, and start stacks — but cannot edit compose files, delete stacks, or access system settings | Team Pro |
|
||||
| **Node Admin** | Full stack and node management within their scope — cannot access system settings, users, or license management | Team Pro |
|
||||
| **Deployer** | Can deploy, restart, stop, and start stacks — but cannot edit compose files, delete stacks, or access system settings | Admiral |
|
||||
| **Node Admin** | Full stack and node management within their scope — cannot access system settings, users, or license management | Admiral |
|
||||
|
||||
### Permission matrix
|
||||
|
||||
@@ -39,7 +39,7 @@ Sencho supports role-based access control with four distinct roles. The classic
|
||||
## Scoped permissions
|
||||
|
||||
<Note>
|
||||
Scoped permissions require a **Team Pro** license.
|
||||
Scoped permissions require a **Admiral** license.
|
||||
</Note>
|
||||
|
||||
Roles can be scoped to specific stacks or nodes. This means you can grant a user the **Deployer** role globally, but also give them **Node Admin** access on a specific node — or limit a viewer to deploy access on only certain stacks.
|
||||
@@ -64,15 +64,15 @@ Admins can manage accounts in **Settings → Users**. From there you can:
|
||||
- **Edit** an existing user's password or role
|
||||
- **Delete** a user account
|
||||
|
||||
When creating or editing a user on Team Pro, you'll see all four role options in the role selector. On Personal Pro, only Admin and Viewer are available.
|
||||
When creating or editing a user on Admiral, you'll see all four role options in the role selector. On Skipper, only Admin and Viewer are available.
|
||||
|
||||
<Frame>
|
||||
<img src="/images/rbac/role-selector-dropdown.png" alt="Role selector showing all four roles on Team Pro" />
|
||||
<img src="/images/rbac/role-selector-dropdown.png" alt="Role selector showing all four roles on Admiral" />
|
||||
</Frame>
|
||||
|
||||
## Managing scoped permissions
|
||||
|
||||
When editing a user on Team Pro, a **Scoped Permissions** section appears below the user form. Here you can:
|
||||
When editing a user on Admiral, a **Scoped Permissions** section appears below the user form. Here you can:
|
||||
|
||||
1. **View** the user's current scoped assignments
|
||||
2. **Add** a new scope by selecting a role, resource type (stack or node), and specific resource
|
||||
@@ -82,7 +82,7 @@ Each scoped assignment grants the specified role's permissions on the specified
|
||||
|
||||
## SSO auto-provisioning
|
||||
|
||||
With a Team Pro license, users can also be created automatically when they log in via SSO (LDAP, Google, GitHub, or Okta). SSO users appear in the Users list alongside local accounts. They are assigned a role based on identity provider group membership or claim mapping.
|
||||
With a Admiral license, users can also be created automatically when they log in via SSO (LDAP, Google, GitHub, or Okta). SSO users appear in the Users list alongside local accounts. They are assigned a role based on identity provider group membership or claim mapping.
|
||||
|
||||
SSO users cannot log in with a password — they must always authenticate through their identity provider. After SSO provisioning, an admin can add scoped permissions to SSO users just like local accounts.
|
||||
|
||||
@@ -97,5 +97,5 @@ When you upgrade to Sencho Pro, your existing single-admin credentials are autom
|
||||
| Tier | Admin accounts | Non-admin accounts | Intermediate roles | Scoped permissions |
|
||||
|------|---------------|-------------------|-------------------|-------------------|
|
||||
| **Community** | 1 | 0 | ❌ | ❌ |
|
||||
| **Personal Pro** | 1 | 3 | ❌ | ❌ |
|
||||
| **Team Pro** | Unlimited | Unlimited | ✅ | ✅ |
|
||||
| **Skipper** | 1 | 3 | ❌ | ❌ |
|
||||
| **Admiral** | Unlimited | Unlimited | ✅ | ✅ |
|
||||
|
||||
@@ -4,8 +4,8 @@ description: Automate recurring Docker operations like stack restarts, fleet sna
|
||||
---
|
||||
|
||||
<Note>
|
||||
Scheduled Operations requires a Sencho **Team Pro** license.
|
||||
Personal Pro and Community Edition do not include this feature.
|
||||
Scheduled Operations requires a Sencho **Admiral** license.
|
||||
Skipper and Community Edition do not include this feature.
|
||||
</Note>
|
||||
|
||||
## Overview
|
||||
@@ -26,7 +26,7 @@ Scheduled Operations lets you automate recurring maintenance tasks across your i
|
||||
|
||||
## Creating a Scheduled Task
|
||||
|
||||
1. Navigate to the **Schedules** tab in the top navigation bar (visible to Team Pro admins).
|
||||
1. Navigate to the **Schedules** tab in the top navigation bar (visible to Admiral admins).
|
||||
2. Click **New Schedule**.
|
||||
3. Fill in the form:
|
||||
- **Name** - a descriptive label (e.g. "Nightly staging restart").
|
||||
@@ -92,7 +92,7 @@ Execution history is retained for 30 days.
|
||||
|
||||
The Scheduler Service runs in the background and checks for due tasks every 60 seconds. When a task's next run time has passed:
|
||||
|
||||
1. The scheduler verifies your Team Pro license is active.
|
||||
1. The scheduler verifies your Admiral license is active.
|
||||
2. It executes the configured action using the same internal services that power the UI buttons (restart, snapshot, prune).
|
||||
3. Results are logged to the execution history.
|
||||
4. The next run time is recalculated from the cron expression.
|
||||
|
||||
@@ -4,10 +4,10 @@ description: Authenticate with your existing identity provider - LDAP, Google, G
|
||||
---
|
||||
|
||||
<Note>
|
||||
SSO requires a Sencho **Team Pro** license. Personal Pro and Community Edition do not include this feature.
|
||||
SSO requires a Sencho **Admiral** license. Skipper and Community Edition do not include this feature.
|
||||
</Note>
|
||||
|
||||
Sencho Team Pro lets your team sign in using existing identity providers instead of managing separate credentials. SSO works **alongside** password authentication - it does not replace it.
|
||||
Sencho Admiral lets your team sign in using existing identity providers instead of managing separate credentials. SSO works **alongside** password authentication - it does not replace it.
|
||||
|
||||
## Supported providers
|
||||
|
||||
@@ -173,7 +173,7 @@ If not set, Sencho auto-detects the URL from the request's `Host` header and pro
|
||||
- **State parameter** - A cryptographic random value protects against CSRF attacks on the OAuth callback
|
||||
- **Encrypted secrets** - LDAP bind passwords and OIDC client secrets are encrypted at rest with AES-256-GCM
|
||||
- **No local password** - SSO users are created with an unusable password hash. They cannot bypass SSO by using the password login form
|
||||
- **Admin-only configuration** - Only Team Pro administrators can enable or configure SSO providers
|
||||
- **Admin-only configuration** - Only Admiral administrators can enable or configure SSO providers
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ When you point `COMPOSE_DIR` at a directory, Sencho expects each stack to live i
|
||||
|
||||
## SSO environment variables
|
||||
|
||||
If you use SSO (Team Pro), configure your identity providers via environment variables:
|
||||
If you use SSO (Admiral), configure your identity providers via environment variables:
|
||||
|
||||
| Variable | Description |
|
||||
|----------|-------------|
|
||||
|
||||
@@ -4,7 +4,7 @@ description: Step-by-step instructions for connecting Sencho to your identity pr
|
||||
---
|
||||
|
||||
<Note>
|
||||
SSO requires a Sencho **Team Pro** license. You can configure SSO via environment variables (shown below) or from the Settings UI after first boot.
|
||||
SSO requires a Sencho **Admiral** license. You can configure SSO via environment variables (shown below) or from the Settings UI after first boot.
|
||||
</Note>
|
||||
|
||||
## Google OIDC
|
||||
|
||||
@@ -39,7 +39,7 @@ Manage your Sencho Pro license from this section.
|
||||
| **Trial status** | If on a trial, shows remaining days |
|
||||
| **Customer / Plan / Key** | Displayed when a Pro license is active |
|
||||
| **Renews** | Next renewal date for active subscriptions |
|
||||
| **Upgrade cards** | Dynamic plan cards with feature highlights and direct Lemon Squeezy checkout links. Community users see Personal Pro and Team Pro; Personal Pro users see Team Pro only |
|
||||
| **Upgrade cards** | Dynamic plan cards with feature highlights and direct Lemon Squeezy checkout links. Community users see Skipper and Admiral; Skipper users see Admiral only |
|
||||
| **Activate** | Enter a license key to activate Pro |
|
||||
| **Manage Subscription** | Opens the billing portal (active Pro only) |
|
||||
| **Deactivate License** | Reverts to Community features (active Pro only) |
|
||||
@@ -196,8 +196,8 @@ Pro license holders get additional support channels:
|
||||
|
||||
| Channel | Description |
|
||||
|---------|-------------|
|
||||
| **Email Support** | Direct email support (Personal Pro) |
|
||||
| **Priority Email Support** | Responses within 24 hours (Team Pro) |
|
||||
| **Email Support** | Direct email support (Skipper) |
|
||||
| **Priority Email Support** | Responses within 24 hours (Admiral) |
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user