Run all your companies as one organization.
Your companies keep their own records and approvals. The organization holds what they share: the product catalog, rules and add-ons, processes and stages, dashboards and reports, plus promotions from sandbox to production, security, webhooks and usage.
In figures
- 39Countries with a jurisdiction profileCounted in the platform’s code.
- 61Identifier types: tax, company and moreCounted in the platform’s code.
- 8Languages of the site, the console and the helpEnglish, Spanish (Spain and Argentina), Portuguese, French, German, Italian, Dutch.
Counted in the platform’s code or measured on the A-REX test environment, November 2026. Not customer results.
The problem
From companies on their own to one organization
A group of companies repeats the same setup, and drifts apart.
The organization owns what is shared. Each company keeps its own records, approvals and keys.
The same setup, again and again
Every company sets up its products, rules and forms by hand, and none of them match.
From practice to production
What was rehearsed in a test company is typed again in production, with new mistakes.
No view of the whole
Security, integrations and usage are checked company by company, if at all.
What it does
Everything the organization owns
Companies and people, dashboards and reports, the product catalog, rules and add-ons, processes and stages, updates, support, webhooks and the audit log, in one place.
Read the full moduleSecurity for every member
Two-factor sign-in for every member, with its coverage shown, fixed sessions, who may stop deliveries, legal holds and how long the read log is kept.
Read the full moduleWebhooks for the organization
Signed events about companies, members and promotions, sent to your systems, with retries and a history of each delivery.
Read the full moduleUsage you can see
What each company used this month, by kind: AI, recording on the ledger, automation runs, report runs, new lots. Sandboxes are never billed, and users are unlimited.
Read the full moduleEach company in its own time
A company's time zone follows its legal home unless you set one. Report periods, schedules, the nightly anchor and every date on screen follow it.
Read the full moduleHow it works
From a sandbox to companies in production.
Set up in a sandbox
Practice data and simulators, with nothing real at stake.
Share what is common
Publish the catalog, rules and processes once, for every company.
Plan the promotion
A dry run shows what would be copied, item by item.
Approve and run
A second owner or administrator approves; the copy runs and can be run again.
From practice to production
Rehearse with practice data and simulators in a sandbox company, then promote what works.
- A sandbox says so on every screen.
- Simulated results never count as evidence and are never promoted.
- Members are invited again; integrations need your own credentials.
What the organization holds
The organization is the umbrella over your companies. People of the organization see only the companies they are assigned to.
| Area | What it holds |
|---|---|
| Companies and people | Companies, members, roles per company and promotions. |
| Shared libraries | The product catalog, rules and add-ons, processes and stages, dashboards and reports. |
| Promotions | Setup and master data from a sandbox company to production, after a dry run and a second approval. Records, evidence and simulated results are never copied. |
| Security | Two-factor sign-in for every member, sessions, who may stop deliveries, legal holds, the read log and a verified domain. |
| Webhooks | Signed events about the organization: companies, members, promotions. Each company also has its own webhooks. |
| Billing and usage | The plan belongs to the organization. Usage by company and kind, alerts at the thresholds you set, and sandboxes never billed. |
| Not yet | Single sign-on and user provisioning from your directory. |
Who uses it
People of the organization see only the companies they are assigned to.
Organization owner
Sets security, approves promotions and sees usage.
Organization administrator
Publishes the shared libraries and plans promotions.
Company owner
Keeps the company's records, approvals and keys.
Developer
Connects your systems to the organization's webhooks.
Every proposal reads as one business sentence with who asked, what it affects, the risks and who still approves.
Resources
The guides, the open standard and the details behind every screen.
- GuideSet up a group of companiesCreate a group, give it one product catalog and the policies its companies inherit, add its companies, and let each company adopt the group's products.
- ModuleOrganization in fullEvery module in full: what it records, who approves and what it checks.
- GuideHelp centerGuides for every screen of the console
- StandardThe A-REX standardThe open standard, kept by the A-REX Foundation
- DevelopersDevelopersAPI, events, signed webhooks and the MCP server
- TrustSecurity and trustApprovals, keys, personal data and agents
Bring your companies together.
Tell us how your group is organised. We will set up an organization with a sandbox company for each of them.
Explore more