A deployment, not a login.

Your infrastructure or ours

The default is your own server: complete data sovereignty, with the platform delivered as one versioned, integrity-pinned release artifact and operated through documented runbooks. Prefer not to run infrastructure? We operate the instance for you with the same discipline.

Onboarding that does the heavy lifting

Enterprise onboarding is white-glove and template-driven: opening stock with lot numbers and expiry dates, suppliers, raw materials and recipes imported in a defined order, so first-expired-first-out picking and expiry alerts work from the first week. Your storefront can cut over from an existing platform without pausing sales.

Security posture, in writing

• Dedicated instance; tenant isolation enforced at the database layer even in single-tenant mode.
• Mandatory multi-factor authentication from first login, with forced credential rotation on handover.
• Append-only, cryptographically chained audit trail across the platform.
• Electronic signatures implementing 21 CFR Part 11 controls for records that require them.
• Documented zero-downtime update, rollback, support-access and data-return runbooks.
• Encrypted secrets per deployment; no shared credentials between customers.

How an engagement runs

1. Demo. Bring your actual SKUs; see production, trace-back and margin on data shaped like yours.
2. Scoping. Your categories, channels, compliance schemes and integrations, written into a deployment plan.
3. Deployment & onboarding. Instance up, data imported, team trained, done with you rather than thrown over a wall.
4. Operation. Annual licensing sized to your operation, with support that answers and an update channel you control.

Pricing is annual and sized to the operation: users, SKUs, lots and schemes, agreed in scoping before you commit. No metered surprises.