What happens when the link to TinyCIO or the network goes down?
A portal that keeps running without TinyCIO, queued events, a ferry expense sent once ashore, a single record despite a lost reply, and a statement reloaded without duplicates.
What you get
- Your company’s data is kept apart from everyone else’s and stays yours.
- Nothing is corrected silently: every change has an author.
- No money, no documents, no emails go out without your action.
Transcript
Subscription invoices are kept by the central TinyCIO system, not by the product itself. If the link to it drops, your portal keeps running: it checks module access on its own and keeps prices locally.
Events for TinyCIO pile up in a queue and go out when the link comes back. Operations never stop for a commercial reason.
The driver’s phone works without a network too. An expense entered on the ferry waits to be sent, and goes by itself once ashore. Or don’t wait: there’s a “Send now” button.
If the server’s answer gets lost and the phone sends the same action again, the office still gets a single record.
And a bank statement uploaded a second time doesn’t create duplicate operations: rows already known are marked as duplicates.
Isolation, roles, immutability, privacy, money under your control, and resilience. These aren’t options: they’re part of the service.