VXCTRL stands alone. Two products connect to it.
The control tower runs the company on its own. When a customer also has VX Terminal, where teams work day to day, or DIN CTRL, where evidence is recorded as it is observed, they connect to VXCTRL, and the traffic between them is one-directional and therefore checkable.
What is each one for?
One of the three runs and governs the company. The other two are separate products that each own a different part of the same loop when a customer has them: doing the work, and recording what happened.
VXCTRL
The enterprise control tower. The org and everyone's reach in it, the server fleet, the web estate, AI governance, and approvals and audit. Where authority is governed and facts become of-record.
VX Terminal
Where teams operate day to day. Connected to VXCTRL, it works inside whatever authority VXCTRL policy has granted.
DIN CTRL
The evidence record: what people and AI agents did, with a trust mark on every entry. Connected to VXCTRL, its records are what the approval gate cites.
On this site, the console on the home page shows a connected install: the two tabs marked "Connects" are VX Terminal and DIN CTRL as they look when attached to VXCTRL, on the same sample company. Each product also has its own live demo on its own site.
Why is the traffic one-directional?
Because the two things moving between these products have opposite risks. Evidence moving up too easily makes the system of record unreliable. Authority moving anywhere but down makes the org tree meaningless. So each direction has exactly one gate.
Data moves up only through approval
Evidence recorded in DIN CTRL does not become of-record by being recorded, and an item in VX Terminal does not become of-record by being raised. Approved facts are promoted into the system of record through an approval gate that re-checks the approver, requires cited sources, and grades trust from those sources as receipted, logged or inferred. The gate refuses raw data dumps, and it never lets a client assert its own trust grade.
Permissions move down only through VXCTRL policy
Authority is not assembled locally in the product where it happens to be used. It descends from VXCTRL policy, scoped by level and by address class, and it is checked against the six-level tree on every governed write. A connected product cannot grant itself reach, and a peer cannot grant a peer reach either, because management is strictly downward.
What is a trust mark, and what is it worth?
A trust mark is what is attached to evidence when it is recorded in DIN CTRL. It travels with the evidence, but the grade that matters downstream is the one the approval gate derives from the cited sources, not one a client declared for itself.
The grades the gate assigns are receipted, logged and inferred. The distinction is the useful part: a fact backed by a receipt is a different thing from a fact backed by a log entry, which is a different thing again from a fact that was inferred, and the system of record keeps that difference rather than flattening everything into "true".
Why are they separate products at all?
Because governing a company, doing its daily work and recording what happened are different jobs, and a customer may need one, two or all three. Keeping them apart is also what keeps the connection honest: a product that could write to the system of record, or hand out its own permissions, would not be connected to a control tower, it would be sharing its database.
The practical test is whether you can answer, after the fact, where a fact came from and on whose authority an action happened. With evidence gated on the way up and authority gated on the way down, and every governed write logged by Monitoring and sealed by Audit, both questions have answers.
Which of the three do you need?
Some companies need the control tower alone; others want the daily working side or the evidence record connected to it. Tell us where you are.
Questions people ask before they commit
Do I need VX Terminal or DIN CTRL to run VXCTRL?
No. VXCTRL stands alone: it is the enterprise control tower, and it runs a company's org and reach, fleet, web estate, AI governance, and approvals and audit on its own. VX Terminal and DIN CTRL connect to it when a customer has them.
Are VX Terminal and DIN CTRL separate products?
Yes. VX Terminal and DIN CTRL are each sold separately. Each has its own live demo on its own site, running on its own fictional sample company.
What changes when they are connected?
Two directions open, each with exactly one gate. Data moves up only through approval: evidence rises to become of-record in VXCTRL only by passing the approval gate. Permissions move down only through VXCTRL policy: authority descends from VXCTRL and is never assembled locally in a connected product.
What is VX Terminal for?
Day-to-day operation. It is where teams actually work. Connected to VXCTRL, it works inside the authority VXCTRL policy has granted, and it can propose a fact to the approval gate; it cannot promote one.
What is DIN CTRL for?
Keeping the evidence record. People and AI agents record what happened there, with trust marks attached. Connected to VXCTRL, that evidence is what the approval gate cites when a fact is promoted, but recording it does not by itself make it of-record.
Does recording something make it official?
No. Approved facts are promoted into the system of record only through an approval gate, which re-checks the approver, requires cited sources, and grades trust from those sources as receipted, logged or inferred. The gate refuses raw data dumps.
Can a connected product grant itself permissions?
No. Permissions move down only through VXCTRL policy, and a client is never allowed to assert its own trust grade. Authority is something a connected product receives, not something it can arrange for itself.