GateBolt
About

Built by one person, on the side.

Which is either a reason to be careful, or the reason it exists.

J

I'm Junayed. I build things around a day job and twin toddlers — Layzer, a few others, and now GateBolt. Every one of them is written with coding agents, which is how I ended up here: git could always tell me what changed, and nothing could tell me what the agent had set out to do.

A record that depends on the agent telling the truth isn't a record. That's the whole product.

What it commits to

Three things that won't change.

Deterministic, or it isn't evidence

No model sits in the scoring path. A verdict you can't reproduce is a verdict you can't defend.

Your code stays on your machine

Paths, actions and line counts, plus the task the agent was given, which agent it was, and the branch. File contents are never sent, and never will be.

The record outlives the account

Revoking a key or deleting a user doesn't erase history. That's what makes it worth keeping.

Tell me what's wrong with it.

Early enough that your opinion changes the product.