This morning I was thinking about Madame Curie and Amelia Earhart, two of my professional inspirations. Not because they were famous, but for the constraints they were working within. They had serious questions that demanded answers. And with limited time and resources, both found new ways of work and each accomplished things most of us never will.

The past few weeks I’ve been busy coding the next version of the security platform I’m developing. I’ve spent a lifetime in the tech industry and seen us go from waterfall ways of testing everything (because your software had to work for a year before any updates), to move fast and break things. We give startups million dollar budgets and let them fail. Big promises, big platforms, that feels wrong.

So I’m building PyLog different.

I prototyped my software including a local LLM two years ago on a 2018 i3, 8GB discarded office laptop. No cloud involved, no API bills or tokens. Just a local-first security engine that turns raw logs into clear answers. Because security shouldn’t require a data center.

My goal isn’t to sell you more dashboards or alerts. PyLog is designed as a small appliance that plugs into the wall and guards your network when you sleep (and also when you work). The principles are simple:
– Your network stays under your control
– Your data never leaves your environment
– Your identity and assets are protected locally
– Security should be understandable, not mysterious

When you trust someone to watch your perimeter 24/7, you shouldn’t need a Ph.D. to configure it. You just plug it in. We are returning to a time where craftsmanship beats scale. Where every line of code has been read, understood and tested by the person who created the code file. And ‘local’ means you own your truth.

That is the idea behind PyLog.