Ingestion and connectors
180 maintained connectors for warehouses, event streams, billing and CRM. Schema drift is absorbed on the next sync instead of breaking the load.
Browse the directoryEducation Strategic Advisory Practice
One console for the pipelines, the lineage and the people on call.
Northlane runs on top of the warehouse you already own. Model the transforms, watch every table and prove where a number came from — without a second scheduler, an agent on a host or a copy of your data.
- Read-only connection
- 180+ connectors
- SOC 2 Type II
Running in production at
One control plane
Three tools, one graph, and nothing left to reconcile by hand
Most teams arrive with an orchestrator, a testing framework and a catalogue that all disagree about what exists. Northlane reads the warehouse query history once and builds a single graph the three of them share — so a schema change, a failed run and a stale dashboard become one event with one owner instead of three tickets.
- Model, run and watch on the same objects Transforms, schedules, tests and freshness contracts attach to the table itself, not to three separate repositories.
- Metadata only, never your rows Schemas, query logs and row counts are read over a role you create and can revoke. Column values stay in the warehouse.
- One declared owner per table Ownership is stated once, and every alert, access request and audit line resolves against it.
Inside the product
Three surfaces an evaluator always asks to see
Pick a surface. Each panel shows the view your team would actually work in, and names the thing it replaces.
Build the pipeline where you can see all of it
Every transform is a node carrying its inputs, its owner and its last run. Drop into SQL on any node without leaving the graph, and diff the change against last night's snapshot before it merges.
- Git-backed history with a readable diff on every node
- Dry runs execute on your compute against yesterday's snapshot
- Dev to staging to production without rewriting a connection string
Know a table broke before the dashboard does
Freshness, volume and distribution checks run on every table Northlane can see. Baselines come from 30 days of history rather than a threshold somebody guessed at in a sprint two years ago.
- Seasonality and weekday shape modelled per table
- Incidents routed by table owner from your existing on-call rota
- Downstream dashboards listed before anyone decides to page
Answer where a number came from in one click
Open any figure and walk it upstream: the model, the join, the source column, the job that wrote it. The same graph answers the auditor's question and the analyst's, so nobody maintains a second diagram.
- Column-level resolution across every connected warehouse
- Blast radius scored before a rename is merged
- Seven-year retention, exportable as signed evidence
In production
Three platform teams on what the console replaced
Each quote comes from a named engineer running Northlane on production workloads, with the figure they reported beside it.
We retired the scheduler, the test runner and the catalogue in one quarter. Northlane did not add a tool to the stack, it removed two of them.
3 to 1 tools consolidated into one console
Priya Raghavan
VP Data Platform · Halden Systems
Every schema change now arrives with the list of dashboards it will break. Nobody guesses, and nobody ships a rename on a Friday any more.
1,400 models under lineage in nine days
Marcus Feld
Director of Analytics Engineering · Ardent Labs
Analysts used to raise a ticket to ask whether a dashboard was fresh. That question has not been asked here since March.
6 hrs of triage returned to the team weekly
Dana Okonkwo
Head of Revenue Operations · Corvane
