Built From
the Rubble
How Steller survived a war, a broken codebase,
and the AI that finally fixed everything
A B2B gift card platform. A development team in a conflict zone. A $10,000 project that couldn't be finished. And one non-coder founder who had to rebuild it all — with nothing but AI agents and a deadline.
A gap in the market.
A team across the world.
The idea for Steller was simple. Businesses that wanted to offer digital gift cards — loyalty programs, employee rewards, consumer promotions — had no clean way to connect to the vendors who supplied them. There was a gap in the market for a reliable B2B middleware: a layer that sat between integration partners and gift card vendors, handled the wallets, processed the orders, and returned the PINs.
I saw the gap. I knew how to close deals, structure pricing, and bring partners on board. What I could not do was write software. So I did what most non-technical founders do: I outsourced. A development team from the Middle East, working on a project basis. The total engagement: $10,000.
The team was talented. They designed a technically ambitious architecture — a modern microservices stack built on ASP.NET Core 9, PostgreSQL, RabbitMQ for asynchronous processing, Vue.js dashboards. By April 2025, the foundational database was live: 36 tables, the full data model for an order management system. By July, security features were implemented. By November, soft delete for compliance. By December, the frontend dashboards were taking shape.
On paper, it looked like a real product was being built.
The team went offline.
The architecture stayed.
In late 2025 the development team went offline. They were a team in a conflict zone, displaced by war. What they left was a codebase full of invisible debt, and a partner integration deadline that did not move with them.
The instinct most founders would follow is replacement. Find another developer. Pick up where the last team left off. Finish what was started. That is not what happened. The $10,000 engagement had produced a real data model and a real stack. It had not produced a system a non-coder could keep alive.
What I had instead was the architecture they left, a production server still tied to that conflict zone, and AI agents — Cursor, Qwen, Claude — as the only engineering capacity left. I am not a developer. I build Steller with those agents. No engineering team. No CTO. Just me and a context window.
"Every time I asked the agent to fix an order flow bug, it changed the right service — but broke two others it couldn't see."Muhanad Abdelrahim — Founder, Steller
Microservices looked correct.
Agents could not hold them.
Steller started as a textbook microservices architecture. RabbitMQ for messaging. Separate services for orders, wallets, catalog, webhooks. The kind of system that looks impressive in a diagram and makes senior engineers nod.
For a large human team, that shape is a feature. For a team of one human and several AI agents, it was a disaster. Every session started the same way. I would describe a bug — orders completing while wallets were not debited, or debited twice. The agent loaded the order service, made a change, and reported success. The wallet service was still wrong, because the agent had never seen it.
The order service published an event. The wallet service subscribed. Those were two codebases and two context windows. When I asked the agent to fix the order flow, it could only see the part of the flow in the file it was reading. The consumer, the wallet debit, the Bamboo vendor call, the webhook dispatch — invisible.
"The unit of architecture for agentic development is not the service boundary — it's the context window."
Microservices optimise for team independence. Agentic architecture has to optimise for context visibility. Those are different goals, and they often require opposite design decisions. The message queue — the thing that makes microservices powerful for human teams — is exactly what makes them hostile to agents.
Fat controllers.
The whole golden flow in one file.
I am not saying microservices are wrong. I am saying they are wrong for a small team using AI agents as the primary development force. For a team of thirty engineers they can still be the right answer. For one human and several agents, they were architectural poison.
The replacement is plain. Fat controllers: the order flow — wallet debit, Bamboo vendor call, PIN return, webhook dispatch — lives in one controller, readable top to bottom. Hangfire for background work: jobs are named C# classes. PlaceBambooOrderJob is a file an agent can grep, open, and read, including the wallet rollback when Bamboo fails.
The pivot was deliberate, not a rescue of the old shape. Service boundaries were consolidated. The two Vue.js 2.6 dashboards were decommissioned and replaced with a unified React 18 / TypeScript / Vite frontend. Fragmented API responses became a single mandatory envelope. Permission lookup tables were flattened. The patterns that helped a human team navigate were replaced with patterns an agent can operate.
This is not clean-code theory. It is what an agent can reason about when something is broken: read the controller from top to bottom, grep the named job, find the rollback. Session orientation dropped from the fifteen-to-twenty-minute search to about two minutes — read AGENTS.md, open the controller, start the work.
From the reckoning
to a system Qwen could run.
The pivot took 27 days and cost $672 in Cursor usage. That is the published cost of transforming the microservices system into an agent-ready monolith — architectural planning, the code transformation, the documentation, and the protocol layer that lets Qwen operate the system day to day. The rebuild shipped with zero critical defects in production.
Expected daily Cursor and Qwen spend after the pivot, for routine operations, was about $15. A 95.2% cache hit rate is why the documentation compounds: files written once are read across hundreds of sessions. Bede — the digital wallet of Zain Sudan — moved from staging into an active API integration. The platform onboards partners to a first successful API transaction in under sixty seconds.
"The lesson isn't that microservices are wrong. It's that microservices are wrong for a team of one human and several AI agents."Muhanad Abdelrahim — Founder, Steller · March 2026
Microservices versus fat controllers
for an agentic team.
This is not a universal rule.
It is a constraint.
Fat controllers break when a team grows past a handful of engineers. At that scale, several people editing the same controller create the merge conflicts microservices were designed to avoid. The context-window argument fades when humans can hold the context themselves.
Independent scaling becomes impossible. If the Bamboo integration needs many times the resources of catalog sync, one controller cannot scale those paths apart. Very large domains get unwieldy too. A controller that handles dozens of flows is not readable to a human or an agent. Steller has one golden flow, not forty.
The principle is not "always use fat controllers." The principle is: design the architecture so an AI agent can hold the entire relevant flow in a single context window. For Steller at this stage, that meant fat controllers. For a larger system, it might mean domain-bounded services with explicit, synchronous interfaces — not event-driven, and not invisible.
Rules for building with
agents, not a department.
Steller is now operated by Qwen Coder. It reads AGENTS.md at the start of a session, runs tests before calling the work done, and logs what it changed. One non-coder founder. Several AI agents. Zero full-time developers. And a system designed for the intelligence that actually runs it.
The human-interest version of this story — AI finished what the developers could not — leaves out the judgment. The complete account is the next essay.