GASP
GASP Workspace

Your governed metrics layer, run for you

GASP Workspace is your company's own metrics layer, built on the open GASP Standard. It keeps your mapping, the decisions behind it with an owner on each, your check results and your readiness history. It compiles the metrics into your warehouse's own engine and serves them to every agent your teams run. We are building it now with three design partners, the data and AI platform leads who run agents over their company's metrics.

What you get

The standard, applied to your company and kept current

The open standard says what each metric means. The Workspace holds what it means for you, who decided it and how ready your data is to report it.

For your agents

One governed layer, served to every agent

Your agents read your metrics from the Workspace over MCP, with your mapping and your owners attached. Every assistant and copilot your teams run answers from the same definition.

For your warehouse

Metrics compiled into your own engine

The covered GASP metrics are written into your semantic model in your warehouse's SQL dialect, over your own table and column names, and run where your data already lives.

For your governance

Decisions with owners and a readiness level over time

Each mapping answer and judgement call is recorded with its owner and date. Your readiness level is kept as a history, so you can see when it moved and which decision moved it.

For your board

A readiness report you can share

One read-only page states the level you reached, the checks behind it and what the next level needs, ready for your board, your auditors or an investor.

For your analysts

Drift scored against your own numbers

Your existing metrics are run beside the canonical ones and every difference comes back with its cause: a filter, a dataset or a formula that one side reads differently.

For your next event

Certification before a raise, a sale or a credit facility

GASP certification is a reviewed, dated readiness report signed by the maintainer, valid for twelve months and bought for the event that needs it.

How it works

From your schema to a served layer in four steps

Each step is a tool in the GASP MCP server. The Workspace runs them for you and keeps every result.

  1. 01

    Profile

    We read your warehouse schema and its statistics and describe each table: its key, its time field and its kind, with the evidence and the questions the names leave open.

    • profile_schema
  2. 02

    Propose and decide

    Your tables and columns are matched to the GASP datasets and fields. Your team settles the open questions and candidates, and each answer carries an owner.

    • propose_mapping
    • record_decision
  3. 03

    Check and reach a level

    The readiness checks run as SQL in your warehouse. Fixes are ranked by the Core metrics each one brings in, and the level you reach is recorded.

    • generate_checks
    • plan_fixes
    • readiness_report
  4. 04

    Compile and serve

    The covered metrics are compiled into your model in your dialect, scored against your own numbers and served to your agents from the Workspace.

    • compile_model
    • score_drift
The evidence

The definition decides whether the answer is right

We asked two Claude models 24 Core metric questions over a SaaS warehouse and ran the SQL they wrote: from the schema alone they were right 60% and 70% of the time, and with the GASP definition both 100%. The Workspace puts your agreed definition in front of every agent that asks.

Schema only
The table definitions and the question
Claude Sonnet 5.5
60%
72 of 120 runs matched the standard
Claude Opus 5.5
70%
84 of 120 runs matched the standard
Schema and the GASP definition
The same, plus the metric’s canonical formula and the fields it reads
Claude Sonnet 5.5
100%
120 of 120 runs matched the standard
Claude Opus 5.5
100%
120 of 120 runs matched the standard

Every question, the SQL behind each miss and the method.

Design partners

Three places, open now

Design partners shape the Workspace and the certification with us, on their own warehouse, before anyone else uses it.

What we ask

  • A named case study once your layer is live
  • A reference call with a prospective customer
  • A monthly call for the first two quarters

What you get

  • Design partner terms for the first year
  • Your price locked for three years
  • A say in how the certification review works, and a place among its first entries
Apply to be a design partner

Write to [email protected] with your company, your warehouse and the agents you run today.

What stays free

The standard stays open

The GASP Standard, its exports and the gasp-standard-mcp package stay free: the standard under CC BY 4.0 and the code under Apache 2.0. The hosted MCP endpoint and its 23 tools stay as they are today. The Workspace adds what a company needs on top: its own state and history, the report page, support and certification.

Try searching for:

↑↓navigate↵select