Möbius
Guides

Govern a warehouse in place

Connect a warehouse, register a table, certify it, and publish a certified view your consumers query, with no data copied into Möbius.

This guide is for Möbius Connect and Möbius Enclave. It takes one warehouse table from connection to a certified view your consumers query, without the rows ever leaving your warehouse. For what "in place" means and how it differs from a held table, read Custody modes first.

Create a connector

You need the Admin or Owner role. Open Integrations → Warehouse Connectors and choose Add Connector.

  1. Give the connector a Name and pick its Connector Type.
  2. Fill in the connection fields for that type (table below).
  3. Under Credentials, enter a Secret reference. On Connect and Enclave, Möbius does not hold your warehouse credentials: you put the credential in your own secrets backend and give Möbius only the pointer, which it resolves on every connection. The form has no password field on these deployments.
  4. Pick the Environment. Every table you register through this connector inherits it.
  5. Set TLS verification (see Choose a TLS verification level).
  6. Check the Certified schema name (see Name the certified namespace).
  7. Optionally choose Test Connection before you save. This test checks the connection with exactly the fields and TLS level you entered, and saves nothing.
TypeConnection fieldsCredential your secret must hold
PostgreSQLHost, Port, Database, Usernamepassword
MySQLHost, Port, Database, Usernamepassword
RedshiftHost, Port, Database, Usernamepassword
SnowflakeAccount, Username, Database; optional Schema, Warehouse, Rolepassword
BigQueryProject ID; optional Dataset locationcredentials (service account key JSON), or a Key file path to a key mounted on the Möbius host
DatabricksWorkspace host, SQL warehouse HTTP path; optional Catalogtoken (personal access token)
MongoDBDatabaseuri (the full connection string)
OracleHost, Port, Service name, or a full connect descriptor; Usernamepassword; for mutual TLS also walletPem and walletPassword

The secret is a JSON object whose keys are the credential fields above. For an Oracle wallet, read Oracle wallet: converting to ewallet.pem.

The connector's database identity needs two kinds of access: read access to the tables you will govern, and the right to create a schema and views in the certified namespace. Möbius publishes certified views with CREATE SCHEMA IF NOT EXISTS and CREATE OR REPLACE VIEW.

A new connector is saved unverified. Möbius refuses to read through it until you verify it.

Name the certified namespace

The Certified schema name is the schema in your warehouse where Möbius publishes certified views for this connector. The form pre-fills it from the connector type and environment, for for an environment named Production, certified_production on PostgreSQL or CERTIFIED_PRODUCTION on Snowflake and Oracle. That way two environments on one physical database never overwrite each other's certified views. You can change it, but Möbius refuses a name that:

  • is already used by a connector in a different environment on the same physical database, or
  • is this connector's own source schema, or its export namespace for held tables.

Treat this schema as Möbius-owned: none of your own pipelines should write to it. To change it later, use Certified schema on the connector's row.

Choose a TLS verification level

Each connector carries its own verification level. New connectors start at the strictest one.

OptionWhat is checked
Verify certificate and hostname (recommended)The certificate chain and the hostname must both match.
Verify certificate chain onlyThe chain is verified; the hostname is not. Use this when the certificate does not match the address you connect to.
Encrypt without verifyingTraffic is encrypted, but Möbius does not check who is on the other end.

For the two verifying levels you can paste a CA certificate for a private or internal CA; leave it blank to verify against the system trust store.

Moving down to Encrypt without verifying is allowed but never silent: the row is labelled TLS: unverified and the downgrade is recorded in the governance event stream. Change the level later with TLS on the connector's row.

The level applies to PostgreSQL, MySQL, Redshift, MongoDB and Oracle connections. BigQuery and Snowflake connect through their vendors' client libraries, which verify by default, so their rows show no TLS label. On Oracle the certificate chain is always verified, and a connect descriptor that would open an unencrypted connection is refused.

Verify the connector

On the connector's row, choose Test Connection. Möbius signs in with the connector's identity and runs a trivial query.

  • Success marks the connector verified, and it becomes available for in-place tables.
  • Failure marks it in error, with the warehouse's message on the row.

Either result is recorded in the governance event stream. Verification proves that Möbius can reach the warehouse and sign in as the configured identity. It does not check object privileges: a missing read or create grant shows up later, when Möbius reads the table or publishes a view.

Today, saved connectors of type PostgreSQL and BigQuery can be verified. For other types, Test Connection on a saved connector answers "not yet supported" and the connector stays unverified, so you cannot yet register in-place tables through it.

If you later edit what a connector points at (its host, database, account or other connection fields, or its secret reference), Möbius marks it unverified again, and reads stop until you run Test Connection again. Changing only the TLS level does not reset verification.

For the CLI, mb connectors list prints each connector's ID, type, status and environment.

Register an in-place table

You need the Editor role or higher. In Data → Data Browser, choose Create Table.

  1. Step 1 — Where does the data live? Choose Warehouse-registered.
  2. Step 2 — Warehouse source. Pick a Warehouse Connector (only verified connectors are listed) and enter the Warehouse table as schema.table_name. Choose Fetch columns from warehouse to pre-fill the columns from the live table; you can still edit each one.
  3. Step 3 — Environment. This is read-only: the table inherits the connector's environment, and Möbius refuses any attempt to set a different one.
  4. Name the table and finish the remaining steps. Its name becomes the certified view's name.

A new in-place table starts quarantined. Registering the same warehouse table twice through one connector is refused. To register from a pipeline, use mb push with --connector and --source (mb push).

Preview live rows

Open the table and choose the Live Preview tab. Möbius reads a random sample (50 rows by default, at most 200) straight from your warehouse through the connector. The rows are shown to you and never stored in Möbius, and each preview is recorded in the governance event stream. Stewards see the same preview in the certification dialog.

Certify the table

Certification runs the certification gate against your warehouse where the data sits: the automated quality checks run as SQL through the connector. Follow Certify a dataset.

When the table certifies, Möbius publishes its certified view automatically. Check the outcome in the table's Settings → Governance section, under Certified View publication. It shows whether a view has been published, its full name, when it went live, and the most recent publication attempt. If a later attempt fails or is refused, the earlier view stays in place and the panel says it reflects an earlier certification.

Point consumers at the certified view

The certified view is <certified schema>.<table name>, a plain SQL view over your source table.

Which columns it contains. The view projects the grain columns first, then each field named in the table's semantic contract, mapped to its source column (or to the source expression the contract declares). Source columns that are not in the contract are not in the view. If the contract names no fields at all, the view selects every column, so define the contract before you certify.

What to grant. Möbius does not issue grants. Give your consumers read access to the certified schema, and keep write access to it for the connector's identity only. Whether consumers also need access to the underlying source table depends on how your warehouse checks permissions on views.

Personal data in the view. The certified view shows personal columns as stored. It lives in your warehouse, so your warehouse's access controls and masking apply to it. Reads of the same table through the Data API and Data MCP leave Möbius and are masked; see How Möbius masks personal data.

Consumers can also read the table through the Data API and the Data MCP. Those reads go through the connector, and every response carries the Governance Envelope, described in the GraphQL reference.

Fence the view to rows Möbius has checked

By default a certified view shows the source table as it stands, including rows added after certification. To limit it to rows Möbius has actually checked, declare an output-gate cursor: a column on the source that only increases as rows arrive, such as a load timestamp, an integer ID, or a time-ordered ID (UUIDv7 or ULID). Today this works on PostgreSQL connectors only.

A steward declares the cursor through the output-gate fields of the update_semantic_contract tool (Workspace MCP) or the matching Workspace API call. Möbius checks that the column exists on the source and that its type carries an order, and refuses the declaration otherwise.

At certification, Möbius records the highest cursor value it has checked, the watermark, and publishes the view with a filter that serves only rows up to it. Rows past the watermark are withheld from the view until they pass the same checks.

When new rows fail a check, the policy decides what happens:

  • Hold (the default). The watermark stops at the last clean row. Nothing past it is served until the failure is fixed at source and re-checked.
  • Exclude. The watermark moves past the failures, and the failing rows' keys go on a block list that the view filters out. This needs a key that uniquely identifies rows; without one, Möbius falls back to holding. You can set a cap on how many rows may be excluded.

The enforcement posture dial for the table's environment also applies. When the dial is set to disclose rather than enforce, the watermark advances past failures and the failures are reported but not withheld. When enforcement is off, the check is skipped and the skip is recorded.

How consumers are told what was withheld

  • Through the Data API or Data MCP, the Governance Envelope reports where the read was served from (the fenced certified view, or the source table when no view is published or no cursor is declared), the watermark, whether Möbius knows of failing rows past it, and when it last checked.
  • In your warehouse, the governance catalog reports the same state for anyone querying with SQL (next section).

Keep the certification current

Möbius re-checks in-place tables when they are used, not on a timer:

  • Incremental re-gating. When a fenced table is read through the Data API or Data MCP, Möbius checks only the rows past the watermark, in bounded batches, and moves the watermark if they pass. The read is served immediately; the check runs afterwards, at most once per window for a busy table.
  • Schema drift on read. A read through the Data API or Data MCP also triggers a check, at most once per window, that the warehouse schema still matches what was certified. A mismatch files a recertification request, listed in Data → Quarantine → Re-certification and by mb recertification list.
  • Freshness on every read. Each certified read is checked against how long ago the table was certified. The read is still served, and a stale read is recorded.
  • Re-check now. In Data → Quarantine → Output Gate, each table with open failures shows a card. A steward can choose Re-check now to run the same check immediately, for example after fixing data at source. Acknowledge records that the evidence was seen; it does not move the watermark.
  • A re-check schedule, if you want one. With the cursor declaration, a steward can ask Möbius to re-run the same check every 1 to 168 hours. The schedule is yours; clear it and Möbius goes back to checking only on access.

Read the governance catalog in your warehouse

On PostgreSQL, Möbius keeps a view named __governance in each certified namespace, with one row per certified in-place table in that namespace. Query it with your own tools:

ColumnMeaning
table_nameThe certified view's name
environment_labelThe table's environment
pinnedWhether a watermark fences the view
vouched_as_ofWhen Möbius last vouched for the table: when the watermark last moved, or the certification time if the view has no watermark
fence_value, fence_kindWhere the watermark sits, in the cursor's own terms, and how to read it
last_checkedWhen Möbius last looked, which is not a claim that the data was clean
open_rejectionsOpen failure records for the table, as of label_written_at
gate_modeThe enforcement posture at the last evaluation
label_written_atWhen this catalog was last rewritten

Möbius rewrites the catalog when a certified view is published, when a watermark moves or is re-confirmed, when the certified schema is renamed, and when a table is deregistered.

What is not available on in-place tables

Your warehouse holds the rows, so Möbius does not write them:

  • No row editing. Creating, updating, replacing, deleting or bulk-updating individual records is refused for in-place tables. Change the data at source.
  • No row export. Exporting records from Möbius is refused; consumers read the certified view.
  • No environment change. A table's environment always follows its connector.

Deregistering a table removes its governance record and drops its certified view. Your source table is never touched. See mb delete.

On this page