Need to know
Whether people outside the program can even find controlled technical data, and every view and download by those who can.
[ Defense and aerospace ]
Need to know, enforced.
Programs share controlled technical data with suppliers and partners and must show who received what, at which revision. Tabellix keeps drawings and specifications under configuration control, shares them only as far as you allow, and is built to run inside closed networks.
01 What gets asked
What program security and quality ask.
01
02
The revision a supplier built to
The exact revision sent to the supplier, when it was sent, and what they opened.
03
The end of outside access
That supplier access ends when the work does, and that nothing was served after it ended.
04
Configuration control
The engineering change, its approvals, and the revisions it released.
05
Inspection to revision
The first article or receiving inspection result, linked to the revision it was inspected against.
06
What runs on the network
What the software contains, whether it ever reaches outside, and how its license is checked.
02 How Tabellix answers
Controlled, and checkable.
01
Hidden unless permitted
Access is decided by policy and denied by default. People outside a program cannot tell its data exists, and an explicit denial always overrides a grant.
02
Revisions you can prove
Every change creates a new version, minor for drafts and major for releases. A snapshot share binds the version sent, and an engagement report shows what each recipient fetched.
03
Access that expires
Shares and grants are time-limited and revocable, and can require an agreement before any content. A share never serves more than the sharer may still read, checked on every page.
04
Engineering change as a case
An engineering change links the affected drawings and specifications, pinned to their versions. Its approvals are signatures with meaning and a fresh sign-in.
05
Inspections linked to the revision
An inspection result is an event record linked to the exact revision inspected, locked at capture and corrected only by amendment.
06
Built for closed networks
Runs on Kubernetes on premises, designed for air-gapped networks. The license is verified offline and the software never calls home. Images hold one static binary, with signed SBOMs bound to each image.
03 Typical records
Under configuration control.
| Record | Kind | What it holds |
|---|---|---|
| Drawing 7731-200, bracket assembly | document | Minor versions while drafted, a major version when released; the superseded revision kept with its full history. |
| Engineering change ECR-0418 | case record | Affected items pinned to their versions; impact assessment and approvals as lifecycle steps, each signed with its meaning. |
| First article inspection | event record | Part, revision, characteristics checked and result, linked to the drawing revision inspected. |
| Supplier data package | document | Sent as a snapshot share with watermarks and an agreement; what each recipient fetched is reported. |
| Supplier corrective action | case record | The finding, the response and the effectiveness check as lifecycle steps, each step signed. |
05 FAQ
Common questions.
01Which cryptography does Tabellix use?
Cryptography is limited to FIPS 140-3 approved algorithms, and the mode is checked in the running deployment. Every file is encrypted with its own key, keys are held in a key manager the deployer supplies, and service links can use TLS 1.2 or 1.3.
02Can AI agents be kept read-only?
Yes. Your agent policy decides allow, confirm or deny for each action, and a read-only agent policy refuses every write. An agent never gets more than the person it acts for, and never changes the configuration on its own word.
03Does Tabellix need a connection to its vendor?
No. The license is a signed file verified offline. It warns before it expires and never blocks reading or exporting existing records.
04How does an engineering data or supplier portal vendor embed Tabellix?
Your product keeps its viewers, structures and workflows. Tabellix is the controlled record underneath, with versions, signatures, shares and the audit trail through one contract over gRPC or REST, and it ships under your brand.
[ Contact ]
Build your product on proof.
Tell us what you build and who audits it. We'll show you how Tabellix fits into your product and how it answers your auditors' most common questions.