Basalts3 api

About us

We were paying more to read our data than to keep it

Basalt started as an internal storage layer for a genomics group whose egress bill exceeded its storage bill four months running.

2013
founded
190
people
19
countries
100%
engineer-owned

Origin

Egress was always a margin, not a cost

We priced out transit, peering, optics and the people to run it. At any serious scale, moving a gigabyte costs a fraction of a cent. Charging seven to nine cents for it is a choice — one that quietly makes your data expensive to leave with. We decided not to make it.

  • Free egress since the first bucket, with a published fair-use rule
  • Erasure coded across three named facilities per region
  • Monthly restore drills on real customer objects, reported to customers
2019

An internal store for one lab

40 TB and a very tired NAS.

2020

Erasure coding across three buildings

Site loss stops being an event.

2021

Public beta with free egress

The pricing model that got attention.

2023

Object lock and compliance mode

First regulated customers.

2026

1.5 exabytes stored

Eight regions, still free egress.

How we work

Boring on purpose

We would rather run software that is three years old and understood than something new that pages us at 04:00.

Own the path

We buy transit from multiple carriers and peer directly wherever it is possible, so a single bad hop is never a single point of failure.

Write it down

Every incident gets a public write-up. Every design decision gets an RFC. Institutional memory beats heroics.

Some of the people behind it

A quarter of the company has been here since the first rack.

W. ChenSecurity
R. MendesInfrastructure
D. HaugenSecurity
C. WhitfieldSupport
B. SørensenProduct
T. OkonkwoDeveloper relations
V. IvanovićSecurity
A. VasquezSecurity

We are hiring

Remote-first across EU time zones, with a small office network for people who prefer one.