Tidewater watches your data pipelines. It tells you when data is late, missing or different from what you expected, which tables and dashboards are affected, and who owns them.
What you can do
- Monitor pipelines and tables for freshness, volume and schema changes.
- See lineage from a source table to every model and dashboard that depends on it.
- Get alerts that go to the owner of the thing that is wrong, with the impact attached.
- Automate all of the above through an HTTP API and signed webhooks.
Where to start
If you want to see it working, follow the quickstart. It takes about ten minutes and ends with a real alert on a sample pipeline.
If you want to understand how Tidewater thinks before you set it up, read concepts. It defines pipelines, runs, assets, expectations and alerts, and shows how they relate.
If you are writing code against Tidewater, go to the API reference. It lists every endpoint with examples in Python, TypeScript and curl.
How the documentation is kept honest
Every code example on these pages runs against a test workspace each time we release. When an example stops working, the build fails, and we fix the page before the release goes out.
Getting help
Ask in the community forum or write to support@saas.phoenixcodes.org. Customers on Business and Enterprise plans have a priority queue with a response time commitment. Search these docs at any time by pressing the slash key.