Airlock — The Runtime Behind the Apps

The safe boundary#

Airlock is internal. It is the runtime that the platform's capabilities actually run inside — a controlled boundary that every app request passes through, rather than calling raw services directly.

• Internal — not in the client sidebar.
• Runs the capabilities MAIA designs.
• Every request passes through it under control.

The other half of MAIA#

Airlock pairs with MAIA. MAIA is where a capability is designed; Airlock is where that finished design runs when someone uses it. One defines the tool, the other executes it.

• MAIA designs a capability; Airlock runs it.
• Design-time hands the finished tool to run-time.
• Together they cover defining and executing a feature.

Why a boundary matters#

Running everything through one controlled gate means requests are checked and the same rules apply every time — the apps stay predictable and contained instead of each reaching out on its own.

• A controlled gate means requests are checked, not free-for-all.
• The same boundary applies the same rules every time.
• Keeps the apps predictable and contained.

For the team#

Airlock is internal plumbing. Users never open it — this guide explains the boundary that lets the apps they use run safely.