BMS Enterprise · in development
One business. Every branch in step.
For teams that have outgrown a single counter. A central source of truth, clear roles and a back-office view — without taking away the fast, offline app the counter already depends on.
No commitment Mobile stays independent No payment today
How Enterprise fits
Design previewClients
BMS API
.NET · JWT authentication
PostgreSQL
Tenant-scoped records
Illustrative architecture. Subject to change.
Why Enterprise exists
A local app is perfect — until the business needs a shared view.
One phone can run one counter beautifully. It cannot show the owner what the depot, the second branch and the field agent did today. Enterprise is the separate edition for that problem.
An honest separation
BMS Mobile and BMS Desktop are not being held back for Enterprise. They remain complete offline apps. Enterprise is a different deployment for a different kind of business — not a paywall in front of the app you already use.
A central source of truth
A .NET API with PostgreSQL for teams that need shared records across counters, branches and the back office.
Roles and permissions
JWT authentication, role-based access control and per-tenant isolation so each branch sees only its own data.
Branches without the mess
Tenant-aware data model designed for resellers, distributors and multi-branch operations.
Audit logging
A record of important actions for owners and administrators who need accountability.
Back-office client
A Flutter admin app for user management, master data, sales oversight and field-agent activity.
API access
A documented API surface for integrations and reporting beyond the built-in clients.
Where it fits
Built for businesses with more than one moving part.
If one person can see the whole business from one device, the free app is the right tool. Enterprise starts when that stops being true.
Multi-branch retail
A main shop, a depot and a second counter that need the same items, prices and credit rules.
Distributors & field sales
Order bookers and recovery agents in the field, with a back office that can see the day as it happens.
Growing teams
More than one person needs to sell, receive stock or collect credit — and the owner needs accountability.
Where it is today
In development, not on a launch countdown.
The server foundation and access model are being built now. There is no release date to announce and no pretending otherwise.
Foundation
Central API and database
A .NET API with PostgreSQL, JWT authentication and tenant-aware records. The server foundation exists and is being hardened.
Access
Roles and branch isolation
Role-based access and per-tenant data separation, so each branch sees only what it should.
Back office
Admin client
A Flutter back-office app for users, master data, sales oversight and field-agent activity.
Pilot
Partner onboarding
Real deployments with a small number of businesses, with migration and support handled carefully.
Enterprise is not required for BMS Mobile or BMS Desktop. If you are running one counter and one device, the free app already covers the workflow end to end.
Enterprise questions
What we can say, and what we can’t.
Clear answers about scope, data and timing — without a sales deck.
Do I need Enterprise to use BMS?
Will Enterprise replace the mobile app?
Can I move my existing BMS data into Enterprise?
How is Enterprise priced?
Where does the data live?
Pilot conversations
Help shape the shared edition.
We are speaking with distributors, multi-branch shops and teams that feel the gap between the counter and the back office. If that sounds familiar, describe your setup and we will take it from there.
Conversations are handled through the project’s GitHub issue tracker at the moment. No forms, no CRM, no follow-up sequence.
Useful to include
Your setup
Number of counters, branches and people who need access.
The workflow
What you sell, how stock is received and how credit is tracked.
The gap
What breaks today between the counter and the back office.
No payment details, no commitment, no obligation to adopt.