Data ownership
The database lives on your computer. You own the data, the hardware it runs on and the backups made from it. There is no EBS cloud holding your records.
Security & trust
Your data stays on your premises.
EBS runs on your own computer, on your own network. No cloud account holds your sales, stock or customer records. This page explains the architecture, the controls and the limits, in plain language.
On-premise · Offline-first · No cloud dependency
- Data stays on your premises
- Role-based access and audit trail
- Daily automated backups
- Health checks every 5 minutes
- No vendor lock-in
Commitments
Six commitments you can hold us to
Security claims are easy to write. These are the controls and operating habits behind the system, stated without a certification badge we do not hold.
Least-privilege roles
Roles are set per module and action. Staff see the areas their role allows, and branch permission gates apply where the business runs more than one branch.
Audit trail
An audit log records changes, so you can review who changed stock, prices or permissions, and when. Login sessions are part of the record.
Daily backups
An automated backup runs every day. Retention is 30 days on Basic, 90 days on Standard and 1 year on Premium.
Monitoring
A watchdog checks the server every five minutes and restarts it if it stops responding. Events are recorded.
No lock-in
Excel and CSV export are built in, and the database is yours. If you ever leave, you take the data with you.
Architecture
A shop server, not a cloud account.
EBS is deployed remotely onto a computer you control. The application, database and backups sit on your premises; devices connect over your local network. The system keeps working when the internet does not.
- The server runs on a computer in your shop or office
- Phones, tablets and laptops connect over the shop LAN
- The web app is offline-first, with a local database on the device
- Changes sync with the server when a connection returns
On your premises
Your computer runs the server
The application and database run on a computer in your shop or office. Automated backups are part of the same system.
Local network
Phones, tablets and laptops on the LAN
Staff use the system over your own Wi-Fi or cabling. The server stays inside the building.
- Counter device for sales and receipts
- Laptop for purchases, stock and reports
- No cloud account required to operate
Offline-first Sync when online
Trading does not stop with the internet
Devices keep a local database and queue changes while offline. When a connection returns, the app syncs with the server and the other devices.
Illustrative architecture — server and devices on one local network.
Access control & audit
Who can do what, and who changed it
Access is granted by role, not shared as one administrator login. The audit log gives you a reviewable record of changes across stock, prices and permissions. Remote support runs on request over a supervised session — no standing access and no unattended connections.
Least-privilege roles
Permissions are defined across a role × module × action matrix, so a counter role and an owner role do not carry the same reach.
- Staff see only the modules their role allows
- Per-branch permission gates for multi-branch teams
- Login sessions are recorded
- Credentials are handled with encryption, not plain text
An audit trail you can review
The audit log supports stock, price and permission reviews. It answers the questions that matter in a dispute: who changed this, and when.
- Records changes with the user and time
- Covers stock, price and permission changes
- Login sessions form part of the record
- Available in the system you already run
Why roles matter: the biggest data risk in a shop is usually a shared login. Role-based access means a mistake or a departure can be traced and contained without changing everyone else's credentials.
Backup & continuity
Backups are tested, not assumed
A backup is only useful if it restores. Daily backups run automatically, and restore drills are part of the operating routine.
Daily automated backups
A backup runs automatically every day. Retention is 30 days on Basic, 90 days on Standard and 1 year on Premium.
Weekly verification and drills
Backups are verified weekly, and restore drills are run so recovery is exercised rather than assumed.
A clear recovery point
If hardware fails, the latest verified backup is the recovery point. We help with the restore; the hardware itself is part of your environment.
Honest boundary: on-premise means your computer is the server. Power, physical access and hardware replacement belong to your environment. The software, the backup routine and restore help belong to us.
Monitoring
Designed for 24/7 operation
Monitoring and auto-restart reduce the time a stopped server stays stopped. They are not an uptime guarantee, and we do not publish an uptime percentage.
Health checks every 5 minutes
A watchdog checks the server and application on a five-minute cycle, all day.
Watchdog auto-restart
If the process stops responding, the watchdog restarts it and records the event for review.
Built for continuous use
The system is designed to run through the working day and beyond. Availability also depends on power, hardware and your network.
Support & SLA
24/7 support with clear terms
Support is available 24/7 on every tier. Response times and any support work beyond the 24/7 channel are agreed in writing; support is a separate service quoted with you. The same terms appear on the pricing page.
| Tier | Support | Response target |
|---|---|---|
| Basic | 24/7 | Agreed in writing |
| Standard | 24/7 | Agreed in writing |
| Premium | 24/7 | Agreed in writing |
Support work beyond the 24/7 channel is a separate service, quoted by agreement. Response times describe a first response, not resolution time. On a narrow screen, scroll the table sideways.
What support covers: questions, configuration, troubleshooting and guidance on using the system. Custom development and hardware repair are quoted separately.
Severity
How first responses are prioritised
We triage by impact. Response times are agreed in writing; the severity decides what is handled first.
| Severity | What it means | Response target |
|---|---|---|
| Critical | Sales, stock or data are unavailable | Within the agreed response time, handled first |
| High | A core workflow is blocked, such as purchasing, reports or sync | Within your tier target, after critical issues |
| Normal | A question, configuration request or training need | Within your tier target, scheduled around critical work |
Response times are agreed in the Service Agreement. They are not an uptime guarantee, and they do not describe resolution time. On a narrow screen, scroll the table sideways.
Compliance
Not certified — and we say so
Some vendors use a certification logo to end the conversation. We would rather answer the questions properly.
We are not certified to ISO 27001 or SOC 2.
We do not hold ISO 27001 or SOC 2 certification, and we will not claim one. What we can do is document our controls, answer your security questionnaire and walk your IT team through the architecture, data flow and backup routine.
If a certification is a hard requirement for your organisation, we will tell you before a proposal rather than after.
Documented controls
The access, audit, backup and monitoring controls described on this page are documented and can be reviewed with your team.
Security questionnaires
Send your questionnaire. We will answer it in writing, including the parts where we do not meet a requirement.
Architecture walkthrough
We can walk your IT team through the on-premise setup, the local network, the sync path and the restore process.
The website itself sets no cookies, runs no analytics and makes no third-party requests. Read the privacy policy.
Review the architecture with your IT team.
We will walk through how the server, devices, audit trail and backups fit together, then answer the security questionnaire your organisation uses.