Integrations

Connect Tessra across decision, consent, and execution

Tessra sits between where actions are proposed, where humans approve, and where work runs—enforcing policy and recording receipts.

Control plane topology

Decision systems  (agents, Cortex, apps)
        ↓
     Tessra  (policy · consent routing · execution control)
     Snowflake catalog (actions · policies · context · bindings)
        ↓
Consent systems  (human approval & delegation)
        ↓
Execution systems  (webhooks, Stripe, internal APIs)
        ↓
Receipts in your warehouse

Tessra does not replace your agents or your APIs. It governs the handoff between them.

Every governed action flows through three surfaces: where it is proposed, where it is approved, and where it is executed.

Decision systems

Where actions originate.

Snowflake Cortex

Native

Submit governed actions directly from SQL agents using native procedures.

View Cortex integration →

Internal agents / services

Generic

Any system that can call SQL or HTTP can propose actions through Tessra.

Databricks

Roadmap

Unity Catalog governs your data. Tessra governs what your AI does with it. Tessra action requests, policy evaluation, and receipts against your Databricks lakehouse.

Join waitlist →

Consent systems

Where human approval and delegation happen.

Slack

Default

Route approval requests into Slack with structured actions and audit context.

Email

Generic

Send approval requests via email with secure links and response tracking.

Future

ServiceNow, Jira, and internal approval systems can plug into the same consent interface.

Execution systems

Where approved work runs.

Generic webhook

Default

Send approved actions to any system via secure HTTP callbacks.

Stripe

Reference

Execute real payment flows (refunds, credits) with policy and approval enforcement.

Internal APIs

Custom

Connect to your own services (billing, ops, infra).

How it fits in your stack

Decision → consent → execution, with Tessra as the control plane and your warehouse or database as the ledger.

Decision systems propose governed actions.
Tessra evaluates policy and routes consent when humans must decide.
Consent surfaces capture approvals and delegation.
Execution systems run approved work.
Your warehouse or database stores the receipt — Snowflake, Databricks, Postgres, and more.

Action lifecycle

DECISION → CONSENT → EXECUTION → RECEIPT

Request shape

SQL procedures and HTTP callers share the same action lifecycle — propose, evaluate, approve, execute, receipt.

Illustrative Cortex call

CALL APP.REQUEST_ACTION_FROM_CORTEX(
  'customer.credit_issue',
  OBJECT_CONSTRUCT(...),
  'reasoning'
);

Works with Cortex today. Same model applies to other agent systems.

Bring your own database

Snowflake Native App is the fastest path to production today. PostgreSQL, BigQuery, and self-hosted deployments are on the roadmap — Tessra's policy engine, approval gates, and execution dispatch are warehouse-agnostic by design.

Let us know what you need →

Request early access Read the docs