Ajo (@Ajo_Circle) header
Ajo (@Ajo_Circle) profile picture

Savings circles that work across borders. Passkey sign-in, AUSD, built on Monad.

Joined October 2026
Photo by Ajo (@Ajo_Circle)Photo by Ajo (@Ajo_Circle)Photo by Ajo (@Ajo_Circle)Photo by Ajo (@Ajo_Circle)Photo by Ajo (@Ajo_Circle)Photo by Ajo (@Ajo_Circle)Photo by Ajo (@Ajo_Circle)Photo by Ajo (@Ajo_Circle)
Our #neathack submission Software breaks every day. The real problem is what happens after the failure. An AI can suggest a fix, but how do you know that fix actually works? And what stops the same bug from coming back? That’s what I’m exploring with Patient Zero 🧬, my solo build for #neathac under Team Trace Element. Patient Zero deliberately tests an application with unexpected inputs, investigates failures, attempts repairs in a quarantined copy, and only promotes a fix if it passes the required checks. But I wanted to take it a step further. Every verified fix can leave behind a regression test, an antibody designed to catch the same problem if it returns. The goal isn’t just to have AI write code. It’s to make fixes prove themselves before they earn their way back into the application. 🛠️ The build: • @neatlogs tracks the healing workflow, from detection to promotion. • @EntireHQ records the development process through checkpoints. • @arithecfo helped me explore the business side, including pricing, costs, and runway. I’ve deployed Patient Zero on AWS, and the live version is ready to explore. It’s not perfect. One case still slips through, and that’s part of what I want to investigate through testing and feedback. Try it: patientzero-heal.duckdns.org… 🔬 Demo video below I’m interested in what people find when they try to break it. 🛡️
building agents is easy getting them to production is hard today we’re launching @neatlogs to fix that
245
27
4
219
32,021
If you’ve ever been in an ajo or esusu circle, you already know the power of saving together. You also know the quiet risk: everything depends on one person holding the pot. What if that part didn’t have to work that way anymore? That’s what we’re building with Ajo.
2
38
What if your savings circle didn’t have to depend on one person’s word? Ajo and Esusu have helped communities save together for generations, but managing everyone’s money still comes with trust challenges. That’s why I started building Ajo. 🔄
3
5
8
58
Ajo brings community savings on-chain using smart contracts to manage contributions and payouts. 🌐 Website: ajo-circle-teal.vercel.app/ 🎥 Full demo: youtu.be/-SwMvbZCvFw?is=z_bY… Built on Monad for the Monad Metropolis Hackathon. Keeping the tradition. Changing how trust works.
52
Millions of families save through ajo and esusu circles. The idea is simple: Everyone contributes. Everyone takes a turn. Everyone trusts the circle. But there’s one part of the system that hasn’t really changed.
1
1
1
2
190
Not by replacing ajo. By rebuilding the part that creates the biggest point of failure. The circle stays. The contributions stay. The community stays. But the money and the rules move somewhere they can be verified.
1
1
15
That’s the idea behind Ajo. Savings circles, onchain. No collector holding everyone’s money. Just members, contributions, rules, and a system that handles the rest. Something’s coming. 🔄
14