Mirage for enterprise teams
One platform, connected to the systems you already run, configured on your own rules, deployed in the environment you choose and run by the engineers who built it. Priced as a platform: by volume, not per user.
It connects to what you already run
Mirage connects the ERP, TMS, WMS, maintenance, telematics and document systems already in place, more than 200 so far, and writes back into them. Nothing is migrated and nothing is replaced.
- With an interface
- Where a documented interface exists, Mirage connects to it.
- Without one
- Where none exists, our engineers build the connector during deployment.
- Construction
- Project management and document control platforms such as Procore and Autodesk Construction Cloud, estimating spreadsheets, and ERP and accounting systems such as SAP, Oracle and Sage.
- Logistics
- TMS and freight systems: in production with Logitude World at OFRET Groupe, and CargoWise through its eAdaptor interface.
- Manufacturing
- ERPs: in production with SAP Business One at Biodéal, and Dynamics 365 Supply Chain Management.
Configured on your rules, not ours
Mirage models your operation's own objects and rules: orders, shipments, assets, sites, suppliers, quantities. The agents follow the way your team already works rather than a generic template.
- What you give
- Your workflow, its rules and exceptions, your codes and document conventions, and the checks your team does by hand today.
- Autonomy
- Configurable for each workflow: what runs on its own and what waits for a person's approval.
- Approval
- Role-based access and human approval flows. A person on your side decides the exceptions.
- Audit
- Every agent action is traceable to the input and the rule that produced it.
Deployed where you decide
Mirage can run in your infrastructure, in your own cloud account, or hosted by Mirage. The architecture decides who holds the data, the keys and the access.
- Data
- In your infrastructure or your cloud, data and processing stay in the environment you control, and nothing is transferred outside it.
- Keys
- In those deployments, the encryption keys are your responsibility.
- Access
- Mirage's access is strictly limited, or removed after deployment, depending on the architecture you choose.
- Review
- A non-disclosure agreement on request, and answers to your security questionnaire for the architecture you are considering. No certification or audit report is listed.
Engineers who deploy it and stay with it
Forward-deployed engineers build each workflow inside your systems, with your team, then Mirage operates, monitors and improves it in production.
- First reply
- Within two business hours.
- Proof of concept
- On your own documents and data, one week after the first meeting.
- Pilot
- Engineers on site, one workflow, at a fixed price. You can stop after it.
- Production
- The first workflow in production in 4 to 6 weeks, operated, monitored and improved by Mirage.
- Next workflows
- Added on the same platform. Transwin started with one document workflow and now runs five systems in production.
Priced as a platform, not per seat
A fixed-price pilot, then an annual subscription priced by volume. Prices start at $10,000 to launch and $1,000 a month; the exact amount depends on the workflow and the volume and is quoted in the first conversation.
- Pilot
- Fixed price, on one workflow, with no commitment beyond it.
- Subscription
- Annual, priced by the volume of work the agents handle, not by the number of users. It only starts if you decide to continue after the pilot.
- What it covers
- The platform, the agents running on it, and Mirage's engineers operating, monitoring and improving them.
Questions from enterprise buyers
No. After a fixed-price pilot, the subscription is annual and priced by the volume of work, not by the number of users. Prices start at $10,000 to launch and $1,000 a month, and the exact amount is quoted in the first conversation.
No. Mirage connects to the systems already in place, more than 200 so far, and writes back into them. Where no documented interface exists, our engineers build the connector during deployment.
Yes. It models your operation's own objects and rules, and each workflow has configurable autonomy, role-based access and human approval. A person on your side decides the exceptions.
Mirage operates, monitors and improves them in production, with the engineers who built them. Your team reviews what is routed to it.
Yes. The pilot is a fixed-price engagement with no commitment beyond it, and the subscription only starts if you decide to continue.
Bring us an operational problem.
Mirage will map the workflow, identify what can be automated and define the fastest path to production.
Start with a written plan
Tell us where your team loses time. We send back which workflows are worth automating, what a deployment involves on your systems and the shortest path to production. No commitment.