ERP.AI
Choose the operating boundary your business needs.
Evaluate infrastructure, identity, ownership, and support together so the deployment fits the way your organization operates.
Three deployment conversations.
| Model | Boundary | What to establish |
|---|---|---|
| Shared SaaS | Multi-tenant platform operated by ERP.AI. | Organization identity, app permissions, data handling, usage, and operational contacts. |
| Isolated runtime | Dedicated network and compute when contracted. | Network design, access, responsibilities, service scope, and operating procedures. |
| Dedicated instance | Single-tenant application and data when contracted. | Region, keys, access, release control, support, and ownership of operations. |
Start with the requirement that changes the decision.
Some teams need a standard managed platform with clear access controls. Others have a specific network boundary, region requirement, or operational responsibility that shapes the deployment. State the requirement and the evidence needed to accept it before selecting a model.
Dedicated infrastructure and customer-defined controls are contract-specific. Confirm certification scope, availability commitments, recovery objectives, response targets, and export requirements in the applicable order form and service documentation.
Agree who operates each part.
Identity and policy
Name who provisions users, reviews service identities, and maintains role assignments.
Change and release
Define how changes are reviewed, who authorizes releases, and which recovery path applies.
Monitoring and incidents
Agree the signals, escalation contacts, severity definitions, and response responsibilities.
Data and recovery
Record backup and restore responsibilities, required recovery tests, retention, and the agreed export scope.
Bring a concise deployment brief.
Include the applications in scope, expected users and machine activity, data classes, identity provider requirements, network constraints, and the team that will operate the service. This gives enterprise sales and technical reviewers a concrete basis for the next conversation.
Put ERP.AI to work for your business.
Choose an application, then configure the records, roles and workflows your team needs.