Time Data Management. On Your Own Network.
Airlock is the backbone of time data management in Yamazo: shared Studio projects, master data, shop-floor video and approvals in one place, on a hub you run yourself.
Three Building Blocks
One Project Repository
Studio projects are saved to one hub. A version check stops silent overwrites and a lock keeps two people from editing the same project at once. The last 20 versions of each project are kept (configurable).
Shared Master Data
Facilities, departments, lines, stations and operators are kept once and used by every Studio and Companion client.
Traceable Changes
Every save, upload, lock and approval is written to a hash-chained change log. Allowance table releases can require a second person.

The Companion web app
Record shop-floor video in your browser, push to Airlock in one tap. No install — Companion is its own product, the shop-floor leg of Airlock. Airlock and Companion come with every active Studio licence and are not sold separately.
What It Does
Client Access
Studio finds the Airlock on your local network and connects with a short-lived pairing code; in air-gapped mode it pins the server's root certificate. Every client gets its own token; Companion seats are capped at your active Studio licenses.
Change Log
Every save, upload, lock and approval is chained to the one before it, and the chain can be verified per project. Studio's own reads are not logged; every data export to a connector or from the TDM catalogue gets its own export record.
Supplier Inbox
Send a supplier an invite link; they upload a video and one reviewer approves it before it reaches a project. Links expire (7 days by default) and work once. Suppliers can also send their study through the Airlock as a signed, encrypted pack.
Project-Scoped Access
You decide which client can reach which project, granted per project. Rights also depend on the kind of client: a shop-floor phone or a supplier drop can only do its own job, and a read connector can write nothing.
Backup Script
A script you can schedule copies the data and videos. Restoring is done by hand.
Optional Encryption at Rest
Set a key and the database and videos are encrypted with AES-256; without a key it stays off. The hub serves over HTTPS.
Second-Person Approval
Approved times (standard and setup times) and, when you switch it on, the allowance table take effect in Studio only after a second person approves them at the Airlock desk. Whoever proposes cannot approve their own proposal.
Signed Receipt
Every approval comes with a receipt signed by Airlock. Studio checks the signature against the key it pinned when it was bound; an approval that cannot be verified changes nothing.
Unbinding Needs Approval Too
Detaching Studio from Airlock governance also needs a second person's approval at the desk. The rules cannot be bypassed by one person's decision.
Read-Only Connector
BI, ERP and MES pull changed projects and master-data versions incrementally, with a credential that cannot write. Airlock does not look inside the data; your connector maps the bundle to its own fields. There is no import endpoint, so authority over the data stays in Studio.
Outbound Connections
Airlock connects out for only three optional jobs: pulling the supplier inbox, renewing a public certificate and sending a supplier pack to a partner you link, only to hosts you allow. All three stay off until they are set up.
Your Data Path
Inbox
Companion
Record & Send
Other apps
HTTPS channel
Station-01
Line A
Station-02
Line B
Local Database
AES-256
??? External
Video and study data stay on your local network.
Development Status
Airlock is in pilot. The hub, the Studio integration, the approval desk, the read-only connector and role separation are built; distribution across sites and an independently witnessed audit trail come next.
One Hub for Your Time Data
Projects, master data, video and approvals on your own network.
Developed by Opsida Technology.