Providers keep their infrastructure and RGW endpoints. Customer object traffic stays on the provider path. ScaleStore adds tenant-aware access, scoped credentials, diagnostics, audit trails, monitoring and recovery checks around that service.
Providers keep infrastructure, RGW endpoints, domains, customer relationships, and the object data path.
Provider and customer actions are separated by role and tenant context.
Access keys, temporary credentials, rotation, revocation, and support flows are treated as product concerns.
Operators can trace failures without exposing credentials or unrestricted backend data.
Readiness checks, monitoring, runbooks, release gates and recovery tests provide concrete operating evidence.
Design partners can evaluate the architecture and workflows while the platform hardens around real provider environments.
Keeping control-plane workflows separate from customer object traffic is the foundation for provider ownership, performance expectations, support boundaries, and trust.
Coordinates product, access, commercial, diagnostic, and evidence workflows.
Executes approved provider-side control actions and reports health.
Serves S3-compatible object traffic directly to customers.
ScaleStore security starts with an explicit architectural stance: providers remain in control of the storage environment and customer object traffic remains on the provider path. That boundary removes a whole class of problems that come with unnecessary central data-plane interception.
Providers should continue owning their Ceph RGW clusters, domains, S3 endpoints, customer relationships, operational policies, and data path. ScaleStore coordinates the product and operational layer around those assets. It should not erase provider control.
A provider platform has to treat tenancy as a first-class concern. Workflows, diagnostics, and support surfaces should be aware of provider and tenant context, and role boundaries need to make sense for each audience.
Commercial storage needs more than long-lived access keys. ScaleStore supports temporary credentials, rotation and revocation, with enough audit and diagnostic context to investigate access problems safely.
The Provider Bridge connects outbound and executes only approved provider-side operations. ScaleStore does not require broad inbound administrative access to the provider environment.
Diagnostics expose the identifiers and backend status needed to investigate failures while redacting secrets and limiting detail to the operator’s role and tenant context.
Providers need to onboard, monitor, support and troubleshoot the service after launch. ScaleStore keeps diagnostics, monitoring, runbooks and release checks alongside the customer and provider workflows.
When something breaks, operators need to see what failed and know how to recover. Release checks and recovery tests make those paths explicit before they are needed in production.
