Connect infrastructure
Onboard the provider, establish the provider-side control boundary and verify the Bridge path to the environment.
Provider-enablement platform for Ceph RGW
Turn Ceph RGW into a customer-ready S3 service.
Ceph gives you the storage engine. ScaleStore gives you the provider product around it. Launch, sell, support and operate S3-compatible storage under your own brand while infrastructure, endpoints, customer relationships and object traffic remain provider-owned.
Ceph remains the engineRGW keeps serving S3-compatible object storage.
Providers stay in controlInfrastructure, endpoints, customers, policy and data stay provider-owned.
ScaleStore adds the service layerOnboarding, access, quotas, usage, commercial workflows, diagnostics and operations.
Why ScaleStore
Storage is only one part of the service.
Deploying Ceph RGW and selling a dependable S3 service are different projects. Providers still need the customer, commercial and operational layer around the storage engine.
Ceph RGW
The storage foundation
Ceph RGW provides a proven S3-compatible endpoint and object-storage engine. ScaleStore does not replace it.
The hidden project
Everything around storage
Customer onboarding, tenant-aware workflows, credentials, STS, quotas, usage, entitlements, billing inputs, diagnostics, auditability, support and recovery all still have to exist.
ScaleStore
The provider product layer
ScaleStore brings those surrounding concerns into one coherent platform while the provider keeps operating its own Ceph RGW environment.
Ceph gives you object storage.ScaleStore gives you the product around it.
Platform
Four layers, one provider platform.
Provider, customer, commercial and operational workflows live in one place.
Provider
Launch and operate
- provider onboarding and lifecycle
- bridge enrollment and health
- service configuration
- readiness and operational handoff
Customer
Use object storage
- customer dashboard workflows
- buckets and S3 access
- access keys and temporary credentials
- usage visibility
Commercial
Package the service
- plans and entitlements
- quota logic
- usage records
- billing foundation
Trust
Support with confidence
- security boundaries
- diagnostics and auditability
- observability and runbooks
- release and recovery confidence
Launch Center
Guide provider onboarding, bridge setup, readiness evaluation and first-service setup.
Credentials
Access keys, rotation, revocation and support-friendly credential workflows.
Temporary access
Short-lived, scoped credentials where temporary access is safer than persistent keys.
Quotas
Translate plans and entitlements into enforceable storage limits.
Usage
Ingest provider-side usage information and make it customer-visible and commercially useful.
Diagnostics
Help operators answer what failed, where and why without exposing unsafe raw detail.
Operational evidence
Track readiness, health checks, recovery results and release status alongside day-to-day operations.
Support workflows
Give operators a controlled way to investigate and assist customers across tenant boundaries.
Architecture
Control plane and object data path stay separate.
ScaleStore coordinates the service. The Provider Bridge is the provider-side control edge. Provider RGW remains the endpoint that serves customer object traffic.
ScaleStore Cloud
Coordinates the service
Provider state, product configuration, approved actions, customer workflows, commercial controls, diagnostics and support.
Provider Bridge
Executes approved control tasks
Runs per provider, connects outbound, integrates provider-side systems and reports health and diagnostics.
Provider Ceph RGW
Serves object traffic
Customers continue talking directly to provider-owned S3 endpoints. ScaleStore Cloud does not proxy their object bytes.
1Provider deploys Bridge
2Bridge enrolls outbound
3ScaleStore authorizes control actions
4Customers use provider RGW directly
Provider ownership
You remain the storage provider.
ScaleStore is not another hosted object-storage provider and it is not a Ceph replacement. It is the surrounding product and operations platform for a provider-owned service.
Provider owns
- Ceph RGW infrastructure
- S3 endpoints and domains
- customer relationship
- service brand and commercial policy
- object data path
- operational policy
ScaleStore provides
- provider and customer workflows
- bridge-based provider integration
- access keys and temporary credentials
- quotas, usage and billing inputs
- diagnostics and audit trails
- monitoring, release checks and recovery workflows
Product workflow
From provider onboarding to day-two operations.
Connect the provider, define the service, onboard customers, manage access and usage, then operate it day to day.
Define the service
Configure the object-storage service, enabled workflows, operational assumptions and commercial boundaries.
Onboard customers
Expose customer-facing workflows around storage access, buckets, credentials, usage and support.
Manage access
Handle access keys, temporary credentials, rotation and revocation as first-class service workflows.
Control usage
Support bucket workflows, quotas and usage visibility while customers keep using normal S3 clients against provider RGW.
Operate and prove
Use health, diagnostics, observability, governance and recovery workflows to support the service after launch.
Security & Trust
Trust starts with explicit boundaries.
Provider infrastructure stays under provider control. Customer object traffic goes directly to RGW. Provider-side actions run through a scoped outbound Bridge.
Provider ownership
Keep control local
Providers keep infrastructure, RGW endpoints, domains, customer relationships, policy and the object data path.
Tenant boundaries
Keep context explicit
Every provider, customer and support action carries an explicit tenant and role context.
Credential governance
Control access
Access keys, temporary credentials, rotation, revocation and support workflows are treated as product concerns.
Bridge model
Limit provider-side exposure
The Provider Bridge initiates outbound connectivity and provides an intentional control boundary instead of requiring broad inbound administrative exposure.
Diagnostics
Support safely
Correlate failed requests and backend errors without exposing credentials or dumping raw sensitive data.
Operations
Operate safely
Readiness checks, monitoring, runbooks, release gates and recovery tests stay part of normal operations.
Core boundary:ScaleStore Cloud coordinates the service; provider-owned Ceph RGW serves the object data.
Build vs. buy
Do not turn your storage launch into a second software company.
Providers can build this surrounding stack themselves. The question is whether customer portals, credential workflows, quota logic, usage pipelines, diagnostics and operator tooling are where you want your engineering effort to go.
Your differentiation
Infrastructure and operations
Reliable infrastructure, local presence, operational quality and the customer relationship are where providers can differentiate.
Necessary software
The surrounding service stack
Every commercial RGW provider needs some version of onboarding, access, quotas, usage, support and governance.
ScaleStore
Reuse the provider layer
Use a purpose-built platform around RGW instead of assembling disconnected scripts, internal portals and one-off integrations.
Use cases
For operators that want S3 to become a product, not just an endpoint.
ScaleStore is aimed at infrastructure operators and customer-facing service providers, not generic retail storage users.
Hosting providers
Add S3 to the portfolio
Offer object storage alongside VPS, dedicated or cloud services without building the full surrounding product stack from scratch.
MSPs
Operate storage under your brand
Give customers structured access, usage and service workflows while keeping provider ownership intact.
Regional clouds
Pair local infrastructure with a product layer
Offer provider-owned object storage with explicit control boundaries and a customer-facing service model.
Infrastructure operators
Turn capability into a service
Use existing infrastructure expertise to launch a branded S3-compatible offering instead of selling only raw resources.
Design partners
Shape ScaleStore against a real RGW environment.
We work directly with infrastructure providers to test onboarding, customer workflows, operations and support against real Ceph RGW environments.
Strong fit
- you operate or plan to operate Ceph RGW
- you want to expose S3 under your own brand
- you care about control, tenancy and supportability
- you want direct technical collaboration with the ScaleStore team
What the collaboration covers
- assisted onboarding and architecture discussion
- provider and customer workflow feedback
- operational requirements grounded in your environment
- direct visibility into product evolution
See ScaleStore as a provider platform.
If you operate infrastructure and want to turn Ceph RGW into a customer-ready S3 service, the design-partner program is the best way to evaluate ScaleStore with your environment.
Technical detail
Architecture, workflows and operations.
The detailed pages cover the Provider Bridge, workflows, security boundaries and operating model.
Why
Why ScaleStore exists
The provider problem, hidden engineering project and build-versus-buy argument.
Platform
Capability map
Provider, customer, commercial and operator workflows in detail.
Bridge
Provider control edge
Duties, non-duties, outbound model and ownership boundary.
Tour
Workflow-level product tour
Provider onboarding through credentials, buckets, usage, diagnostics and operations.
Trust
Security & Trust
Provider control, tenant boundaries, credentials, diagnostics, recovery and evidence.
FAQ
Direct answers
Product, Ceph RGW, architecture, security, operations and the design-partner model.