ServiceStack

We build software for businesses, then we keep it running.

Five products, one small team, and a network we operate ourselves out of Brisbane. The map below is the real one. Hover a product to see where it runs.

How our products run Five product lines run from their public addresses through the Cloudflare edge and our Brisbane rack to the services they depend on. A dashed line carries the nightly backup to a standby server in Azure. office.servicestack.com.au API, two copies getkioski.com Tablets and queues getinboxr.app SES and the SMS phone notes.servicestack.com.au Postgres and search datachef.servicestack.com.au Connectors Cloudflare edge Brisbane rack Standby in Azure every night

The lines on the map

How a change reaches you

  1. It builds on our own machines

    Every commit is built and tested on agents we run, not on someone else's shared queue.

  2. A copy installs from nothing

    Before anything ships, a throwaway copy sets itself up from an empty database, signs in and loads the pages you use. If that fails, the release stops.

  3. Half updates while half serves

    Each app runs as two copies behind a load balancer. One is replaced while the other keeps answering, then they swap.

  4. It is backed up overnight

    Encrypted copies of everything go off-site every night, and we restore them onto a standby server on purpose to prove they work.

Work we can point to

776 checks, 0 failures

Releases nobody notices

We ship Consolidated as two copies of every app. Across three live releases we fired checks four times a second, with the server deliberately loaded, and not one request failed.

11 minutes

Two servers died. The services didn't.

When two of our three old servers failed, we moved 26 services onto a new host behind Cloudflare, pulled 5.3 million monitoring records back off the dead disks, and set up nightly off-site backups. A full restore onto the Azure standby took 11 minutes in the last drill.

9 services on Azure

Adeva Pro

Debt resolution for Australians: debtor, client and admin portals plus a public API, which we build and operate on Azure Container Apps with monitoring and alerts.

In pilot

Cut N Fade

A barbershop running its walk-in queue on Kioski. Customers check in on a tablet at the door and barbers take them in order under their own names.

Tell us what you run

A system that keeps falling over, a spreadsheet that became a business, a product you want built and looked after. Write to us and a person replies.

Brisbane, Queensland