Core Technology

What Is a Data Lakehouse?

We use this term across our site, so here's a short, jargon-free explanation. In one line: it's where your history lives — cheap enough to keep everything, organized enough to ask real questions of it.

Get Started See Pricing

It's Two Old Ideas, Combined

For years, storing data meant picking one of two options. A lakehouse is what you get when you stop having to choose.

A data lake

The good part

Cheap. Holds anything, in any shape, for as long as you want.

The catch

Hard to search. Finding one answer can mean sifting through everything.

A data warehouse

The good part

Fast and tidy. Built for questions and reports.

The catch

Expensive, and you have to decide up front what you'll keep and how.

A data lakehouse

The good part

Both. Cheap enough to keep everything, organized enough to query it quickly.

The catch

No trade-off to make — which is why we use one.

Why It Matters for Your Data

Three practical differences you'll actually notice

Nothing Gets Thrown Away

Most monitoring systems save space by overwriting old readings or averaging them down to a single number per day. We keep every reading at full detail, for as long as you want it.

Ask Questions of Years at Once

Compare this winter to the last four. Find every hour a pump ran hot. Because the history is organized, questions like these come back in seconds instead of requiring a data project.

The Data Stays Yours

It's stored in open formats, not a private one only we can read, so your history is never locked inside our platform. When you need a full copy of it, ask and we'll put one together for you.

Where Your Data Goes

From a device in the field to history you can search

Step 1

Your devices report

Sensors send readings and cameras send counts, continuously, all day long.

Step 2

The live window keeps 14 days

Everything from the last 14 days powers your live map, alerts, and dashboards. It's included in what you already pay per device.

Step 3

The lakehouse keeps the rest

On Expanded Operations, readings older than that move into the lakehouse and stay there — years of history, still queryable, instead of rolling off and disappearing.

What It Costs to Keep

Expanded Operations includes 100 GB of lakehouse storage and 1 TB of query compute every month. Past that, storage is $0.05 per GB per month — sensor readings are small, so years of them usually cost very little. The pricing page has the full breakdown.

Stop Losing Your History

Every reading your infrastructure produces is worth keeping. We make that the default instead of an expensive project.

Schedule a Demo Explore IoT Sensors