A note about this build log entry: I published this after the week it covers. DevNitro reconstructed a draft from work-related entries in my journal, Git commit history, and time tracking. I reviewed, edited, and approved the final post. The story reflects what I knew and built at the time.

From the Backlog to the Build Log

Week of February 27 - March 5, 2026

What I Worked On

This was the week DevNitro stopped being a thing only I could run.

Up to now, running it meant my machine, my setup, my head full of steps. This week I built a cross-platform client distribution and self-update system with release automation. A user installs the CLI, and it can update itself to the next version without me walking anyone through it. That sounds small until you have someone waiting to use your software and the only install instructions live in your memory.

The reason mattered. A real customer had committed to paying for two seats, and I was the bottleneck. So the week bent toward everything that stands between me and handing over the keys: distribution, updates, and the database.

Databases were the other big piece. I made migrations run automatically on startup, with a confirmation prompt before anything changes, so a fresh install brings its schema up to date on its own. I moved the deployment workflow off a pile of Bash and onto a proper C# file based program, and I got the schema files to publish correctly for the generated sites, not just the core. This is the same multi-database migration work from last fall, now wired to run without me in the loop.

Billing kept moving too. I added multi-seat subscriptions, real seat counting, and rebuilt the billing overview to read from local data instead of calling Stripe on every page load, picking up right where last week's billing overhaul left off.

What the AI Did Well

The distribution and release automation is the kind of wiring the agent is good at once I decide the shape. Cross-platform packaging, a self-update mechanism, and the release steps came together fast. It also handled a wide theme refactor cleanly: moving the whole theme system to CSS variables so dark mode and light mode both work from the client instead of being half-set on the server. And it added hierarchical Git strategy settings, so a company can set a worktree-or-branch policy and have it inherit down through team, project, and user, with a worktree tool the agent uses to honor it.

What Needed Correction

The honest friction was onboarding, which is exactly what breaks when a second person shows up. I logged in as a fresh test user assigned to a company and could not see the company. It sat in the menu but returned "company not found." Projects said "you are not authorized." The new user was on one team but not the others, and I had no clear rule for how employees get added to teams automatically. None of that shows up when you are the only account in the system. It all shows up the moment you invite someone.

Dark mode fought me too. It would not start in dark mode even when it should, and the dropdown controls misbehaved during theme init. The fix was to stop setting the theme on the server and drive it entirely through CSS, which is cleaner anyway.

What Shipped

DevNitro has a cross-platform CLI with self-update and release automation. Databases migrate automatically on startup behind a confirmation prompt, and deployment runs through a C# tool instead of Bash. Subscriptions support multiple seats with accurate seat counting, and the billing overview reads local data. The theme system runs on CSS variables with working dark mode, and Git strategy is a hierarchical setting enforced from company down to user.

The Numbers

Category Hours
Product / Features 28h 16m
Deploy / Infra 16h 2m
Business 4h 15m
Content 2h 44m
Testing 2h 33m
Community 2h 11m
Total 56h 1m

Sixteen hours in deploy and infrastructure is unusual for me, and it tells the story: this was a week about making the deploy path boring again.

The hardest part of a product is not the demo. It is the second user. This week was mostly the plumbing that turns a thing I run into a thing other people can install, update, and trust. Not flashy, but it is the difference between a project and a product.

Curious how this site was built?
Watch the 5-minute walkthrough at devnitro.com →

An AI built this blog (but not this post)

This entire blog system (domain models, database, services, UI, auth, etc.) was built by DevNitro on its own in 95 minutes. I recorded every second.

    We respect your privacy. Unsubscribe at any time.

    Built with Kit