Every vendor has a bad day. What matters is whether your staff, your stock and your sales depend on it. With Vritti, they run on a system of your own.
Every software vendor has a bad afternoon. A data centre loses power, a release goes wrong, a network route disappears for an hour. The question is not whether it happens to the company that runs your business software, but what it takes down with it.
With most cloud software the answer is everything. Your staff sign in through the vendor, your plan is checked on the vendor's servers, and your stock lives in the vendor's database. When they are down, so are you.
Vritti draws the line in a different place. Vritti Cloud is where you sign up and where your system is managed. Your system itself — VAP, its database and its sign-in — runs as a separate deployment of its own.
Signing in does not phone home
When a cashier or a store manager signs in to VAP, the check happens on your own system. Their password is verified against your own database, and the session is issued there. Nothing is sent to Vritti Cloud to ask whether they may come in.
That matters at opening time. Someone arriving for the morning shift needs to get to work, not to read a vendor's status page. Whether Cloud is reachable at that moment does not decide whether they can.
Your plan travels with your system
Software you pay for has to know what you have paid for. The usual way is to ask the vendor, on every request or every few minutes. If the vendor does not answer, the software has to guess — and it usually guesses by locking you out.
VAP does not ask. When your plan or your features change, Vritti Cloud sends your system a licence signed with an Ed25519 key. Your system checks the signature, checks that the licence was issued for this deployment and no other, and stores it in its own database. From then on it reads the licence from there, re-checking the signature against a public key it already holds.
The signature cuts both ways. A licence that has been edited — by anyone, including someone with access to the database — fails the check and counts as no licence at all. The only thing that changes your plan is a new licence, signed by Vritti Cloud, for your deployment.
What Cloud is for
Some things do need Vritti Cloud, and it is better to say which. Signing up and creating your organisation happen there. So do changing your plan, receiving new features, and operating your deployment from the console — starting and stopping it, reading its logs, running a backup or a restore.
Those are management tasks. If Cloud is unreachable, they wait until it is back. Signing in, receiving stock and taking orders carry on, because they never went through it.
It is the same idea as a database per business, taken one step further: the data is yours, and so is the system that runs on it. Vritti Cloud manages that system. It does not stand between your staff and their work.