User Guide

Introduction

Airlock is a secrets management service, run by Network14.cloud as a fully managed offering. It stores encrypted values behind a plain HTTP API, gates access with per-client keys, and writes every operation to an audit trail. This guide covers everything you need to integrate against it — there's nothing to install or deploy yourself.

Core concepts

Term	Meaning
Owner	A numeric ID that groups access keys and the secrets stored under them. Airlock doesn't have user accounts — an owner is assigned when Network14.cloud provisions your access key.
Access key	A bearer credential sent as the `access-key` header. It identifies the caller, scopes which secrets they can reach, and can be IP-restricted.
Secret	A named, Fernet-encrypted value tied to one owner. Secret names are unique per owner, not globally.
BYOK	"Bring Your Own Key" — an optional per-secret Fernet key supplied by the caller instead of the service default, for extra isolation.

Base URL & request shape

There's no SDK and no request body for most operations — everything is plain HTTP headers. Your managed instance is reachable at:

https://airlock.fastapicloud.dev

A minimal example

curl -X POST https://airlock.fastapicloud.dev/api/create-secret/ \
  -H "access-key: $ACCESS_KEY" \
  -H "secret-name: DATABASE_PASSWORD" \
  -H "secret-value: correct-horse-battery-staple"

curl https://airlock.fastapicloud.dev/api/get-secret/ \
  -H "access-key: $ACCESS_KEY" \
  -H "secret-name: DATABASE_PASSWORD"

Where to go next

Getting Started — get an instance running
Authentication & Access Keys — how access keys and IP allowlisting work
Endpoints — the full request/response spec for every route
Error Reference — every error message, mapped to cause and status code
Security Model — encryption, hashing, and what does (and doesn't) leave the service in traces