Run the whole company from one place, top down.
VXCTRL is the enterprise control tower. It is where a large company runs itself from the group down: its people, its AI agents and its machines; its store and server fleet; its web estate. Every action is governed and on the record.
A global restaurant group, as the example: managed at the group, by country, by brand, by market and by store, down to its people's AI agents, the computer an employee signs in on, and the robot making the taco. The six levels are the ones the product enforces.
What you are looking atThe product itself, running below on a made-up global restaurant group. Pick who you are, from the group chief executive to the robot on the taco line, change something, and read what the change did.
i
What goes hereWho you are signed in as. The list runs from the group chief executive at GLOBAL down to a crew member, an AI ordering agent, a kitchen robot and a manager's laptop at NODE.
Who can change itIn the product, nobody: your session is issued to you at sign-in and carries exactly what you can see and manage. The switcher exists here only so you can stand in several places and compare.
What changing it doesEverything else on this page re-scopes. The tree and its counts, the fleet, the web estate, the policy table, the approval queue and the AI grants all narrow to what this member can see, and the actions narrow to what it can do. A robot or a laptop is scoped exactly the way a person is.
Why can I see this?You are Marguerite Ashdown, and you lead Orrinvale Dining Group (GLOBAL). You see 71 of 71 modelled members: your own node and everything below it. In the sample company's full count that is 2,471 stores and 91,829 people, AI agents and machines. Nothing sits above you or beside you: this is the top of the tree. You can manage members below GLOBAL, not other members at GLOBAL, and not yourself.
Org and reach
This is Orrinvale Dining Group, a fictional global restaurant group, drawn as the six-level tree the product enforces: the group at GLOBAL, each country at COMMAND, each brand at ORG, each market at OPS, each store at FIELD, and every person, AI agent and machine at NODE. You are seeing the 71 modelled members inside your own reach and no others. Open a unit to drill down, click any card to open it, then change something and read what the change did.
Large numbers are shown as counts with a drill-down, not as thousands of cards. The counts are the sample company's illustrative size, not a measure of what the product has been tested at. Eight stores are modelled in full, member by member, so the rules can run in your browser.
Select a member to open it.
Every field carries a small (i) that says what goes in it, who is allowed to change it, and what changing it does.
What does VXCTRL actually run?
Five things, each of them in the product today, and each scoped by the same tree: the org and everyone's reach in it, the server fleet, the web estate, AI, and the approvals and record that hold it all together.
From the group to the robot
One six-level tree, from the group down through countries, brands, markets and stores to every person, AI agent and machine. Reach is worked out from position: each member sees its own node and everything below it, never sideways into a sibling brand, and manages only what is below it. Each sign-in carries exactly that scope. A person, an agent or a machine is added as a NODE through the same governed write as any other change.
In the demo: Org and reach, then "view as".
Every server, with its health
The server fleet, from the group's own servers to the server in each store: the hosts, their health and their capacity, shown against the brands and sites they serve. Reach applies here as everywhere: a store manager sees her store's server, a country sees its own, and only the group sees all of it.
In the demo: Fleet.
Every brand's sites, page by page
Every brand's public web sites in one tree, page by page. Each page is graded for search and AI readiness: title, meta description, structured data, social tags, canonical link, and real text without JavaScript. Pages that do not answer are flagged, and so is any site whose sitemap and page list disagree. The domains themselves, with their DNS and certificates, are the Domain engine's.
In the demo: Web estate.
Which models each level may use
Which AI models each level may use, with interactions logged. A level can only ever offer a subset of what the level above it has, so taking a model away at the top takes it away everywhere below. The AI agents themselves are NODEs in the tree, scoped like anyone else.
In the demo: AI governance.
Every action on the record
Deny-by-default policy decides every governed action. Facts become of-record only through an approval gate that re-checks the approver and requires cited sources. Every action and every refusal is logged to a hash-chained operational log and sealed onto an append-only audit ledger.
Two-person control is built and ships switched off: a setting, available to turn on. Identity lifecycle and access review are built and not yet enabled.
In the demo: Policy, Approvals, Audit log.
Governance is how it works
Every write, whatever it touches, takes the same path in the same order: Core, Identity, Hierarchy, Policy, the engine that owns the domain, Monitoring, then Audit. Identity says who is asking, Hierarchy says whether the target is inside their reach, Policy decides, and nothing reaches the engine that does the work until those three have agreed. That is what lets one place run everything without anyone being able to reach further than their position allows.
What should I actually do with it?
Four things, in about three minutes. Each one is a rule you cannot really believe from a sentence but can see happen.
Change who you are
Use "view as" to become the United States country president, then a brand president. The other country, then the sibling brand, disappear: not greyed out, not empty, absent, and the store and headcount totals shrink to what is inside your reach. Then become the taco line robot: it sees one node, itself, because nothing sits below an individual and a machine is governed exactly like a person.
Move somebody and read the consequence
Open a member on the Org and reach tab and change who they report to: move a country president under a market, or a market under another brand and watch its stores move with it. The note that comes back says what left their reach and what entered it, and how many audit entries were written. Sessions are scoped at sign-in, so the next session issued to that member carries the new scope.
Try something you are not allowed to do
As the Texas market director, try to move anybody. Hierarchy is perfectly happy, because the target is below you, and it is still refused, because no rule in the table allows it. That is deny-by-default, and it is the whole mechanism. Then add the missing rule on the Policy tab and try again.
Push a fact up through a connected product
On the VX Terminal tab, which shows what VXCTRL looks like when a customer also has VX Terminal, propose an open item to VXCTRL. It arrives in Approvals carrying the trust grade the gate derived from its cited sources. Approve it and it becomes of-record, and the DIN CTRL tab shows the same record's new state. Switch on "require a second approver" first and you will need two different people to agree, on the same write, byte for byte.
Every one of those, allowed or refused, is on the Audit log tab with the actor, the target, the outcome and the rule that decided. Press Reset demo at any time and the sample company goes back exactly as it was.
Does VXCTRL need anything else?
No. VXCTRL stands alone. Two other products connect to it when a customer has them: VX Terminal, sold separately, is where teams do their daily work; DIN CTRL, sold separately, keeps the evidence record of what people and AI agents did, with a trust mark on every entry.
When they are connected, the traffic is deliberately one-directional. Data moves up only through approval, so nothing becomes of-record because a system claimed it. Permissions move down only through VXCTRL policy, so nobody gains reach because a system asked for it. The two tabs marked "Connects" in the console above show what that looks like, on the same sample company.
Want to see it against your own company?
Email us and describe its shape: how many countries, brands, markets and stores, what mix of people, AI agents and machines, and what you need to be able to prove afterwards. A plain email reaches a real mailbox.
Questions people ask before they commit
What is VXCTRL?
VXCTRL is the enterprise control tower: one place where a large company runs itself from the top down. Its people, its AI agents and its machines; its store and server fleet; its web estate. Every action is governed and on the record: each governed action is checked against the org tree and the rules, and the outcome is sealed onto an audit ledger.
Who is VXCTRL for?
Large, multi-site companies that need to run everything from one place, top down: multi-brand groups, franchise networks, and multi-site retail and restaurant operators, with a mix of people, AI agents and machines, who need authority, visibility and accountability enforced rather than just documented.
Is the demo on this page real, and is the data real?
The behaviour is real: the visibility rules, the downward-management rules, the deny-by-default policy evaluation and the approval gate all run the same logic the page describes. The company is not. Orrinvale Dining Group, its brands, people, stores and web sites are fictional; it is not a customer and it is not based on one. Its store and headcount totals are illustrative counts, not a tested capacity. Everything runs in your browser, nothing is sent anywhere, and nothing is saved.
What are the six levels?
GLOBAL, COMMAND, ORG, OPS, FIELD and NODE. In a global restaurant group, GLOBAL is the group, COMMAND a country, ORG a brand, OPS a market, FIELD a store, and NODE a person, an AI agent or a machine, such as the employee laptop, the POS terminal, the kiosk or the kitchen robot.
Does VXCTRL govern AI agents and machines too, or only people?
All three. A NODE is an individual, and that individual can be a person, an AI agent or a machine. A drive-thru ordering agent, the laptop an employee signs in on and the robot making the taco are each a NODE under their store, governed exactly like anyone else. AI governance additionally controls which AI models each level may use, and interactions are logged.
Can someone at one brand see another brand's data?
No. Visibility flows down: you see your own node and everything below it, never sideways into a sibling brand. The same brand in another country is a separate unit under a separate country, so it is outside your reach too. Management is strictly downward as well, so you can manage below you but not at your own level.
What does VXCTRL show about our web sites?
The web estate: every brand's public sites, page by page. Each page is graded for search and AI readiness, from the title, meta description, structured data, social tags, canonical link and how much text it carries without JavaScript. Pages that do not answer are flagged, and so is any site whose sitemap and page list disagree.
Do I need VX Terminal or DIN CTRL to use VXCTRL?
No. VXCTRL stands alone. VX Terminal, where teams do their daily work, is sold separately, and DIN CTRL, which keeps the evidence record of what people and AI agents did, is sold separately. When a customer has them they connect to VXCTRL: data moves up only through approval, and permissions move down only through VXCTRL policy.
What happens when an action is refused?
The write stops, and the refusal is still recorded. Monitoring logs every action and every refusal to a hash-chained operational log, and the outcome is sealed onto an append-only audit ledger, so a denial leaves the same kind of evidence as an approval. The demo's audit tab shows both.