About ObjectBasin
We run object storage for teams that care about request-level cost and predictable latency — mostly media companies, logistics platforms and small product teams that outgrew a single server.
How the service is operated
Objects are written to three independent nodes inside a region before the write is acknowledged. Reads are served from the node closest to the caller; range requests are satisfied from a single replica. Metadata is versioned and copied hourly to a separate region. A background scrubber verifies checksums continuously and repairs a replica from its siblings when they disagree.
Regions
Frankfurt (fra1) is our primary region with the largest capacity, followed by Amsterdam (ams1) and Helsinki (hel1). Ashburn (ash1) serves read-heavy US workloads. Storage runs on eleven nodes in total: three each in fra1, ams1 and hel1 and two in ash1, with read nodes added where traffic justifies them. New regions are added when a customer commitment justifies the capacity — we do not announce a region before it is live.
Engineering principles
- Boring storage. Checksummed writes, immutable parts, no transformation on the write path.
- Honest accounting. Counters are exposed per bucket, hourly, and downloadable as CSV.
- Small surface. One API, one gateway, documented behaviour on every error path.
- No surprises. Deprecations are announced 90 days ahead in the changelog.
Company
ObjectBasin GmbH is registered in Frankfurt am Main, Germany. We are a small team — engineering, operations and support — and we answer email ourselves.
| Contact | Address |
|---|---|
| Support | support@objectbasin.com |
| Sales and DPAs | sales@objectbasin.com |
| Security | security@objectbasin.com (PGP on request) |
| Postal | Hanauer Landstraße 148, 60314 Frankfurt am Main, Germany |
| Phone | +49 69 2475 4410 (10:00–18:00 CET/CEST, weekdays) |