Built on the bench,
not in a boardroom.

Synapsi is a one-person operation. I'm an IT administrator at an IT asset disposition facility in Northern California — the kind of place where hundreds of machines come through the door every week and every drive that leaves has to be provably sanitized.

That job is where all of this comes from. Every tool on this site started as something I needed and couldn't find: a procedure I was tired of hunting for in a shared drive, a diagnostic pass that took three separate utilities, a report that had to be assembled by hand because nothing exported cleanly.

Why the tools look the way they do

Software built for a bench has different requirements than software built for a demo. It has to work on an isolated network. It has to produce output an auditor will accept. It has to be usable by someone who is standing up, holding a laptop, and has four more to get through before lunch.

That shapes a few decisions you'll notice:

• Local-first. No cloud dependency means no outage takes the floor down, and no compliance conversation about where customer data went.
• Plain output. Reports export as JSON, Markdown, and PDF. If Synapsi disappeared tomorrow your records would still open.
• No accounts, no subscriptions. Licenses validate locally. A license server is one more thing that can fail at 7am on a Monday.
• One job per application. Small tools that do one thing completely beat one large tool that does five things adequately.

Background

My day-to-day covers network infrastructure, identity and device management, imaging and deployment, and data sanitization workflows across a multi-certification environment — NAID AAA, R2v3, ISO 27001, e-Stewards. I work to NIST SP 800-88 standards regularly enough that the sanitization tooling here reflects how the standard actually gets applied, not how it reads on paper.

Before the admin role I was a team lead on the laptop line, which is the part that matters most for this software. I built these because I was the one using them.

Where this is going

Most of the applications carry a one-time price, which is what keeps development going. There's no subscription and there won't be one — you buy a tool once and it stays yours. Knowledge Base is free and will stay free.

Custom work is the other half of it. If you need something specific built, the request form is the place to start.

If you just want to say a tool was useful or that something is broken, the contact page has an address. Both are read.