I build practical automation for IT, identity, and security teams.
My focus: messy access requests, ugly device data, noisy compliance asks, and the "Can you just pull me a report real quick?" fire drills every company deals with.
I take the work people do manually in tickets and spreadsheets… and turn it into something consistent, reviewable, and repeatable.
-
Automate the boring stuff first.
If humans are doing it over and over in tickets, that's a bug. -
Security and auditability are not optional.
I design workflows where changes are reviewable, reversible, and attributable. PRs and logs > mystery admin actions. -
Identity is the source of truth.
Okta / Entra / SCIM should drive access. Not “who asked nicely in Slack.” -
Make it deployable by a real company.
I build things IT can actually run in production, not just pretty demos. -
Respect for IT reality.
Legacy systems, compliance pressure, legal hold, vendor review, offboarding risk — I don’t pretend those don’t exist. I build with them in mind.
I live in the overlap of IT engineering, security, identity, and internal tooling.
I spend personal time turning painful internal workflows into reusable building blocks that other teams can adapt.
If that work helps you reduce manual IT work, tighten access control, or survive audit season with less drama:
Your support = more boring-but-critical IT automation released openly.
- Trying to make access / offboarding / device posture less manual?
- Dealing with identity sprawl across Okta + Entra + SaaS?
- Need internal automation that security will actually approve?
DM me on GitHub or open an issue.
All work here is created on my own time, in my personal capacity. It is not developed for, sponsored by, or endorsed by my employer (past or present). || No SLA, no warranty, no guarantees. This is community/open source tooling: use it at your own risk, and only if you are allowed to do so under your company’s policies, contracts, and security rules.
By using any code or ideas from my Open source repos/tools, you accept that:
- I am not providing professional services or support.
- I am not responsible for any impact, breakage, security exposure, audit findings, data loss, compliance issues, or production incidents.
- You are responsible for reviewing, testing, and getting the appropriate approvals before using anything in your environment.