ERP.AI
A shared core with clear service boundaries.
Use several interfaces without giving each one a separate copy of your business logic.
ERP.AI applicationsAgents and software
Authenticated APIs
Records · relationships · views · business rules
A conceptual service map. Permissions and configuration determine the operations available in each workspace.
Follow a request through the platform.
A request enters through the gateway with the caller and organization context. The gateway routes it to the service that owns the operation. That service checks access and applies the relevant validation and business rules.
This separation matters when a person and an integration work with the same app. The interface can change while the authoritative records and access decisions remain with the platform services.
Know which service owns which responsibility.
| Service | Responsibility |
|---|---|
| Gateway | Authentication, organization context, routing, and configured limits. |
| App Builder | Apps, schemas, records, views, forms, workflows, reports, documents, pages, hosting metadata, and audit events. |
| Identity | Organizations, users, service accounts, keys, OIDC, SCIM, and hosted-app identity. |
| Permission API | Roles, permissions, assignments, and invitations. |
| Agent API | Conversations, knowledge, app plans, search, reports, documents, pages, and action approvals. |
| Renderer | Multi-tenant hosted pages and portals. |
Keep authority separate from presentation.
PostgreSQL is the durable source of truth for ERP.AI business records. A report, a generated document, an agent response, or an exported file is a view or output of the work; it does not automatically replace the underlying record.
Related tools may provide context retrieval, model routing, or agent development capabilities. Their role should be evaluated separately from the ownership of transactional business data.
Design each connection around an explicit contract.
Identify the owning app, supported operations, caller identity, required permissions, and expected result. Then define how errors, retries, external side effects, and reconciliation will be handled by the client and the connected service.
A successful request proves that operation completed under the current configuration. It does not establish that every downstream business step is finished. Build handoff and exception states into the process itself.
Put ERP.AI to work for your business.
Choose an application, then configure the records, roles and workflows your team needs.