Enterprise support for Cozystack is a commercial support contract from Aenix, the open-core company that created and maintains Cozystack and is its largest single contributor. It gives organizations running the open-source platform themselves direct access to the maintainers: architecture review, incident triage and root-cause analysis, upgrade planning and execution, custom feature development against Cozystack, and compliance gap analysis for DORA, NIS2 and sovereignty requirements. It is sold as a monthly retainer, independent of any Ænix platform licence, and is the usual entry point for product teams running Cozystack on Hetzner, OVH or leased bare metal who want vendor backing without the commercial portal and billing layer. Customers of the Ænix platforms receive support as part of their engagement, at the tier they select.
Ænix enterprise support covers self-run Cozystack environments on a standalone retainer, and Ænix platform deployments as part of the engagement. Direct access to the engineers who maintain Cozystack and ship Ænix Platform.
Two paths
If you have an Ænix platform engagement (Public Cloud, Private Cloud or AI Platform), enterprise support is part of the engagement bundle. Specific SLA matches your support tier (independent of platform):
- Basic ($1,250/month per 10 nodes annual) — Business-hours support, 8-hour emergency response
- Standard ($3,000/month) — Business-hours support, 4-hour emergency response, priority tickets
- Plus ($5,500/month) — 24/7 support, 4-hour emergency response, full enterprise features (white-labeling, air-gap, GPU sharing)
- Enterprise (Custom) — 24/7 support, 1-hour emergency response, named TAM, personalized roadmap, customer-template MSA permitted, classified-data-cleared engineers for sovereign-cloud engagements
Ænix platforms → | Detailed pricing & tiers →
Path 2 — Cozystack support (self-running organizations)
If your team runs Cozystack itself, without an Ænix platform licence, support is available on a standalone retainer: architecture review and best-practice guidance, incident triage and root-cause analysis, upgrade planning and execution, custom feature development against Cozystack, and compliance gap analysis for DORA, NIS2 and sovereignty. Monthly retainer or pay-per-incident.
Response windows, review cadence, named TAM and 24/7 coverage vary by tier. The feature-by-feature comparison lives in one table on the pricing page rather than a summary here.
Support tiers and pricing →
How to start
Book a discovery call to scope your support requirements.
Ænix is the team behind Cozystack (CNCF Project) and the maker of Ænix Platform.
Frequently asked questions
Do we need an Ænix platform licence to buy support?
No. Support for self-run Cozystack is sold on its own as a monthly retainer, and that is a deliberate offering rather than an exception we tolerate. Cozystack is Apache 2.0 and a CNCF project; running it without buying anything from Aenix is a legitimate, supported choice, and a support contract simply puts the maintainers on call when you do.
How is this different from buying one of the Ænix platforms?
Support covers the engine you already run. The platforms add surfaces around that engine — billing, customer portals, compliance architecture bundles, migration tooling, productized installers. Teams with their own platform-engineering capacity frequently want the first and not the second, and that is the case this product is built for.
What does the response SLA actually cover?
Response, not resolution, and the distinction is stated in the contract rather than buried in it. A P1 acknowledgement lands within the tier’s window with an engineer who can read the stack traces; resolution time depends on the fault. Architecture review cadence, incident triage, root-cause analysis and upgrade planning are the substance of the retainer, and most of the value shows up before an incident rather than during one.
Can you support a version we have pinned or forked?
Pinned versions, yes, within the supported release window, and upgrade planning off an old version is one of the more common reasons teams start a retainer. A local fork is a scoping conversation: we can support divergence we have reviewed, and we will say plainly when a change has moved a deployment outside what we can reason about.
How does this differ from the free community support?
Community support is GitHub issues, the CNCF Slack channel and the Telegram group — best-effort answers from maintainers and other operators, and often good ones. What it cannot give you is a response time you can put in a risk register, a named engineer who knows your topology, or an upgrade you can schedule. That is what the retainer buys.
How does it compare to a Red Hat OpenShift subscription?
OpenShift support is bundled into a per-CPU subscription, so support cost scales with the size of your estate. Ænix support is priced per 10 nodes for self-run Cozystack, or bundled into a platform engagement that is scoped as a project. The engine itself stays Apache 2.0 either way, so you are buying people rather than the right to run software.
Does support include compliance work?
Gap analysis against DORA, NIS2 and sovereignty requirements is in scope, as is the architecture work that follows from it. Formal certification is not something a support contract delivers — ISO 27001 and SOC 2 alignment support is part of a platform engagement or a separate services scope.
