I have a technical problem
Bring the gnarly thing — automation, infrastructure, security, an AI workflow, a haunted integration. Here's where engagements live and how to reach me.
/start-here
Choose your path through the Pakkit OS.
Pakkit.net is the home of Brandon Donaly's professional work, technical experiments, writing, music, gaming, and independent consulting. You should be able to jump straight to whatever you came for.
What brought you here?
Pick the path that sounds like why you came.
You don't have to understand the whole Pakkit OS. Find the door that matches your reason for showing up and start there.
I want to see proof of the work
Case studies with the architecture, the trade-offs, and the messy details — not just screenshots.
I want practical things I can use
Reusable playbooks and checklists, notes on building real systems, and the build loop behind them.
I want to learn or build alongside someone
Mentorship, pairing, and the kind of back-and-forth that turns a vague idea into something you can actually ship.
I want to see what's happening right now
A live look at what I'm building, the experiments in flight, and the gear I actually run.
I came for the side quests
The playful corner — DJ sets as PakkitStorm, gaming and esports, and the fox-flavored Pakkit identity that ties it together.
Build / Create / Play
Three sides of the same person.
Not separate brands — connected parts of how the work, the curiosity, and the play feed each other.
engineer
Build
Software, security, AI, automation, infrastructure, and products — turning weird ideas into resilient systems.
Explore Build →make
Create
Writing, music as PakkitStorm, side experiments, and the community tools that come out of them.
Explore Create →compete
Play
Gaming, esports, playful systems, and the curiosity-driven side quests that keep things fun.
Explore Play →Suggested first stops
A short route, depending on your time and mood.
Five minutes
Need help
Want depth
Still not sure? Send the messy version.
You don't need the right service name or the perfect technical vocabulary. Describe the problem however it lives in your head — half-formed, jargon-free, or three tangents deep.
If there's a real system hiding in there, we'll find the shape of it together.