Technology
Built the way a finance team would want it built.
These are the commitments behind both products. We describe what we do, not every detail of how; if you need more for a security review, ask us and we will walk you through it under NDA.
- Isolated tenants
- Each client's financial data lives in its own database. Shared services never return another tenant's rows, and this is enforced at the database layer, not only in the application.
- Role-based access
- Who may open which screen, which companies and which actions is decided on the server. Hiding a menu is not a permission; the server checks every call.
- Everything is logged
- Sign-ins, changes, imports and every export are recorded with who, when and from which screen. Posted ledger entries are never edited, only reversed.
- Your ERP stays in charge
- GARWIS DI reads from your ERP on a schedule and never writes back. It is a reporting and decision layer, not a second system of record.
- AI assists, people decide
- AI features propose, summarise and draft. They never post, never change a figure and never see another tenant's data. Your data is not used to train models.
- Hosted in the EU
- Production runs on EU infrastructure over encrypted connections, with daily backups kept for 45 days. Dedicated hosting is available on request.
How we work
Small releases, verified before they ship.
Automated checks
Every screen is opened and every record type is created, read, updated and deleted by a test run before a release; accounting invariants are tested on every posting path.
Visible change log
Every change is written up in plain language inside the product: what it was, why it mattered, what you will see. Help pages are updated in the same release.
Five languages, one source
The interface, help and this website are maintained in English, Turkish, Dutch, French and German from one source, so no language falls behind.
We deliberately do not publish data models, integration internals or algorithm details here. This protects our clients as much as our work.