We started Logwave in 2022 after a decade of debugging production outages at midnight using tools that felt punishing. Forty-two of us now. One mission: make observability feel like it was designed by someone on your team.
In Q3 of 2021, Maya Chen. Then a principal engineer at Datadog. Watched her own team's observability bill cross $400k a month while their alert volume crossed 800 pages a week. The tools she'd helped build for everyone else were now the thing keeping her team from shipping.
She left in January 2022 with two co-founders and a thesis: observability priced per gigabyte is broken, and alerts trained on textbooks instead of your own data are noise. Logwave is the platform she wanted on her own desk.
Today we're a team of 42 across San Francisco, Lisbon, and remote. We ship every weekday. We carry the pager for our own platform. We charge per seat, on purpose, forever.
Six rules. They're on the wall in our office and at the top of every onboarding doc.
Every engineer at Logwave is on-call for the product they own. There is no separate ops team. If you build it, you wake up for it.
Per-seat pricing. Forever. We will never charge by ingest, by host, by custom metric, or by any unit that punishes you for using the product more.
Postgres, Rust, ClickHouse, NATS. We don't ship infrastructure we can't debug at 2 AM. The novelty goes into the product surface, not the stack.
A feature isn't shipped until the docs ship with it. The changelog is human-written. The release notes don't read like compliance documents.
Our agent, our query parser, our Terraform provider, our Helm charts. All Apache 2.0. We compete on product, not vendor lock-in.
RFC-first culture. Decisions live in writing. Meetings happen when async failed. Not before. New engineers can ramp from the doc trail alone.
A small look at the 42 of us. Engineers, designers, support, GTM. All of them on-call for the parts of Logwave they own.
Former principal engineer at Datadog. Wrote her PhD thesis on time-series compression and now spends her days arguing with sales about pricing.
Built the storage layer at Honeycomb, then a high-frequency trading firm. Owns the ingest pipeline. Refuses to ship anything written in Java.
Ex-design lead at Vercel. Believes the on-call experience is a product surface, not a feature. Owns the dashboard editor end-to-end.
Wrote the anomaly detection paper everyone's quoting. Joined from Lightstep. Maintains our open-source query parser in their spare time.
Runs the platform team that runs the platform. Ten years of carrying the pager at Booking and Stripe. Knows where the actual bodies are buried.
Maintains the agent, the SDKs, the Terraform provider, the Helm charts. If you've ever read a Logwave doc, you've read Theo's writing.
About this design template
This is a design template that shows how Albertson Designs approaches saas websites. The structure, photography, typography, and copy were built around how a real saas business actually operates. Generic about-services-contact patterns are not here.
When Albertson Designs builds your site, we use designs like this as a reference for color, structure, and category vocabulary. Every line of code, every photo, and every word is custom for your business. Most full builds ship in four to eight weeks depending on scope.
Book a free consultation