Back to Blog

Governance and responsibility

We do not build what we cannot maintain

By AIPathTech Editorial · 26 October 2026 · 5 min read

The governance cost of the simple version was zero, because there was nothing to govern.

We wanted one number: how many people opened a page. The server already knew it. Reading it back turned out to be a paid plan, and the price was not the reason we wrote our own.

Fifteen dollars was never the problem

Access logs for our own content delivery network sit behind a plan at fifteen dollars a month. That is nothing. It is less than the coffee consumed while discussing it.

Price is the easy thing to compare, which is why it is usually the only thing compared. The question worth asking is different: what does turning this on oblige us to own, for as long as the company exists?

In this case, the list behind the button is longer than the button.

So the comparison was never fifteen dollars against nothing. It was one route and one table against a configuration surface, a storage policy, a retention decision, and a category of data we had deliberately chosen not to hold.

  • A storage bucket to create, in the right region, with the right access settings.
  • A field selection to decide, because the log can carry more about a visitor than we want to hold.
  • An access policy for whatever is eventually going to read it.
  • A retention rule, and therefore a decision about how long is defensible.
  • <b>Viewer IP addresses sitting in our own storage.</b> That is personal data, and it arrives with everything personal data brings: a lawful basis, a retention period, a line in the record of processing, and an obligation if it is ever exposed.
  • And at the end of all that, the code that reads the logs and turns them into a number, because nobody hands you the number.

What we built instead

A counter. About a hundred lines, added to a function that already existed.

A page opens, and two numbers go up: that page today, and the label on the link the reader arrived through. That is the whole mechanism.

The governance cost of the simple version was zero, because there was nothing to govern. A system that collects nothing has nothing to disclose, nothing to delete, and nothing to explain to anybody.

  • No third party, so nothing to agree with anybody and nobody else holding our readers' data.
  • No cookie, no identifier, no session, no device, no address. It cannot tell us the same person came back, and it is not supposed to be able to.
  • Where somebody came from is never read from the browser. We count a label <em>we</em> put in our <em>own</em> links, which says which of our posters a reader walked through and nothing whatsoever about the reader.

And the data is real

The lazy reading of a post like this is that somebody found a way around paying and got a cheaper version of the same thing. That is not what happened and the distinction matters.

We did not reproduce the paid product and we are not pretending to. Server logs would show every single request, including the ones no browser ever reports. We gave that up, knowingly.

What we kept is the part that was already ours: a real event, counted once, at the moment it happened, by code we wrote and can read. Nothing is estimated, nothing is modelled, nothing is filled in. A number that was not measured does not appear anywhere, which is why our own report says logging is off rather than printing a plausible figure in its place.

A measurement is something you could check

Here is the test we would put to any analytics product, and to ourselves.

Our counter and the network's own logs are two separate records of the same event, kept by two different systems, for two different reasons. Either can be checked against the other. We have not needed to, and that is exactly why it matters that we could.

Most dashboards cannot be audited at all. You are shown a figure and invited to trust it. So the question for a vendor is not how accurate the number is. It is: what is the second record, and who holds it.

A number you could verify against an independent record is a measurement. A number you simply have to believe is a claim.

The objection, which is the real one

Fine for you, somebody is thinking. You built it. What happens when the person who built it is not there.

That is the honest argument against building rather than buying, and it has nothing to do with code. It is about handover.

Every repository here opens with a document that says what this is and what to read before changing anything. The rules sit beside the code rather than in somebody's head: what may be deleted and what may only be moved aside for a person to remove afterwards, how far an assistant's reach extends into the files, how the site is published, and what is never to be touched. Someone arriving cold can work inside those rules without anybody explaining them.

Building it yourself only produces a system nobody else can run if you do not write it down. Written down, it is the most transferable thing you own, because there is no vendor standing between a new person and the thing itself.

What this is actually a rule about

Not analytics. Analytics was just the week it came up.

Every tool offered to a small company is offered on its price, and the price is almost never what it costs. The cost is the configuration you now own forever, the data categories you have quietly become responsible for, and the question you will have to answer one day about where that data is and who can reach it.

No infrastructure is described here beyond the shape of the idea: no account identifiers, no resource names, no addresses. The plan price is public.

The cost of a solution is not its price. It is the configuration it obliges you to own forever, and the categories of data it quietly makes you responsible for. Build what you can maintain, write down how it works, and collect nothing you cannot justify holding.

MK!

AIPathTech Editorial

There is no tracking on this site. No analytics, no cookies, nothing recording where you went or how long you stayed.

But I would like to know if something here was worth your time. If it was, press the heart. It tells me nothing about you. It is a number going up, and it is what tells me to keep writing.

Share this article

XLinkedIn

If you want more of this, I am on X. @Queendemetriak