The builder behind the practice
I've spent 25+ years writing production code — starting before C# was cool, back when ASP.NET Web Forms was cutting edge and deploying meant burning a CD. Over that time I've built custom software for enterprises across finance, healthcare, logistics, and SaaS. The kind of systems where downtime costs real money and a bad architecture decision compounds for a decade.
I led cloud migrations for companies moving billions in transactions. I served as Tech Lead and Interim CTO at Catch Health, a health insurance marketplace serving 400K+ members, where I architected AI-powered compliance monitoring, built integration layers across corporate systems, and led the technical team through rapid growth.
Before that, I spent years deep in insurance technology — MGAs, TGAs, brokers — environments where fragmentation doesn't just slow you down, it creates compliance risk and costs real money in manual commission reconciliation, delayed carrier launches, and agent churn. I built platforms, rescued failing projects, and learned what actually matters when shipping enterprise software.
Why Cloudflare, and only Cloudflare
After two decades of building on every major cloud — AWS, Azure, GCP — I noticed a pattern. Most consulting firms spread themselves thin across all three. They know a little about everything and a lot about nothing. Their architects spend half their time reading release notes for services they used once two years ago.
I decided to go the opposite direction. Deep expertise in one platform beats shallow knowledge of many. Cloudflare's developer platform was it — Workers, D1, R2, Durable Objects, Queues, KV, Vectorize. A complete runtime that deploys globally, scales to zero, and runs TypeScript end to end. No Kubernetes. No VPCs. No cold starts.
That conviction is the foundation of my consulting practice at George Rios Consulting LLC — a practice built entirely around Cloudflare's edge platform. Not "we also do Cloudflare." Cloudflare is all we do. Every architecture, every build sprint, every line of code runs on the same stack I use for my own products.
What I'm building now
Real products running at the edge. Not demos — software with users.
Origami
gambase.net
The CRM for insurance agencies. Multi-tenant SaaS, 100% on Cloudflare — isolated database per agency, provisioned on signup and routed at the edge.
DoubleSpace
doublespace.io
Cloud sync without the cloud bill. Real-time WebSocket sync, R2-backed storage with zero egress, native drive mounting.
Moreover
moreover.dev
Email-fed project intelligence. Email links and notes to yourself; it summarizes, files, and flags what contradicts what you believe.
Rehearse
rehearse.sh
CI feedback in seconds, before you push. Runs GitHub Actions workflows on every save — ~63× faster than GitHub Actions. Apache 2.0.
Facturably
facturably.com
Invoice like you deploy. Track time, generate PDF invoices, get paid via Stripe — from a portal, REST API, CLI, or MCP server.
Engrave
tryengrave.com
The black box recorder for AI agents. Tamper-evident traces of every tool call, with inclusion proofs you can verify offline.
PRYVC
pryvc.com
OAuth for contact details. Every form-fill becomes a consented, time-limited, revocable share — with an audit trail both sides keep.
CommissionSight
commissionsight.com
Reconciles carrier commission statements in any format, scores every member month over month, and recovers the commission you're owed.
My approach
Four principles that guide every engagement and every product I build.
Deep beats broad
Specialist in one platform, not generalist across many. I know Cloudflare's edge platform at the level where I can tell you what will break before you build it.
Ship deployed code, not slide decks
Every engagement produces running software. Architecture reviews come with working prototypes. Strategy decks come with deployed proofs of concept.
TypeScript all the way down
One language, edge to database. No context-switching between Python Lambda functions and Go microservices and Terraform configs. TypeScript everywhere.
Transfer, don't hoard
Your team should own the knowledge. Every sprint includes knowledge transfer. I could write all your code, but it's better if your team can maintain and extend it.