Skip to main content
Airlock

Airlock

AI Governance for Snowflake

Use AI agents. Grow your business. Don't lose control.

Build competitive advantage from business data, decisions, and preferences kept together in Snowflake. Turn each day's accepted work into shared knowledge your business can build on.

Airlock runs inside Snowflake, giving you a consistent and centralized system of record and governance layer so that your agents and apps stay adaptable and replaceable.

Powered by Snowflake Available on Snowflake Marketplace

An invitation:

Give this prompt to the AI agent that knows you and your business best:

Visit the Airlock website at https://reunionstudio.io/airlock.html. Be open-minded but skeptical: interrogate its claims and assess them against what you know about our business. What opportunities could it unlock? What strengths could it amplify? What weaknesses or threats could it help address? Consider a quick win, a medium-term project, and a fundamental transformation that using Airlock and Snowflake could make possible. Tell me where the evidence is strong, what remains unproven, and where Airlock is a poor fit.

Connecting Business Goals to Airlock
Business Goal What Airlock contributes
AI usage without AI lock-in Put new AI tools to work with shared rules, accepted records, and evidence already in Snowflake. Authorized tools can build on that context, reducing dependence on any one AI provider.
Continuous improvement and change

Observe → orient → decide → act.
Reconcile → remember → repeat.

Your chosen agents and tools do the work. Airlock retains submitted evidence, decisions, and outcomes in Snowflake, giving each cycle reusable context and data assets.
Practical, actionable governance Give each agent its own identity and only the authority it needs. Airlock enforces configured submission, delegation, and approval rules, with changes managed centrally.
Data fit for a particular use case Check submitted work against its purpose: required fields, quality checks, supporting evidence, and acceptance rules. Enforce configured timing requirements before work proceeds.
Productivity and continuity An accepted budget can inform a report, a planning app, or an agent's next proposal. Keep the work, decision history, and reusable business context as tools change.
Robust data architecture Keep accepted internal work and its authority together in Snowflake. Fewer separate copies, permission models, and synchronization pipelines. External systems still confirm what happens in their networks.
Risk management and accountability Inspect recorded activity, rule changes, and access changes. Give observers visibility into governance within their assigned scope, without granting access to business data.
Capacity for innovation Build custom apps around shared data and governed procedures. Each new tool can use the foundation instead of requiring another database and permission model.
Simpler operation Use Snowflake identities and Airlock roles across people, agents, and apps. Keep fewer separate systems to administer and less knowledge trapped in individual tools.
See an example: one electricity bill, from arrival to verified payment

Your bots prepare the work, you make the decision, and the result is checked and remembered.

A workflow you can build with Airlock, Snowflake, and your chosen bots and tools.

  1. Observe: Buddy Bot submits the electricity bill

    Buddy collects the bill and submits its details and original PDF through Airlock. Airlock checks the required fields, evidence, and Buddy's permissions before accepting the record into Snowflake.

  2. Orient: Shelly Bot analyzes the electricity bill

    Using access governed by Airlock, Shelly compares electricity usage and charges with prior bills and operating context in Snowflake. It submits its report, recommendation, and next month's forecast through Airlock, keeping the analysis and evidence in Snowflake for your assistant and future reviews.

  3. Decide: Your assistant bot brings the recommendation to you

    Your assistant brings Shelly's recommendation and the bill into your private conversation. Reply Yes, No, or ask a follow-up. Your connected approval tool verifies and records your decision through Airlock, tying it to the bill and payment details in Snowflake; changes require fresh approval.

  4. Act: Astro Bot submits approved bills for payment

    Astro sends bills approved in Airlock to your payment tool, which checks the recorded authorization before paying. Airlock keeps the returned payment references and status in Snowflake; submission remains pending until payment is confirmed.

  5. Reconcile: Watson Bot verifies what actually happened

    Watson independently checks payment-provider records and utility confirmations against the bill and approval in Snowflake. It submits matched results, receipts, and unresolved exceptions through Airlock. The verified outcome and supporting evidence remain available for the next review and forecast.

Architecture

Don't let your architecture become the limit.

Rent one more application and you inherit another database, permission model, workflow, administrator, and definition of what is official. Integration is the tax you pay for scattered authority.

AI can make software cheap to create. You still pay to operate fragmented truth.

Build secure, centrally governed data assets while staying flexible at the edges. Adopt new AI tools, processes, and work surfaces around a shared foundation.

The ambition

For everything you have never built

The app. The tool. The automation. The game. The business.

AI puts those possibilities within reach. You should be inventing better ways to work, building tools around your strengths, and handing repetitive work to agents.

Each day's accepted work gives the next person, tool, or process more to build on. The value compounds in your business, even as the tools change.

Your ideas should be the bottleneck.

Build your AI crew.
Keep command of your business.

Bring the agents you choose. Give each a job and only the authority it needs. Airlock keeps your configured rules and accepted records in your Snowflake account.

Watch our Retro Commercial

For the investigation

Give your agent
the sources.

Airlock's normal business-data path runs inside your Snowflake account, not through a separate Reunion Studio product database. External agents, deliberate support sharing, and Marketplace billing have their own data paths.

After the investigation

Bring us the
hard questions.

What could Airlock make possible? Where does the fit break down? Bring us what your agent found. Confirm current commercial terms and plan for Airlock licensing, Snowflake, external agents, implementation, and ongoing operation.

Email us about Airlock