IMS Architecture
System-level view of the IMS Windows client, IMS.Api, IMS Global, separate company databases and server-side integration workers.
Core components
| Component | Role |
|---|---|
| IMS client | Windows operational application used for POS, inventory, purchasing, finance, reporting and administration inside the selected company. |
| IMS.Api | Central service boundary for secure bootstrap, authentication, workstation checks, company routing information, Global administration and protected secrets. |
| IMS Global | Dedicated administration application for company records/database profiles, Global users/company access, workstations, version control and controlled cross-company setup tools. |
| ims_global | Global identity, company/access, workstation, version, API administration and protected-secret data. |
| Company databases | Independent PostgreSQL databases containing each company's operational configuration, stores, inventory, transactions, finance and history. |
| Background/integration services | Server-side automation and e-commerce/integration workloads such as IMS Autos and the Shopify integration service. |
Session flow
- The workstation is validated.
- The user authenticates against the global IMS identity.
- IMS resolves active company access.
- The default/selected company determines the company database runtime profile.
- The client opens the company operational context and then applies company-local permissions.
Separation by designGlobal identity and company membership are centralized, while operational data and local authorization remain company-specific.