I'm Kelvin, and Talvigen Technologies is my fractional architecture practice. I design, build, and operate production systems, and work fractionally so your team gets senior judgment without a full-time hire.
I've been building software since 2008, all of it in and around SaaS. That span covers a full generation of platform change: on the data side, from SQL Server and Oracle to PostgreSQL; on the infrastructure side, from on-prem deployments through hybrid setups to fully cloud-hosted systems. I've designed and migrated products across those transitions - so the move you're weighing is usually one I've already made at least once.
I'm a certified solutions architect on both AWS and Azure, and I still write code, because architecture divorced from implementation is just opinion. The aim is judgment that holds up in a design review and in a pull request alike.
I also build and operate my own SaaS product, so my advice comes from the daily reality of shipping software - not consulting theory.
Every significant call becomes a short decision record - context, options, trade-offs, decision. Your team inherits the reasoning, not just the outcome.
Deliverables are design docs, standards, and reviewed code - artifacts your engineers use the next day.
Written reviews on a predictable cadence beat standing meetings. Synchronous time is spent where it earns its cost.
Engagements are designed to end well - ownership, docs, and standards transfer to your team from day one.
If the fit is wrong, or a cheaper shape solves your problem, you'll hear it on the first call. I take at most two embedded engagements at a time.
Reviews don't assume follow-on work, and recommendations never depend on hiring me to execute them.
Bring a real problem to the intro call and leave with a useful answer, whether or not we work together.