How we build

One factory. Many workspaces.

Every Frontifier product comes off the same line, so a fix in the core reaches all of them.

Three layers.

Whatever a module declares gets the core for free: role checks, approval limits, the audit trail, metering, the decision inbox and agents.

Industry packs14 packs, from auctions, real estate and retail to healthcare, hotels and manufacturing. Each adds its words, rules and agents.

ModulesContacts and KYC, invoicing, bank, books and ZATCA e-invoicing, shared by every business.

CoreCompanies, people and roles, approvals, events, ledger, agents, plans and metering, and the API.

Everything is a command. People, agents and integrations change data the same way.

1A requestFrom a person in the web app, an API token or an agent.

2GuardrailsIs the pack on? Is this role or agent allowed? Is it over their limit?

3ApprovalOver the limit, it waits in the decision inbox for a second person.

4Business rulesThe module or pack does the work, and the ledger posts balanced entries.

5Event storeAn append-only event records who acted, why and which approval allowed it.

Each agent has one job, its own permissions and a spending cap.

Exceptions go to a person, and above their limit, to a second one.

Right to left is built in, not added later.

Each company is walled off in the database. Several products run in your cloud too.

Books must balance, events cannot be edited, and every action is attributed.

Connect Claude, ChatGPT, Copilot Studio or n8n by MCP or the API, each with its own limits.

Start from a product or from the core.