01
Security · Precheck
Security Precheck
Guided security precheck for new client requests: set scope, verify, sign, derive pricing, and hand off cleanly into the portal before any scan starts.
Open to conversations
ANGUS UELSMANN
I build systems that hold upAPIs people can rely onbackends without dramatools that stay usefulworkflows that do not fight backlocal-first softwareproducts that survive real useinfrastructure that stays quiet
Independent software builder focused on backends, security, product architecture, and tools people can still understand later.
Context
System first. Interface second.
I build software from the bottom up: data, permissions, failure cases, performance, privacy. The interface matters. But trust is usually won or lost in the parts people do not see first.
No tracking. No games. Here is how this site works.Thinking
A product shows pretty early whether someone thought it through.
Product
Products show whether the idea holds.
Guided security precheck for new client requests: set scope, verify, sign, derive pricing, and hand off cleanly into the portal before any scan starts.
View Security Precheck.
01
Security · Precheck
Security Precheck
1 / 6
LAB
Small tools.
Real friction.
Some tools do not start as big product ideas. They start as annoying moments in a real workflow. When a small tool keeps removing friction, it earns a place here.
PhishGuard
Automatic phishing, download, ad and link-risk signals.
ImageLite
Collect images from pages, tabs, files or screenshots, then optimize and export locally.
FocusShot
Blur, dim or hide sensitive page details locally before taking screenshots.
Stack
Tools I actually reach for
How I work
Small surface. A lot underneath.
I start where projects usually break later: data models, permissions, state, performance, privacy, and the path real users actually take.
Read the entity profile.What do you build?
Web products, backend systems, security-adjacent tools, and small developer tools that do not turn into baggage after launch.
Who is this for?
For people who need more than a polished interface. The product has to hold up in production too.
How do projects start?
With the goal, risks, data flow, and the parts that can hurt. Then I build in small steps so the system proves itself early.
Why backend-first?
Because trust is rarely lost at the button. It breaks in auth, state, slow media, unclear data ownership, or code nobody wants to touch again.
Contact
Have something
worth building?
Got something that needs to be built and should not fall apart in production? I take on a few projects a year, usually the kind where architecture, security, and clean execution actually matter.