On this page
What Enterprise adds#
The Enterprise Edition is the Community Edition plus the capabilities below. An install is the Community Edition unless it holds a verified licence key (licence.md). This page extends Editions in the Community guide.
Community and Enterprise side by side#
| Community | Enterprise | |
|---|---|---|
| Cloud accounts | 1 | no limit |
| Resources per scan | 1,000 | no limit |
| Active remediation policies | 3 | no limit |
| Retention | 30 days | no limit |
| Remediation | Preview: a plan is written and shown, nothing is changed | Autopilot: changes within policy are carried out without a person |
| Approval requests | Shown, not mailed | Mailed, reminded and escalated (mailed-approvals.md) |
| Ticketing (Jira, ServiceNow) | no | yes |
| Single sign-on (OIDC) | no | yes (sso.md) |
| Ingestors: AWS, Azure, GCP | yes | yes |
| Ingestor: Kubernetes | no (it comes with Pro and Enterprise) | yes |
| Ingestors: Databricks, Snowflake, AI platforms | no | yes (ingestors.md) |
| Realized-savings verification | no | yes |
| Finance-grade audit trail | no | yes |
Azure and GCP are in the Community Edition: what an edition limits is how many cloud accounts it connects, not which cloud.
Read this before you rely on a row#
The table is what the licence allows. It is not a statement that every row is built in the 0.9.0 beta.
- Execution is planned. In 0.9.0 Hyvop opens no ticket in any edition, and the Community guide says that Hyvop does not change or delete resources: remediation is a plan a person reviews and applies. Read Remediation and Ticketing for what the screens show.
- Not every ingestor is installed by the chart. See ingestors.md.
- The finance-grade audit trail (tamper evidence, retention rules, export to a SIEM) is Enterprise only. The Audit page of the Community guide says what Hyvop records today.
The four tiers#
The Starter and Pro tiers lie between the two.
| 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.
What stays the same#
The chart, the way it is installed, the permission model, the API and the model settings are not edition-specific. What an edition changes is the table above.
How the limits show up#
- Connecting a second cloud account while one is on is refused in the Community Edition, and so is switching a second on.
- Jira and ServiceNow are refused by core in the Community Edition, naming the plan that has them.
- Switching an integration off is always allowed, so an install whose licence ended can stop what it can no longer use.