What each of your people gets
Everyone works with the same customers, the same money and the same history — and everyone sees only what they should.
The whole business, under your control
Sales, money, partners and stock in one system, with the same figures for everyone — and rules that you set.
You can:- see the whole business in one place instead of a dozen spreadsheets
- decide where your data lives: your servers, your country or our cloud
- require a second person for the most critical actions
- ask what the business looked like on any past date and get the answer as it was then
- change a bonus, a discount or an approval limit — checked before it goes live
- know that nobody can quietly rewrite history
The auditor asks about March
You replay March and show the same figures, step by step — and what the system knew on 31 March, not what is known today.
Grow through people who recommend you
Distributors, partners, referrals and loyalty points — with volumes, ranks and payouts calculated by your plan, not by a spreadsheet.
You can:- run a partner network with deep levels, volumes and ranks calculated automatically
- pay commissions exactly: the parts always add up to the pool, to the cent
- pay in several currencies and point types, each kept separately
- let every partner see their own branch — and only their own
- never pay the same bonus twice, even if a request repeats
- answer «why did I get this amount?» with the calculation behind it
A partner asks why the bonus is smaller
They open their own calculation and see every level, every volume and the rule that produced the amount — the same figures your team sees.
Books that always balance
Every operation is double-entry, every amount is exact, and every figure can be traced to the operation that produced it.
You can:- keep books that balance after every operation
- work with exact amounts — no rounding drift in totals
- close the month knowing no payment went out twice
- correct a mistake with a new entry while the original stays visible
- hold money in reserve and settle it in two steps
- require a second factor or a signature to approve a payout
A customer questions an invoice
You recalculate it with the data of that day and get exactly the same result — then show where each amount came from.
Every order, every step, in order
Orders, stock and shipments follow your process, and the system refuses a step that is not allowed.
You can:- count stock as carefully as money: every movement is an entry
- run orders through clear statuses — placed, paid, shipped, refunded
- give each step its own permission: only the warehouse ships, only finance refunds
- process a repeated request once — a double click never makes a double order
- keep confirmed data through a power cut
- describe your own exceptions — returns, limits, approvals — as rules
A shipment without payment
Someone tries to ship an order that is not paid. The system refuses, names the reason, and the order stays exactly as it was.
Everyone sees and does only what they should
Rights by role, region and field — with deputies, time limits and a full record of who did what.
You can:- hide salaries and bank details from everyone who does not need them
- let a regional manager see only their region
- hand your rights to a deputy — except those you mark as personal
- grant access for a set period that ends by itself
- remove all access of a leaver at once, including what was delegated
- see every refused attempt in the audit log
A manager goes on leave
Her deputy gets her rights for two weeks — except approving payouts, which she marked as non-transferable. On day fifteen the rights end by themselves.
Your servers, safe updates, nothing foreign inside
One platform to run instead of many — in our cloud or on your own network of nodes.
You can:- run it on your own servers, ARM64 or x86-64, or in our cloud
- update without fear: every update is signed and rolls back by itself if it fails
- manage nodes over an encrypted channel with mutual keys — with no remote shell to attack
- keep disks encrypted, with the key never stored on the server
- connect existing tools over standard protocols, including PostgreSQL, Redis and Kafka
- rely on an operating system with no third-party code, about 5 MB per node
An update goes wrong at night
The new version boots on probation. It is not confirmed, so the server returns to the previous version by itself — nobody has to drive to the data centre.
Start with one team, add the next when you are ready
Every role works with the same customers, money and history, so adding the next team never means moving data between systems.
See it on your own business
Book a demo: we show the platform on your processes and agree where your data will live — in our cloud or on your own nodes.