Your clinical data and your cash, handled seriously
A clinic trusts its medical records, inventory and invoicing to a system it doesn't control. These are the technical decisions behind that trust, explained without smoke.
Isolation between clinics
Each clinic is a tenant with its own identifier, and the per-clinic filter is applied in the query engine, not in each screen. If the system can't determine which clinic a query belongs to, it doesn't run it: it fails closed instead of returning too much data.
- The per-clinic filter is injected inside database transactions as well
- Writes by identifier are validated against the owning clinic before linking
- Automated tests verify isolation on every code change
Permissions and access
163 permissions govern screens and actions. Roles are built per position and can be scoped per branch. Nobody can widen their own permissions, and the owner role — the one with full access — is only granted with email authorization from an existing owner.
- Clinical files (X-rays, lab work) require a specific permission
- Password-reset links are single-use and die when the password changes
- Sessions can't be tampered with from the browser to escalate privileges
Encryption and credentials
Traffic runs over HTTPS and integration credentials (payment gateway, messaging, delivery) are stored encrypted at rest, not in plain text. User passwords are stored hashed, never in a recoverable form.
- SSL certificate included on your subdomain and your own domain
- Per-clinic secrets are never exposed in public responses
- Charges validate the amount on the server, not the one the browser sends
Backups and traceability
The database has automatic backups, and every create, edit and delete is logged with user, date and branch. Inventory movements have their own log, which is where stock discrepancies get resolved.
- Action log queryable from the panel itself
- Inventory movement log per product and branch
- A system-status screen with the health of each integration
The data belongs to your clinic
No hostages: 28 system entities export to Excel whenever you want, including a combined workbook with the medical history. If you ever decide to leave, you leave with your data.
- Export catalog, clients, patients and history to Excel
- Download the XMLs of your electronic receipts
- No lock-in contract and no cancellation penalty
How we work on the code
Security in a multi-clinic system breaks with small changes, so the project has tests that watch the rules themselves: if a change leaves a query without a clinic filter or a medical file without a permission, the test goes red before it reaches production.
- Thousands of automated tests before every deployment
- Tests that watch the isolation and permission rules themselves
- Periodic audits of our own code and integrations
- Per-clinic error logs to diagnose without guessing
Have a specific security question?
If you need technical detail for a purchase decision — isolation, backups, data handling — write to us and we'll answer precisely.
What people usually ask before deciding
If you have a question that isn't here, message us on WhatsApp and we'll answer straight.
Try it with your clinic's data
Create your account, load the starter catalogs with one click and import your catalog from Excel. If it doesn't work for you in 14 days, you pay nothing.
- 14-day trial
- No credit card
- Assisted migration
- Cancel anytime