AirCTRL
AIRCTRLGoverned AI gateway + secrets vault
Build AI applications on explicit boundaries, not scattered keys. AIRCTRL pairs a governed model Gateway with a client-encrypted Vault for secrets and environment variables, so teams can scope access, separate environments, and review activity.
Claude Code, Cursor, Codex, or your own agent.
Verify access. Route models. Apply usage and spending limits.
Connect supported cloud providers or local models.
Secrets & environment variables
Build with development access.
Test with separate credentials.
Limit access to approved workloads.
Separate environments, separate grants. Vault encryption does not cover Gateway’s server-decryptable provider keys. An authorized app or agent that receives a decrypted secret must still be trusted.
Why Gateway + Vault
A model connection does not manage the rest of your application’s secrets. A shared .env file is not an access-control system. AIRCTRL puts routing controls and credential management in one product family, with explicit boundaries around who can use what and a record of the activity.
Encrypt
Vault encrypts secret values on your device with AES-256-GCM. The service stores ciphertext and wrapped keys; authorized clients hold the keys needed to decrypt. API keys, tokens, and sensitive environment values have a managed home instead of scattered copies.
Authorize
Identity, account membership, operation permissions, and resource access are checked separately. Scope human and machine access to the project and environment, so a development agent does not automatically receive production credentials.
Verify
Cryptographically linked, append-only audit events make changes to recorded history detectable. Review access and changes without logging decrypted Vault values, alongside usage and spending for requests routed through Gateway.
Who it’s for
For AI builders, development teams, and platform owners who need to turn a working prototype into an application with deliberate access, data handling, and evidence.
Organize settings and secrets by project and environment. The same variable name can have different values and permissions in development, staging, and production.
Use supported SDK, CLI, and MCP workflows deliberately. CLI child-process injection can supply an authorized app without returning its secrets as a model tool result. The receiving runtime still needs to be trusted.
Remove access that is no longer needed. Rotate exposed credentials with the service that issued them, update dependent apps, and verify the old key no longer works. Revoking Vault access cannot recall a value already copied.
Take a closer look
Explore how Gateway and Vault fit your stack, then review the security architecture against the requirements of your application.
