About Ridox Studio

Ridox Studio is a small software engineering studio based in Nigeria. We build web apps, mobile apps, cloud infrastructure and AI features for clients, and we run three products of our own. This page covers where the name comes from, what we work on and how we work.

Where the name comes from

Ridox is a play on redox, the chemistry term for a reaction that only happens as a pair: one thing oxidises while the other reduces, and neither half happens alone. We wanted the studio to work the same way, with design and engineering done together by the same people instead of passed between two departments. Our tagline, “software systems engineered at the reaction point”, comes from the same idea.

The first commit is dated March 2022. The studio then sat quiet for four years and restarted in 2026. We’d rather tell you that than pretend it’s been running nonstop.

What we work on

We like problems we can point at. RISMS, Cilbup and Resurgee all started because something people needed either didn’t exist or didn’t hold up once people used it every day.

In client work we keep looking for the same thing: the assumption a team stopped questioning. In our experience that’s where software breaks. The payment flow that works until a refund comes in, or the admin tool that was built for a demo and then had to survive a full school term.

Client work and studio products

We do two kinds of work.

• Client work. Commissioned builds and advisory engagements. When we hand a system over, we walk your team through how it works so you’re not left with a black box. You can see some of it on our work page.
• Studio products. Software we build and run ourselves: RISMS, school management software for Nigerian schools; Cilbup, anonymous messages and tips for creators; and Resurgee, an AI layer on top of Google Tasks and Calendar. Running our own products means the advice we give clients comes from software we keep online ourselves.

The team

We’re small on purpose. The people who scope your project are the same people who write the code and pick up the phone when something breaks. We work across product, engineering and AI, and we only add AI where it actually helps the product.

We’re not going to list headcounts or job titles we don’t have. If you want to know exactly who you’d be working with, ask us. It’s a short conversation.

What’s not on this page yet

This page isn’t finished. Still to come: a public build log that links the decisions we’ve already written up on this blog, named case studies once clients are happy for us to name them, and a dated note on team size and what we’re building right now.

---

Want to build something with us? Get in touch or read how we work. No sales funnel, just a conversation.