Platform
Everything a number needs before the room can stop arguing about it
The landing page shows four things. This is all of it — the modelling layer definitions are written in, the certification process that decides which are official, the lineage that explains where one came from, and the controls a security team will ask about before this sits in front of the warehouse.
01
Modelling
Where a definition lives, and why it is the same number everywhere.
One definition, every reader
A metric is defined once and served to dashboards, notebooks, spreadsheets and the API through the same compiled query. Not a convention the team agreed to follow — the only path to the number there is.
Warehouse-native compute
Sightline compiles to SQL and executes in your warehouse. Your data never moves, your existing row-level security still applies, and your compute bill stays with the vendor you already negotiated it with.
Definitions as files
Every model and metric is a version-controlled file with a diff, an author and a review. The definition of revenue changing is a pull request, which is the only form of that event anyone can audit later.
Composable metrics
Ratios, cohorts and period comparisons are built from certified metrics rather than redefined beside them. Net revenue retention derives from revenue, so it cannot quietly disagree with it.
02
Certification
The part that decides which definition is the official one.
Certification policy
Rules for what a metric must have before it counts as official — an owner, a description a non-analyst can read, tests, a freshness contract, a named approver. Written as configuration and enforced, rather than as a wiki page nobody opens.
Review and sign-off
A change to a certified definition goes to the people who depend on it, with the impact analysis attached. Finance finds out that revenue changed before the board deck does, not after.
Freshness contracts
Every metric declares how current it is expected to be. A number served past its window is labelled stale wherever it appears rather than quietly rendering as if it were fine.
Deprecation with a forwarding address
Retiring a definition points its readers at the one that replaced it. A dashboard querying a deprecated metric says so and names its successor, which is the only version of this that actually gets migrated.
03
Lineage
Answering where a number came from, and what breaks if it changes.
Column-level lineage
Resolved to the column, not to the table. A schema change upstream reports which specific metrics it touches instead of flagging every model that reads the same source.
Impact analysis before a merge
The diff shows what the number would have been for the last ninety days under the new definition. Approving a change to revenue without seeing that is approving it blind.
Definition-conflict detection
Two certified metrics compiling to substantially the same query is surfaced as a conflict. This is how three revenues appear in the first place, and it is detectable long before the meeting.
Query history
Who asked for which metric, from which tool, and what it returned at the time. The record that makes a figure in a six-month-old deck reproducible.
04
Security & compliance
What the review board asks for, answered before they ask.
Your warehouse's permissions, unchanged
Queries run as the asking user where your warehouse supports it, so row-level and column-level security you already configured still governs the result. Sightline does not become a way around it.
SSO, SCIM and RBAC
SAML and OIDC single sign-on, directory-synced provisioning, and role-based access down to individual models and columns.
Data residency
The control plane pins to a region, and because compute stays in your warehouse, the rows themselves never leave the account they already live in.
Tamper-evident definition history
Append-only, hash-chained and exportable. When a regulator asks how a reported figure was calculated in March, the answer is a signed record rather than an archaeology project.
Define the number people argue about.
Pick the one metric that starts every disagreement, write it down once, and let a week of meetings resolve against it. That is the whole evaluation.
Free for 14 days · No card required