How we run what we build

Building a system is half the job. This is how we keep it running — only what we do today, and all of it we can show you.

Backups, restored to prove they work

• Every night, each system’s data and configuration are backed up and encrypted with AES-256.
• Fourteen days of encrypted backups are kept.
• Every week, the latest backup is restored into a separate, sealed database and checked table by table against the live system. The result is logged.

Health checks and automatic recovery

• If a service stops, it restarts on its own — no one has to be awake for that.
• Databases and most core services check their own health every 10 to 30 seconds, around the clock.
• Certificates renew automatically before they expire.

Security, every day

• HTTPS everywhere, and outdated encryption refused.
• Server access by key only — no passwords to guess.
• Repeated failed sign-ins are blocked automatically, and we get an email the moment a server is reached from an address we have not seen before.
• Security updates install automatically.

When something goes wrong

Our engagement lead spent more than seven years in the national operations centre of nbn™, Australia’s national broadband network, running 24/7 incident and change management for nine million customers. We work the same way:

• Every issue gets a reference, a severity and a time.
• You are told what is affected and when the next update will come.
• Afterwards, a short written note: the cause, the fix, and what we changed so it does not happen again.

Support hours

Support hours and response times are agreed with each client and written into the service terms before go-live. Cover outside those hours for urgent issues is available as an add-on.

We do not hold formal certifications such as ISO 27001, and we will not pretend to. If you want an independent security test of your system, we will work with the tester of your choice.