Describe the system you need. Governed agents build it.

Everything a business application needs, generated and governed

Most organizations run their regulated processes in spreadsheets, shared inboxes and one-off database apps that nobody can audit. DXMachine replaces them with real applications built on one governed foundation.

Working running in development builds · Next the current build stage · Planned scheduled after it. Roadmap →

State machines are the rules, not a diagram of them

In most platforms a process flow guides the user through a screen, and the underlying record can still be edited into any state. In DXMachine the state machine is enforced at the record. A transition that isn't defined can't happen, whether it comes from the form, the API or an agent.

Because the lifecycle is data rather than code, it is versioned like everything else. You can see exactly which rules were in force on the day a record moved, and a change to the rules goes through its own approval.

Generate it with a wizard. Keep changing it for the life of the app.

The App Configurator works the same way as our Industry Configurator: a short guided wizard. It starts from the industry personality you already built, so the processes you selected become candidate applications and your terms become the names. You describe what the app has to do, governed agents draft the specification, and you review it before anything runs.

Review the spec the agents drafted

The spec is a readable record of what the app will be: each row declares a table, a relationship, an index, a state, a separation-of-duties rule or a report. Nothing is published until an owner has approved it.

ComingThe App Configurator is our next release. Its first target is Chandra Passport, General Reasoning's own access product, which we are generating from a spec instead of hand-building.

The spec is where an app starts, not where it stops

Regulations change, and so do the processes built on them. Every mechanism used to generate a DXMachine app stays available inside it for as long as it runs. You don't regenerate the app or schedule a migration project. You change it in place, through the same approvals, and every version stays on the record.

Agents build under the same rules as people

Every AI agent in DXMachine is a named principal with a bounded capability envelope. An agent can propose a schema change, draft a form or advance a work item, but only as far as its role allows, and through the same state machines and gates as everyone else.

Work is pulled, not pushed

DXMachine began as a value stream manager, and flow still runs through the whole product. Strategy enters at the top and is vetted at each level before anyone commits capacity to it. Work is pulled into execution only when there is room, under strict WIP limits and aging controls, so nothing sits unseen in a queue.

Alongside your ERP, not instead of it

You don't have to rip anything out. Keep your ERP and CRM as systems of transaction. Move the regulated processes that have to be proven, such as complaints, change control, inspections, exceptions and approvals, onto DXMachine, where every step is attested.

One application shape, repeated across regulated work

Most compliance software is the same few things over and over: a register, a lifecycle, approvals with separation of duties, expiry dates and evidence. DXMachine builds that shape once, properly governed, and generates it for each domain. These are the categories where it fits best.

By domain

The regulatory domains below are already modeled in the Industry Configurator, and the operational domains (project management, IT service management and HR) need no regulatory model at all. For each one we list the established tools in that category, and just as deliberately, what stays in your existing systems: DXMachine governs the regulated process and leaves the systems of transaction where they are.

Product names identify the category DXMachine competes in and are trademarks of their respective owners. No affiliation or endorsement is implied.

How DXMachine compares

Enterprise suites and low-code platforms are excellent at breadth. DXMachine is built for the part they can't do: proving to an examiner that the application, its rules and every action taken in it were authorized and unaltered.

Reachability is not authority

An AI adversary doesn't attack one application at a time. It builds the whole graph of your systems, identities and data flows at once, and walks the edges between them. That is why every product in the General Reasoning stack follows the CRC standard (Consolidate, Reduce, Close): fewer surfaces, fewer edges, and every remaining edge governed.

Where DXMachine stands

DXMachine is under development, and we would rather tell you exactly where it stands than oversell it. It runs on Chandra Enterprise, which is in beta with customers today. Each stage below makes a wider set of applications credible.

Pricing you can model

The same three line items as the rest of the General Reasoning stack.

See current pricing →