Mon-Fri: 9am - 6pm PST
Systems that hold under load — designed, built and shipped by the person who answers your email.
Mykolay Chelabchi's Software Studio
The stack behind this page
Not a diagram. The actual thing.
Five processes, two MCP servers, one database. The public MCP and the chat backend run inside the site process; the admin MCP is its own unit so publishing survives a redeploy of the panel. States are measured when the page loads, not drawn in.
- nginx TLS · routing responding
- site Astro SSR responding
- admin TanStack Start responding
- public MCP 15 tools responding
- chat streaming responding
- admin MCP bearer responding
- postgres one database responding
All services responding · checked 3:06 AM PDT
In progress
Services, solutions and pricing are being rewritten and will land here shortly. The blog, the contact form and the MCP server are live now.
From the blog
All posts →-
80% of Businesses Are Paying for AI They Don't Use. Here's the Data.
New 2026 data shows only 17–20% of US businesses use AI in actual daily workflows — while 89% say they're "using AI." The gap is costing SMBs tens of thousands per year in unused subscriptions.
Jun 15, 2026 · 6 min read
-
Failover in Microservices: Keeping Your System Resilient
Learn how microservices automatically detect failures and reroute traffic to healthy instances. A practical guide to failover mechanisms, circuit breakers, and building fault-tolerant systems.
May 26, 2026 · 6 min read
-
Unifying two registries into one: the provider catalog refactor
When microservices and AI providers lived in two different registries, every code path that touched both paid a coordination tax. Here's how we collapsed them into one.
May 23, 2026 · 8 min read