Thirty years, one problem: who can read this?

By Rob Linton ·2026-08-11

The verdict first: every system I have shipped since the 1990s answers one question. Who is allowed to read this?

Everything else (the middleware, the cloud books, the encrypted file company, the governed AI platform, even the patent filings) is that question wearing a different costume.

Where does the story start?

In the machine rooms of the nineties: databases, networks, and other people’s emergencies.

I mean that literally. By the 2000s I was co-founder and CTO of LogicalTech SysTalk in Melbourne, building integration middleware, the plumbing that lets systems talk when they were never designed to. Among our customers were Victoria’s Triple Zero (000) emergency service and the Melbourne Metropolitan Fire Brigade.

When the systems you are connecting help dispatch fire trucks, “who is allowed to read this, and can they trust it” stops being an architecture diagram and becomes an operational question with a clock on it. The work won the Australian iAwards in 2010 and an Asia-Pacific APICTA award, but that is the part that stayed with me.

Moving data was never the hard part. The hard part was controlling who could read it once it arrived. Access, not transport.

Why bet early on the cloud?

Because I could see where the data was going.

In 2011 I wrote one of the first practitioner guides to AWS migration, 336 pages published by Packt while most enterprises still thought the cloud was someone else’s science experiment (the book is still on Amazon). The same year I founded Australia’s first AWS user group in Melbourne. It is now the country’s oldest, with more than 4,500 members.

In 2015 Amazon named me an AWS Community Hero, one of only 22 worldwide at the time. I was also VP of the Australian Oracle Users Group somewhere in there, which dates me nicely.

My read on that period: the cloud bet was right, and it was also the setup for the contrarian one.

Why build against the cloud two years later?

Because some data should never leave its owner’s hands, and by 2012 everyone was busy handing it over.

So I spent my own money betting against the thing I had just written a book about. Podzy was a fully on-premise, encrypted alternative to Dropbox: file sync and share where the keys and the files stayed in the owner’s custody. People call that idea sovereign now. In 2012 it was just the observation that a hospital’s files belong in the hospital.

In 2013 Podzy won the national iAward for Best IT Toolset, ahead of entries from Fujitsu and CSIRO.

The honest caveat, so we’re not caught out: Podzy did not beat Dropbox. Contrarian bets rarely win on volume.

What it did was prove the idea well enough that Senetas acquihired the company in 2015 (the acquisition completed in February 2017). Senetas is the Melbourne company whose certified hardware encryptors have protected government and defence networks for nearly three decades, in more than 60 countries. Podzy became SureDrop, distributed globally by Thales. A proven pattern, not a hypothesis.

Why is AI the same problem again?

Because an AI assistant reads everything it can reach, at machine speed, and most organisations cannot answer the old question about any of it.

At Senetas I originated HAOS, a governed AI data platform. The design position is simple to say: one encrypted copy of your files, analytic tables and vector data, and every read, whether a person or an AI agent asked, checked by the same policy engine against the same rules. An agent acts on behalf of a person and can only ever see what that person is cleared to see. The line I use with customers is the whole thesis in one sentence:

If you’re not cleared to open a document, neither is your AI assistant.

I am the sole inventor on two US provisional patent applications covering parts of that work, filed in July and August 2026. Patent pending is true today. What the mechanism actually is stays off the internet, on purpose.

It is not a new habit, either. The first provisional I was involved in went to IP Australia in May 2008, filed through LogicalTech (AU 2008902168, “Data communication system”). It lapsed, as most provisionals do. Eighteen years between filings; the same instinct both times.

Thirty years after the machine rooms, the question has not changed. The reader has.

And the motorbike?

In 2023 I took a 1972 Honda CB350 to Lake Gairdner and set an Australian land speed record in the 350 M-CG class: 78.119 mph on salt. Not fast by superbike standards. Records are just claims with evidence attached, and that one comes with a timing slip.

Which is the same standard this site holds: every claim on the record links to a third party who will vouch for it.

Net: thirty years, five costumes, one question. The next decade of it is about making sure the answer holds when the reader is a machine.