Why we run our own products on the same stack we sell

NordGryd, Direkta, PageBaze and Solene are ours. We built them, we run them, and they are built the way we build for clients.

That is a deliberate arrangement rather than a coincidence, and it changes the incentives in a way that is worth explaining.

We find the problems first

When a deployment process is fragile, we are the ones woken up by it. When a monitoring gap means an outage is noticed by a user rather than by us, it is our user. Running our own systems on the same foundations means the rough edges reach us before they reach you.

An agency that only ever hands work over never gets that feedback. Everything they learn about how their own build behaves at two in the morning comes second hand, through a client who is already unhappy.

It keeps the advice honest

It is easy to recommend an architecture you will never have to operate. It is much harder to recommend one you will be maintaining yourself in three years.

When we tell you a simpler approach is the right one, it is usually because we have carried the cost of the complicated one somewhere in our own estate.

What it means for your project

The practices are not written for a proposal. Prepared statements, least privilege database users, encrypted personal data, audited changes, tested restores: these are how our own products are built, so applying them to your work costs us nothing extra and is not a line item you can accidentally cut.

It also means the answer to "have you built something like this" is usually yes, and we can show you the running system rather than a slide about it.