ScaleStore handles provider onboarding, customer access, quotas, usage, diagnostics and day-to-day operations around Ceph RGW.
Provider lifecycle, bridge enrollment, readiness, service setup, and operational handoff.
Dashboard workflows, bucket flows, credentials, file access patterns, and usage visibility.
Quotas, usage, entitlements, billing foundation, and future pricing support.
Diagnostics, audit trails, monitoring, runbooks and operator workflows.
Instead of one long description, the platform is organized into practical operating areas.
Guide provider onboarding, bridge setup, readiness evaluation, and first-service setup.
Provider states, health, configuration, certification, and operational handoff.
Expose service access, buckets, credentials, and usage to customers.
Support common object-storage actions while keeping RGW as the storage endpoint.
Access keys, rotation, revocation and the information support needs when access fails.
STS-style short-lived, scoped access where temporary access is safer than long-lived keys.
Translate plans and entitlements into enforceable storage limits.
Ingest provider-side usage information and make it visible and commercially useful.
Create the records and control surfaces needed for provider billing workflows.
Help answer what failed, where, and why without exposing unsafe raw detail.
Readiness checks, release checks, recovery results and operational status.
Give operators a controlled way to investigate and assist customers.
Each layer has a clear job, with explicit boundaries between provider, customer, commercial, and trust concerns.
Providers often already have the infrastructure part: compute, networking, storage, and an RGW deployment. The missing work is usually everything customers and operators need around that RGW deployment.
ScaleStore focuses on that service layer. It does not absorb the RGW endpoint or move object bytes into a central proxy.
The same work usually ends up spread across scripts, admin procedures, internal portals, manual support paths and one-off integrations. ScaleStore puts those workflows behind one provider and customer model.
Providers can build these workflows themselves, but that means owning another software stack alongside Ceph. ScaleStore exists so engineering time can stay focused on infrastructure, reliability and customers.
