Editions#
An install is the Community Edition unless it holds a verified licence key. Core decides what an install may do from one
table; the UI asks core (GET /api/entitlements) and keeps no copy.
Licence#
Hyvop is proprietary software. The Community edition is free to use. The source code is not published.
What the Community Edition includes#
| Community | |
|---|---|
| Cloud accounts | One, on AWS, Azure or GCP. A second is refused while the first is on |
| Resources | 1,000 per scan, counted across all services and regions. A scan that stops there says so above every screen |
| Remediation policies | 3 active. Those already active stay; a fourth cannot be switched on |
| Retention | 30 days of metrics |
| Remediation | Preview: a plan is written and shown; nothing is changed in the cloud account |
| Approval requests | Shown, not sent: the plan names whom it would ask and no mail, reminder or escalation goes out. Answers on the screen count (approvals.md) |
| Azure and GCP | Included. What an edition limits is how many accounts it connects, not which cloud |
| Model for the AI features | Included: the install's model, or one an organisation brings itself (models.md) |
| Ticketing (Jira, ServiceNow) | Not included |
| Single sign-on (OIDC) | Not included: Enterprise only |
| Kubernetes | Not included: it comes with Pro and Enterprise |
| Databricks, Snowflake and AI platforms | Not included: they come with the Enterprise ingestors |
| Realized-savings verification, finance-grade audit trail | Not included: Enterprise only |
The whole table#
| Community | Starter | Pro | Enterprise | |
|---|---|---|---|---|
| Cloud accounts | 1 | 1 | no limit | no limit |
| Resources per scan | 1,000 | 5,000 | 30,000 | no limit |
| Active remediation policies | 3 | no limit | no limit | no limit |
| Retention (days) | 30 | 365 | 365 | no limit |
| Remediation mode | Preview | Assisted | Assisted | Autopilot |
| Model of an organisation's own | yes | yes | yes | yes |
| Ticketing (Jira, ServiceNow) | no | no | yes | yes |
| Remediation beyond preview | no | yes | yes | yes |
| Approval requests mailed | no, shown only | yes | yes | yes |
| Single sign-on | no | no | no | yes |
| Ingestors: AWS, Azure, GCP | yes | yes | yes | yes |
| Ingestor: Kubernetes | no | no | yes | yes |
| Ingestors: Databricks, Snowflake, AI platforms | no | no | no | yes |
| Realized-savings verification | no | no | no | yes |
| Finance-grade audit trail | no | no | no | yes |
The modes are: Preview, a plan is written and shown and nothing is changed in the cloud account; Assisted, a person approves and Hyvop helps carry it out; Autopilot, changes within policy are carried out without a person.
How the limits show up#
- Connecting a second cloud account while one is on is refused, and so is switching a second on.
- Jira and ServiceNow are refused in the Community Edition, naming the plan that has them. Single sign-on set in a Community install does not stop it: people sign in with their e-mail and password, and the sign-in page says why.
- Switching an integration off is always allowed, so an install whose licence ended can stop what it can no longer use.
Upgrading from an older chart enforces these limits at the first start: see upgrade.md.