Igor Katsuba — a system exposed over a few transports.
I build software whose users are increasingly not people. Agents call it, other systems depend on it, and it has to keep working when nobody's watching.
I'm a platform engineer working out of Valencia. For the last while I've been living at the seam between AI agents and backend infrastructure — the unglamorous layer that decides whether the clever stuff on top actually holds.
The framing on this page isn't a gimmick. It's genuinely how I think about building: define a capability once, expose it through whatever transport the caller speaks — HTTP, MCP, a CLI. Same idea applies to a person. This is me, exposed over the transports below.
Nearly everything I've built has been for other engineers rather than for end users: platform foundations, release paths, test corpora, the internal tools nobody demos. That comes with the other half of the job — hiring for the team, reviewing its code, and starting the weekly meeting where designs get argued out loud. The résumé has the specifics.
I write about frontend for a Russian-speaking audience, and take on the kind of infrastructure work most people would rather not touch.
Durable execution, agent orchestration, developer tooling, the glue between systems. I'm happiest one layer below the product, where reliability is the whole job.
Platform teams, hiring tracks, and the weekly meeting where designs get argued in public instead of in DMs. Building for other engineers is most of what I do, and the people half comes with it.
I run a Telegram channel on Angular and frontend, and a blog with 20+ articles. Explaining things is how I understand them, and it turns out other people find it useful too.
Conference talks on monorepos, build tooling, and pipeline acceleration — Frontend Conf, CodeFest, Podlodka. The recordings age; the problems they solve mostly don't.
An Angular course an agent takes itself. Delivered over MCP, built for the world where the student isn't always human.
02roostA native macOS workspace for Claude Code sessions — projects, tabs, a tree of terminal panes, and an attention queue that tells you which agent is stuck.
03nx-cache-serverSelf-hosted remote cache for Nx. S3, Docker, Helm — bring your own infra, keep your build times.
04mutatesAST mutation toolkit — mutate the AST, not your brain. Hands for an agent that needs to rewrite code and be sure it did.
05ng-httpExperimental declarative HTTP server written with Angular. What if your backend spoke the framework your frontend already does?
06deno-mastraAI agents built with Deno and the Mastra framework — the runtime and the orchestration, end to end.
07serverless-redisHTTP → Redis server, Upstash-compatible. Hono + Deno, one click to deploy on Railway.
Legal-tech SaaS. The platform, the release path, the incident root cause, and the company's internal AI agent platform.
- Root-caused a full production outage — a migration's ALTER TABLE stuck behind an orphaned transaction, poisoning the Postgres lock queue until the connection pool went with it — then fixed the class with bounded timeouts at the migration-session layer.
- Traced a three-day, traffic-independent database CPU climb to one long-open transaction pinning the xmin horizon, and named the single metric that catches it in an hour rather than three days.
- Built the internal AI agent platform end to end as sole author: Slack and web surfaces, per-user MCP OAuth, sandboxed multi-agent execution, and a durable event log that fixed chat resume losing turns.
Consumer fintech. Led the frontend platform team and built the foundation every frontend product shipped on, from the internal CRM to the public site.
- Led the platform team and owned the shared foundation — architecture, build and release tooling, the component and design-system layer — across every frontend surface the company had.
- Hired into the team and ran interviews end to end.
- Started the weekly internal talks, so design decisions got argued in the open instead of in direct messages.
Built the company's frontend platform. Parts were released as open source, which is the visible tenth of it.
- Built platform systems rather than product features: an in-house error-monitoring service and its browser client, analytics systems, a micro-frontend framework, and the shared build tooling underneath.
- Led Angular hiring — owned the interview track and kept the bar consistent across a pool of twenty interviewers.
- Started the weekly talks and knowledge-sharing meeting, which outlived my tenure.
Product frontend, and the first tooling I owned rather than used.
Where I started — large government-scale web applications.
This server accepts connections.
If you want to talk infrastructure, agents, or the tooling underneath both — or just argue about durable execution — open a connection.