We closed off the database, two days after saying we wouldn't.

On September 24th I wrote down a decision: during the beta, the live database would stay reachable from outside Neeos's own servers. It was convenient, and I judged the risk acceptable. Two days later I took it back.

What changed my mind

Thinking about it again, the honest picture was uncomfortable. My laptop held master keys that didn't require a second factor to use, and AI agents run on that laptop. A mistake or a stolen laptop could have reached the live data. Convenient for me meant exposed for you.

What's different now

• The production database can only be reached from inside Neeos's own servers. It's no longer reachable from the open internet.
• Any administrative access requires a second factor, a one-time code, and sends me an email alert when it's used.
• Security alerts go to a single inbox I actually read.

It means that if I want to look at something in production, I now have to stop and prove it's me, every time. That friction is the point.

What this does and doesn't say

It does not make Neeos “secure” in some absolute sense, and I won't use that word as a finish line. It closes one door that I'd left open on purpose. I'm writing the reversal down rather than quietly fixing it because the decision two days earlier was mine, and you deserve to know I made it and why I unmade it.

Written October 21, 2026 from the build log, and dated to when this happened.