# Eddy

> A reporting database for SaaS products.

eddy keeps the data behind customer reports updated as source records change. Your app and agents can query the results, or eddy can send them to other systems.

## Product facts

- [Eddy reference](https://eddy-gilt.vercel.app/reference.md): What Eddy does, who it serves, source and SQL support, time alignment, early-access pricing and recorded evidence.
- [HTML reference](https://eddy-gilt.vercel.app/reference): The same product facts in a web page.

## Marketing and integration

- [Better reporting for your customers](https://eddy-gilt.vercel.app/): Customer reports getting slow, expensive or out of date? eddy keeps reporting data updated in a separate database for your app, agents and other systems.
- [How a change reaches your customer report](https://eddy-gilt.vercel.app/product): See how eddy keeps reporting models updated, handles corrections and delivers results to your product. Examples of customer data, model changes and time alignment.
- [Connect reporting data to your product](https://eddy-gilt.vercel.app/developers): Connect source data, define SQL or dbt models, then query or push the results. Setup, access rules and model changes for developers.
- [Better reporting inside your SaaS product](https://eddy-gilt.vercel.app/for/saas): Slow reports, overnight updates or rising server costs? eddy keeps customer reporting data updated in a separate database for your product.
- [Reporting data for your customer agents](https://eddy-gilt.vercel.app/for/agents): Let customers ask about their data. Connect agents and MCP tools to the reporting models behind your application, with your product's access rules.
- [SQL and dbt for customer reporting](https://eddy-gilt.vercel.app/for/data): Reuse the SQL and dbt models behind your customer reports. eddy keeps the results updated for your app, agents and other systems.
- [Early-access demos, pilots and pricing](https://eddy-gilt.vercel.app/pricing): Book a demo and discuss a hosted pilot on your data. We agree the price before you start while we develop usage-based pricing.

## Recorded evidence

- [Serving benchmark](https://eddy-gilt.vercel.app/assets/benchmarks/read-fleet-2026-10-08.json): Recorded workload, machine setup, results and scope.

## Optional

- [Operator reference](https://eddy-gilt.vercel.app/operators): What each SQL operator costs per change and keeps as state under incremental view maintenance, in Redis-style complexity, with an explorer and a skew simulation. Engine-neutral.