mirror of
https://github.com/Studio-Saelix/sencho.git
synced 2026-07-26 20:00:08 +00:00
Anso
865d792874
* feat(pricing): collapse to two tiers (Community + Admiral) Collapse Sencho's pricing from three tiers (Community / Skipper / Admiral) to two: a generous free Community tier and a single paid Admiral tier. The Skipper tier is removed. Now free in Community: auto-heal, auto-update, scheduled operations, webhooks, notification routing, Fleet Actions and bulk operations, SSO preset providers (Google / GitHub / Okta), unlimited users with admin and viewer roles, and deploy safety (atomic deploys, auto-rollback, and one-click rollback). Admiral (paid) is focused on running and governing a fleet: blueprints, Fleet Secrets, deploy enforcement, vulnerability report export, audit log, host console, private registries, mesh networking, node cordon, managed cloud backup, LDAP / Active Directory SSO, and the advanced RBAC roles (deployer, node-admin, auditor) with per-resource scoped assignments. Internally the license variant distinction is removed so tier is binary (community / paid). License validation still verifies the Lemon Squeezy store and product before granting paid status. Docs and the contributor guide are updated to the two-tier model. * docs(pricing): correct licensing page to two-tier pricing and tidy stale tier wording The licensing docs page kept the old Admiral pricing plus a Founder Lifetime column and an Enterprise paragraph after the two-tier collapse. Update it to $12/month or $99/year, drop the lifetime and Enterprise content, and link to the pricing page for current pricing. Also fix stale "Skipper" wording in CLA.md, SUPPORT.md, one test title, and three test comments. Historical CHANGELOG entries and the retired-Skipper license-guard test are intentionally left as-is. * docs: align licensing and SSO pages with the two-tier model Correct the SSO overview so the Google, GitHub, and Okta presets read as available on every tier, matching the provider table; only LDAP and Active Directory require Sencho Admiral. Remove the lifetime-plan references from the licensing, settings, and troubleshooting pages so they reflect subscription-only Admiral pricing. * fix(rbac): omit scoped permissions from /me on the Community tier Scoped role assignments only take effect on the paid tier, but GET /api/permissions/me returned them unconditionally, so a downgraded instance with leftover assignments rendered per-resource affordances the API then rejected with 403. The endpoint now mirrors the permission middleware and includes scoped permissions only on the paid tier. Adds a regression test covering the downgrade case. * docs: use custom-pricing wording on the contact page The two-tier model has no Enterprise tier; reword the contact page's enterprise pricing/deals to custom pricing/deals so it does not imply a tier that no longer exists.
69 lines
3.1 KiB
Plaintext
69 lines
3.1 KiB
Plaintext
---
|
|
title: Contact & Support
|
|
description: Official contact channels for support, licensing, security, privacy, and general inquiries.
|
|
---
|
|
|
|
Sencho provides dedicated email channels for different types of inquiries. Use the channel that best matches your need so your message reaches the right team.
|
|
|
|
## Support
|
|
|
|
<Card title="support@sencho.io" icon="life-ring" href="mailto:support@sencho.io">
|
|
Technical support, how-to questions, and troubleshooting help. Available to Admiral license holders via **Settings > Help & Support** in the app.
|
|
</Card>
|
|
|
|
Community users can get help through the [Documentation](https://docs.sencho.io) and [GitHub Issues](https://github.com/studio-saelix/sencho/issues).
|
|
|
|
## General inquiries
|
|
|
|
<Card title="contact@sencho.io" icon="envelope" href="mailto:contact@sencho.io">
|
|
General inquiries, partnership proposals, and media requests. Found in the website footer under **Community > Contact**.
|
|
</Card>
|
|
|
|
## Licensing
|
|
|
|
<Card title="licensing@sencho.io" icon="key" href="mailto:licensing@sencho.io">
|
|
License activation issues, upgrade questions, custom pricing, refund requests, and alternative licensing arrangements.
|
|
</Card>
|
|
|
|
This address appears in:
|
|
- The [LICENSE](https://github.com/studio-saelix/sencho/blob/main/LICENSE) file for alternative licensing inquiries
|
|
- Upgrade prompts inside the app (paywall screens)
|
|
- The [Refund Policy](https://sencho.io/refund) and pricing section on the website
|
|
|
|
## Security
|
|
|
|
<Card title="security@sencho.io" icon="shield" href="mailto:security@sencho.io">
|
|
Vulnerability reports, security incidents, and bug bounty submissions. **Do not open a public issue for security vulnerabilities.**
|
|
</Card>
|
|
|
|
You can also use [GitHub private vulnerability reporting](https://github.com/studio-saelix/sencho/security/advisories/new). Both the app and the website publish a `/.well-known/security.txt` file that points to this address.
|
|
|
|
See the full [Security Policy](https://github.com/studio-saelix/sencho/blob/main/SECURITY.md) for response times and disclosure guidelines.
|
|
|
|
## Privacy
|
|
|
|
<Card title="privacy@sencho.io" icon="lock" href="mailto:privacy@sencho.io">
|
|
GDPR data requests, CCPA inquiries, Terms of Service questions, and DMCA claims.
|
|
</Card>
|
|
|
|
This address is listed in the [Privacy Policy](https://sencho.io/privacy) and [Terms of Service](https://sencho.io/terms) on the website.
|
|
|
|
## Community conduct
|
|
|
|
<Card title="conduct@sencho.io" icon="users" href="mailto:conduct@sencho.io">
|
|
Reports of Code of Conduct violations in any Sencho community space.
|
|
</Card>
|
|
|
|
All reports are reviewed promptly and handled with confidentiality. See the [Code of Conduct](https://github.com/studio-saelix/sencho/blob/main/CODE_OF_CONDUCT.md) for details.
|
|
|
|
## Summary
|
|
|
|
| Email | When to use |
|
|
|-------|-------------|
|
|
| `support@sencho.io` | Technical help (Admiral) |
|
|
| `contact@sencho.io` | General inquiries, partnerships, media |
|
|
| `licensing@sencho.io` | Upgrades, custom deals, refunds, license issues |
|
|
| `security@sencho.io` | Vulnerability reports, security incidents |
|
|
| `privacy@sencho.io` | GDPR/CCPA requests, legal, DMCA |
|
|
| `conduct@sencho.io` | Code of Conduct violations |
|