Enterprise AI · built by APEX
an AI operating system APEX built.
Five Amarok products connect operations, delivery and client visibility — grounded in company records and operating on live work since June 2026.
APEX owns the operating logic, data layer and roadmap. Amarok shows what is happening, what needs a decision and who owns it.
Visit APEX GroupThe product family
Five products. One platform.
One operating record across APEX delivery, client visibility and specialist tools.
01 — Command
Amarok Command
The private operating intelligence the business runs on.
Coordinates delivery, project risk and operational decisions from APEX records. Every answer traces to a source or returns unknown.
Internal · Live in daily use
02 — Client
Amarok Client
The project, visible without asking for an update.
Shows clients current status, milestones, deliverables and approvals without waiting for a manual update.
For clients · Live by invitation
03 — Register
Amarok Register
Full service registration and analytics technology.
One attendee record across RSVP, payment, confirmation, QR code and entry.
For event organisers and attendees · In development
04 — Reach
Amarok Reach
Media buying, planning, optimisation and reporting.
Tracks media spend, delivery and campaign outcomes directly from advertising platforms.
For clients and internal team · In development
05 — Site
Amarok Site
The website, built and then watched.
Builds the site, then monitors its health, security, search performance and content.
For clients · In development
Why it matters
Controlled by APEX.
Built for APEX
Rules come from real delivery work, not generic software defaults.
Controlled by APEX
APEX owns the operating logic, data layer and roadmap.
In daily use
Operating on live client work since June 2026.
One coordinated system. One business pipeline. One standard of excellence.
Engineering principle
Most AI is built to always have an answer. Ours is built to stop.
Every answer must trace to a board, file or ledger. Without a source, it says it does not know.
Enforced in the code, not left to the model's discretion.
Governance
Authority terminates with a named individual.
Automation carries the operating spine. Authority remains human — not as a policy written down somewhere, but as gates in the code with a named person on the other side.
Capital
Payments and financial commitments require named human authority.
Separation
The agent doing the work does not clear its own compliance review.
Identity
Agents use approved company roles, never an employee's identity.
Disclosure
When asked whether AI was involved, APEX answers truthfully.
Evidence
Actions and failures remain recorded and reviewable.
Containment
Bounded autonomy can be paused by the principal.
What it does not do
- It does not replace the people doing the craft or holding the relationship.
- It does not invent prices, terms or facts.
- It does not take instructions from documents it reads.
- It does not mark work complete without an observed result.
Governed workflow walkthrough
Examine it against a live brief.
Send the APEX team a brief or procurement question. The walkthrough follows that exact case: what the system reads, what the client sees, where it stops, and which named person holds authority.
Underneath it
What the loop is actually made of.
The architecture the whole thing rests on, and the part that is hardest to fake.
