Three deployment shapes
Same back-end code. Same domain rules. Same UI. Different runtimes. Pick the one that matches today; switch shapes without re-implementing anything.
Standalone
Flutter desktop on Windows, macOS, or Linux. SQLCipher encrypted database on disk. No server. No JVM. The Dart domain library runs stock allocation, money math, FX, calendar conversion, document numbering, and the audit chain in-process.
- Runs without internet
- Encrypted at rest by default
- Backups via the online server when reachable
Local LAN server
Spring Boot on a customer LAN host. PostgreSQL, Redis, MinIO behind nginx. Flutter desktop clients connect over HTTPS. Survives internet outages and supports as many concurrent stations as you have desks.
- One server, many stations
- Nightly Postgres + MinIO backups
- TLS via mkcert or your own CA
Online server
We run the Spring Boot stack for you in regional cloud (UAE, India, or Türkiye). Account management, license verification, encrypted backup, master-data updates, cross-device sync, and desktop auto-update.
- Hands-off operations
- Cross-device sync
- Disaster-recovery without a second server
What changes between shapes
The feature set is identical. What changes is the runtime — where the database lives, how stations connect, what we operate for you, and how recovery works.
| Feature | Standalone | LAN | Online |
|---|---|---|---|
| Stations | 1 | As many as your package allows | As many as your package allows |
| Database | SQLCipher — encrypted SQLite | PostgreSQL on your own server | PostgreSQL, we run it |
| Works without internet | Always — it never needs internet | Yes, inside your own network | Needs internet to sync |
| Sync between computers | — | Inside the network only | From anywhere |
| Backups | To a folder or USB you choose | Scheduled on your server | Encrypted, off-site, automatic |
| Files and images | On the same computer | MinIO on your server | S3-compatible, encrypted at rest |
| Updates | In the app, when you accept them | You schedule the server update | We update the server |
| What you need to buy | One Windows or macOS computer | One computer to act as the server | Nothing — a browser or the desktop app |
| Runs on your premises | ✓ | ✓ | — |
| How it is paid | Buy once, or subscribe | Buy once, or subscribe | Subscription — hosting is a service |
Move between shapes without re-implementing anything
Export
The export job produces a portable archive — schema, data, and audit log — encrypted with a customer-supplied key.
Import
The new shape imports the archive on first boot. Document numbers continue from where they left off; sequences are preserved.
Activate
A single license re-binding step ties the install to your account. Old activations are revoked. You keep your data.
Choosing and installing
Does the desktop app need an internet connection?
Standalone needs none at all. LAN clients only need to reach the server on your own network. Online needs internet to sync but keeps recent data cached locally, so a short outage does not stop the counter.
How long does installation take?
Standalone is an installer and a first-run wizard — under an hour including entering your company details and opening balances. LAN adds a server to prepare; budget a day with our team on the line.
What do I need to run the LAN server?
One machine that stays on, with Postgres, Redis, and object storage. We ship a Docker compose file that brings all three up, and we will size the machine with you based on station count and transaction volume.
Can I import my existing data?
Yes. Products, customers, suppliers, warehouses, price lists, and opening stock all import from CSV, validated row by row so you see what failed and why before anything is committed.
Do you support multiple branches?
On the online plan, yes — branches in different cities on one set of books, with document numbering that keeps each branch series separate. LAN is one site. Standalone is one PC.
Questions everyone asks
What does "customizable" actually mean?
Configuration, not custom code. An industry pack switches whole screens, fields, and rules on or off. Beyond that you control the sidebar per role, the roles themselves and what each may see, price lists, tax codes, currencies, document-number prefixes per branch, and which calendar dates are entered in. What we do not do is fork the product per customer — that is how ERP projects become impossible to maintain.
Is Telos right for a business our size?
It is built for small and medium businesses, and the plan follows the shape of yours: one counter on Standalone, up to ten stations on a LAN server, any number of branches online. A single-shop retailer and a three-warehouse wholesaler run the same core — what changes is the deployment and the pack, not the product.
What languages are supported?
English, Dari, and Pashto — every screen, every error message, and every printed document. Dari and Pashto lay out right to left, and the translations are written in Afghan administrative register, not borrowed from another country.
Does it use the Solar Hijri calendar?
Yes, as a first-class calendar rather than a display conversion. Dates are entered, filtered, and printed in Solar Hijri alongside Gregorian, and fiscal periods, payroll cut-offs, and public holidays all follow it.
Can I sell in more than one currency?
Yes. Every amount carries its own currency code, and a multi-currency transaction records the exchange rate at the moment it is created. That rate is never recomputed, so last month margin does not change when today rate moves.
Can I export my data?
Every report exports to CSV, and Standalone and LAN can take a full database dump you keep yourself. There is also a generic accounting export you can feed into your accountant tool — it is a CSV, not a Tally- or QuickBooks-shaped file.
Who owns the data?
You do, in every deployment shape. On Standalone and LAN it never leaves your building unless you send it. On the online plan we hold it for you and hand it back in full, in an open format, whenever you ask — including if you leave.
Is my data encrypted?
On Standalone the whole local database is encrypted on disk with SQLCipher. On LAN and online, traffic is TLS and stored files are encrypted at rest with AES-256. Backups are encrypted before they leave the machine.