Deploying Ceph RGW and selling an S3 service are different projects. The missing work is commercial, operational, and customer-facing.
Customers do not buy a storage cluster. They buy a service with onboarding, access, visibility, support, and trust.
ScaleStore leaves storage to Ceph RGW and provides the product and operations layer around provider-owned infrastructure.
Providers keep ownership of infrastructure, customer relationships, domains, and data while avoiding years of glue software.
Ceph RGW is an excellent object-storage foundation. It provides an S3-compatible endpoint and a proven storage engine. What it does not provide is everything required to offer a commercial storage service.
A provider needs customer onboarding, tenant-aware workflows, access-key lifecycle, temporary credentials, quotas, usage visibility, support paths, governance, and a trustworthy operational model. These are not storage problems. They are provider problems.
For many providers, deploying Ceph is the visible project. Building everything around it is the hidden project: customer dashboards, provider operations tooling, access workflows, STS, revocation, usage ingestion, entitlements, billing inputs, diagnostics, auditability, safe operational boundaries, validation, observability, and evidence.
Every provider ends up assembling some version of this stack. The implementations differ. The effort rarely does.
ScaleStore adds provider onboarding, customer workflows, credentials, quotas, usage, diagnostics and commercial controls around Ceph RGW. Providers keep operating their own infrastructure and customers keep using provider-owned S3 endpoints.
The result is a provider-run S3 service with the customer and operator workflows needed to sell and support it under the provider’s own brand.
Some providers can. Many do. The question is whether building and maintaining that software is where the provider wants to spend its time.
Operating reliable infrastructure is already a specialist discipline. Building and maintaining the software platform around it is another. ScaleStore exists so infrastructure teams can focus on operating the service rather than recreating the same surrounding software stack from scratch.
ScaleStore focuses on Ceph RGW so its workflows can match RGW directly instead of hiding it behind a generic storage abstraction.
