Apply request policies in the browser context.
Configure host, path, and method rules and substitute configured phantom tokens on intercepted browser requests. This prototype is not an OS-level egress firewall.
Explore the workflow → ISOLATED BROWSER TESTING FOR CI
Turn browser explorations
into repeatable tests.
Record a browser journey, compile it to Playwright, then submit runs from CI through Airlock Cloud. Review the response from your deployment; advanced sandbox capabilities are evolving.
✓ CI-first API✓ Browser test tooling✓ Run response evidence
Airlock CloudSAMPLE WORKSPACE
ACME WORKSPACE / RUN DETAILCheckout payment
SAMPLERESULT✓ Passed
STEPS18 of 18
EXECUTION42s
Execution timelineSample response
✓Isolated browser readyFresh execution context started
✓Checkout assertions passedTest steps completed successfully
◇Attestation returnedProof attached to run result
All sample checks completePREVIEW DATA
Policy boundaryOutbound request evaluated✓
Run evidenceIllustrative preview
3D execution path · illustrative sample
FROM COMMIT TO EVIDENCE
A straightforward path from your pipeline to a result.
⌘Your CI runnerPush or pull request
⇄Airlock run APIPOST /v1/runs
▣Browser runnerExecution varies by deployment
✓Run responseReturned to CI
A SAFER WAY TO TEST
Confidence belongs in
every pull request.
Airlock provides a run-submission API plus a local Playwright toolkit with request policies, browser-state checkpoints, and evidence utilities.
Reuse browser state for test variations.
Capture browser storage and session state, then restore it into a new Playwright context. These are browser snapshots, not VM memory clones.
View the sample console →Create verifiable execution bundles.
AirlockQA can generate hash-linked ledger entries and signed bundles for verification with the configured key. This does not certify compliance.
See the response path →BUILT FOR YOUR PIPELINE
One request.
A result your CI can use.
The cloud API exposes a run-submission route at POST /v1/runs. Cloud execution is still evolving; confirm the capabilities of your deployment before relying on run isolation or advanced diagnostics.
See the CI/CD setup →GITHUB ACTIONSairlock.yml
jobs:
browser-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm install
- run: npx airlock test --cloud
env:
AIRLOCK_API_KEY: <from CI secrets>READY TO SEE YOUR RUNS?
Open sample workspace ↗Take a look inside Airlock Cloud.
Explore the sample workspace and the current run-submission flow. Sample metrics are illustrative.