Brian Deeker

Brian Deeker Software Architect
I build software that few can.

Fifteen years in enterprise .NET and Azure. I do not just write code for other people's products. I build my own, end to end: architecture, security, the business logic that actually matters, and the judgment to know which parts to get right the first time.

Vowlio

An AI powered wedding marketplace serving couples and vendors across 4 languages.

SiteGuardian

An accessibility scanning platform built to compete with established players.

GovSaaS

A multi tenant municipal software platform currently in pilot discussions with a local city government.

About

I have spent Fifteen years building enterprise software in .NET and Azure. Somewhere along the way I stopped being satisfied writing features for other people's roadmaps and started building my own products instead.

I am the sole technical developer behind Vowlio, a wedding planning and vendor marketplace with a real payments system, a real vendor CRM, and localization into 4 languages with plans for 16 more. I built SiteGuardian, an accessibility scanning tool, from the ground up as a second product running on the same architectural foundation. Most recently I have been designing and building GovSaaS, a multi tenant work order platform for municipal governments, currently in active discussions with local government for a Public Works pilot.

Building software is where I spend my time and where I do my best work. I would rather ship a product than talk about one.

Case Studies

Vowlio

A wedding marketplace built from nothing, run by two people.

Vowlio is an AI powered wedding planning and vendor marketplace: guest lists, budgets, seating charts, a day of timeline tool, an AI vendor matching engine, and a full vendor side CRM with contracts, invoicing, and subscription billing. I built the entire technical stack solo on ASP.NET Core, Azure SQL, and Stripe, with a directory seeded from 89,000 vendor listings across more than 120 cities and full localization into 4 languages.

The interesting engineering problems were not the obvious ones. Payment plan logic that has to stay correct across four tiers and two currencies. A directory search that has to stay fast at scale. Fraud and bot resistance after a coordinated account creation attack. The kind of problems that only show up once real users and real money are involved, which is exactly the environment I wanted to be building in.

SiteGuardian

Accessibility scanning, built to go up against the established players.

SiteGuardian scans websites for WCAG accessibility violations using three separate scanning engines running in parallel, with four subscription tiers built on a separate Stripe integration from Vowlio. Built on the same ASP.NET Core foundation, deployed independently, designed from day one as a reusable base I could stand up a second product on quickly.

In pilot discussions

GovSaaS

Municipal software, built the way a government security review actually wants to see it.

GovSaaS is a multi tenant work order platform for municipal governments, currently being evaluated by local government for a Public Works pilot. Every department's data is isolated at the database query level, not just hidden in the interface. Every change to every record is captured in an immutable, field level audit log, not just a last modified timestamp. Three distinct access tiers, from public facing citizen submissions through to full administrative control, each enforced independently at both the route and the data layer.

This is the project where the standard I hold myself to shows most clearly: not just working software, but software that would hold up under an actual security audit, because it was built assuming one would happen.

How I Work

I use AI assisted development seriously and deliberately, not casually. That distinction matters more than it might sound.

I run a real workflow: version control discipline, a second automated review pass on every significant change, and my own judgment as the final check on all of it. I have caught that second review tool confidently asserting things that were flatly wrong, more than once, and built a habit of verifying claims against the actual code rather than trusting output because it sounded authoritative. That is the actual skill now. Not whether you can use these tools, but whether you know when to override them.

I think this is where the field is headed, and I would rather be ahead of that shift than catching up to it later.

Get in touch

If you are evaluating software for a municipal government, building a product and need an architect who can take it from nothing to production, or just want to talk about how any of this was built, reach out.

brian.deeker@gmail.com