Scality Ecosystem & Application Partners
Scality and Wasabi.
Scality on-prem, Wasabi in the cloud. Standard S3 on both ends, no egress fees on the cloud half, so DR and offsite stop being budget conversations.
the problem
Hybrid object is still two storage worlds, two billing structures.
On-prem and cloud each have their own operating model. Egress fees turn DR and offsite into budget conversations. Code written for one side rarely runs on the other unchanged.
- Hybrid object means two operating models.
- Egress fees punish DR and offsite copies.
- Cloud sticker shock at petabyte scale.
- Code rewrites every time data crosses the boundary.
the joint solution
Standard S3 on both ends, no egress trap on the cloud half.
Scality on-prem and Wasabi in the cloud — both standard S3. Wasabi has flat-rate pricing and zero egress on the cloud half. The same code path reaches both back ends.
- Standard S3 on both ends; no rewrites to span them.
- Wasabi: flat-rate cloud pricing.
- Zero egress fees on the cloud half.
- Hybrid storage planned on the same S3 contract.
joint solution benefits
What hybrid object delivers.
Predictable hybrid economics.
On-prem economics on Scality, flat-rate economics on Wasabi. Spend math stays calculable month to month.
Same code path to both ends.
Applications and backup software written for one reach the other without modification.
Disaster-recovery rehearsals stay affordable.
Wasabi has no egress fees. Pulling data back from cloud doesn't trigger a budget review.
Not a one-way door.
Pull data back on-prem when economics or compliance shift. The S3 abstraction holds either way.
Joint architecture
How Wasabi runs on Scality.
Workloads flow through the partner integration and land on the Scality data layer.
Show us the workflow. We will show you the fit.
