CLYSO Enterprise Storage
CES Subscriptions
CES Subscription defines how CES is operated and maintained in production environments.
It combines validated releases, consistent operational standards, and structured subscription levels to support stable and predictable operation of CES clusters.
CES releases are validated through CLYSO’s engineering-driven build and test framework and follow a controlled lifecycle to ensure consistent deployment and operation.
CES Subscription applies exclusively to validated CES environments.
CES and Ceph Upstream
CES builds on Ceph Upstream and follows a controlled release model operated by CLYSO.
Scope and Operational Reliability
CES Subscription defines the operational scope for running CES in stable production environments. It covers core operational activities within validated configurations and focuses on reliable cluster operation rather than architecture design, migration, or consulting services.
Operational reliability
CES releases are validated and tested multiple times by engineering before delivery.
Operational stability is supported through:
Supported Platforms and Deployment Methods
CES environments are supported on validated Linux platforms and deployment methods defined per CES release.
CES / Ceph
Core storage services delivered as part of CES.
Deployment options include:
Kubernetes with CES
Validated Kubernetes environments using:
Validated within the CLYSO ecosystem
Deployment components are validated and supported as part of the CES operational model.
Subscription Levels
CES is available in multiple subscription levels. Levels differ mainly in service availability, response times, and service limits.
Essential : Business-hours coverage for environments with established internal operations teams.
For smaller or non-critical environments.
Coverage: 8x5
Response time: Next business day
SLA: Limited number of service requests
Best for: Test and smaller production environments
Enterprise 8x5 : Structured production subscription during business hours.
Coverage: 8×5 (Mon–Fri, 9 a.m.–5 p.m.))
Response time: Fast handling of critical incidents
Scope: Extended service coverage
Best for: Production clusters
Enterprise 24x7 : Continuous subscription coverage for mission-critical environments.
Availability: 24×7
Response time: Priority handling for critical incidents
Scope: Maximum operational availability
Best for: Business-critical operations
Operations and Incident Handling
Incidents are classified according to operational impact. Critical incidents are prioritized based on the selected subscription level, while lower-severity requests are handled during standard service availability.
Operational actions may require customer-side execution. Customers are expected to:
Qualified customer personnel are required for operational activities.
Scope Limitations
Not included
Scope boundary
Issues unrelated to CES functionality are outside the subscription scope.
The subscription assumes that surrounding infrastructure, operating systems, and external software components are managed separately.
Additional Services and Programs
Additional Services
Planning, migration, and implementation activities are available separately from CES Subscription through CLYSO Services.
This allows customers to engage support along the full lifecycle — from initial planning to production operation.
Academic Program
CLYSO offers an Academic Program for universities and research organizations working with CES.
The Academic Program is separate from commercial CES subscription levels.
Frequently Asked Questions
These are the questions we hear most often about CES (CLYSO Enterprise Storage) Subscriptions.
What is the difference between CES and Ceph Upstream?
CES is based on Ceph Upstream but delivered as a validated subscription model with defined releases and operational standards.
Is CES Subscription the same as a support contract?
No. CES Subscription defines how CES is operated and maintained. Ceph support outside CES is offered separately.
Is Kubernetes supported with CES?
Yes. Kubernetes environments using Rook and Ceph-CSI are part of validated CES deployment models.
Which components are used for Kubernetes-based CES deployments?
Typical components are:
Does CES Subscription include migration or implementation services?
No. Planning, migration, and implementation are provided separately through CLYSO Services.
Can I migrate from Ceph Upstream to CES?
Migration scenarios depend on the existing environment and should be evaluated individually through CLYSO Services.
Part of the Ceph Open Source Community
Active contributors to the Ceph ecosystem and members of leading open-source foundations.
Looking for an enterprise-ready Ceph solution?
Discover how CES combines validated releases and operational standards for production use.