Yours to keep
Your shop, your machine, your data
Backups that have actually been restored, a key you hold, and a straight answer about what is protected.
Backups
- On a schedule, to more than one place
- A backup that only ever went to the same disk covers one kind of failure, and not the common one.
- Restored, to prove they restore
- A backup nobody has ever restored is a rumor, and you find out which on the worst morning.
- Encrypted with your key
- We can hold a copy at your asking, and only at your asking.
- Restore from inside the program
- It rehearses the file first and takes a safety backup before it replaces anything.
What is protected, and what is readable
Passwords are hashed and cannot be read back by anyone, us included. The secrets the server has to present, like a mail password, are encrypted with a key kept outside the database.
Everything else is stored plainly: customers, tickets, parts, engine history. That is the trade for owning it. You can read and export it with any tool, and nobody can lock you out of your own records. It also means a plain copy of the database is as readable as your filing cabinet, so keep it where you would keep that.
Day to day
- Nothing is sent to the wrong server
- Workstations and the phone check the server's certificate before they send anything.
- Guessing a password gets slow
- Sign-in attempts are limited by account and by machine.
- Permissions you can edit
- The floor can ask for parts without being able to spend money.
- A log of what changed
- Read-only, written as sentences, covering the things people argue about later.