About Gribbite

Gribbite is a one-person technology lab. It exists because a lot of what gets said about AI systems, cloud infrastructure, and security is said by people who have not run the thing they are describing. The only reliable fix for that is to run it.

The work here is deliberately small. Bite-sized: a question that fits in a weekend, a rig that fits on one desk, a write-up that fits on one page. Small experiments finish, and finished experiments can be checked.

Who runs it

One person, with roughly fifteen years in enterprise identity, endpoint security, and detection engineering — mostly in environments where getting it wrong was expensive. This site is the personal half of that: the parts I want to test without a change advisory board, on hardware I own.

What this is not

• Not affiliated with, endorsed by, or speaking for any employer, customer, or vendor. Everything here is personal work and personal opinion.
• Not a consultancy and not selling anything. There is no pitch at the end.
• Not a news site. If something is well covered elsewhere, the link goes on the resource shelf instead of being rewritten here.

How things get published

A project goes up when there is enough to reproduce it: hardware, versions, method, and results — including the runs that failed. Pages get revised as the work continues rather than frozen at the moment of publishing, so a project page reflects where that project actually stands.

The name

Gribbite came from wanting something short, unclaimed, and easy to say out loud. The mark is a circuit-etched gecko: small, quick, and interested in everything. It fits.

Getting in touch

If you are working on local inference, agent security, or detection engineering and want to compare notes, mail is the best route. I read everything and reply to most of it.