About Tidewater
We build the tool we wanted on call.
Tidewater began in 2021 when two engineers got tired of learning from a stakeholder that the numbers were wrong. We are a remote-first company of about 40 people who think data should be trusted for a reason.
Why Tidewater exists
Priya Raman ran the data platform team at a freight marketplace. Every few weeks a source feed arrived two hours late, every job still reported success, and the numbers customers saw in the morning were wrong. The tests passed and the orchestrator was green. The first alert was a forwarded complaint.
Tomas Lindqvist had built scheduling systems for a grocery delivery company and knew the shape of the problem from the other side: a schedule is a promise, and a promise can be checked. In 2021 they wrote the first version over a long weekend and pointed it at their own pipelines.
Today Tidewater watches data for 140 companies and reads about 90 million run events a month. The median time from data going late to someone knowing is 4 minutes. The principle has not changed: tell the owner first, and say what it affects.
- 140 customers
- 41 people in 11 countries
- 4 min median time to detect
- 99.97% uptime over 12 months
How we work
Three habits we keep.
Say what we do not know
Our alerts say "probably" when they are guessing. Our docs say "not yet" when a feature is missing. We would rather lose a deal than mislead a data team.
Owners over dashboards
A number nobody owns is not a metric, it is decoration. Everything in Tidewater has an owner, and the product makes ownership easy to set and hard to forget.
Read as little as possible
We take metadata, not data. Every feature starts with the question of what we can learn without reading a single row.
People
Some of the team.
Everyone here is invented, like the company. There are no photographs on this site, so each person is shown with their initials.
-
Priya Raman
Co-founder and CEO
Priya ran the data platform team at a freight marketplace before starting Tidewater. She still reads every demo request.
-
Tomas Lindqvist
Co-founder and CTO
Tomas built scheduling systems for a grocery delivery company. He owns the architecture and writes more Rust than he admits.
-
Ines Duarte
Head of Product
Ines spent eight years in analytics engineering. She decides what Tidewater says no to.
-
Callum Reid
Staff Engineer, Ingestion
Callum leads the team that reads run events from orchestrators and warehouses, about 90 million a month.
-
Amara Nwosu
Developer Advocate
Amara writes the quickstart, answers questions in the community forum and tests every release against a messy demo warehouse.
-
Jonas Weber
Head of Security
Jonas runs the security programme, the annual penetration test and the answers to your questionnaire.
-
Hannah Cho
Customer Success Lead
Hannah helps new teams get from first pipeline to first useful alert in a week.
-
Rafael Ortiz
Solutions Engineer
Rafael runs most product demos and is the person who says "show me the pipeline that hurts".
Where we work
Tidewater is remote-first. Our registered office is 14 Seawall Lane, Floor 3, Portland, Maine 04101, United States. We meet in person twice a year and write everything down the rest of the time. See our open roles.
Want to see what it would catch?
Book a 30 minute walkthrough. We connect a sample of your setup and show you what it would have caught last month.