About us
We built it after an invoice that was larger than our hosting bill
Lumberyard started when the observability spend at our previous company overtook the infrastructure it was observing.
Origin
Priced to discourage looking
Per-host, per-seat, per-query and a fifteen-day retention window: every dimension of that pricing pushed us to send less, keep less and look less. That is the opposite of what observability is for. One meter, long retention, free queries — and if you cut what you send, we will help, even though it lowers our revenue.
- One meter: gigabytes in
- Thirteen months of retention at every paid volume
- The ingest analyser exists to reduce your bill
A columnar log store
Object storage, stateless query.
Metrics without cardinality limits
Dictionary-encoded labels.
Traces and exemplars
Three signals, one query language.
13-month retention as standard
Retention tiers removed entirely.
118,204 hosts
Across accounts ingesting 4.1 TB a day each.
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.
We are hiring
Remote-first across EU time zones, with a small office network for people who prefer one.