Build · Optimise · Execute

Engineering scale. Engineering growth.

Scale for enterprises whose systems have to hold up under real traffic and real money. Growth for startups that need to ship this quarter and keep shipping.

Start a project Meet our products

Trusted by teams in payments, crypto, media, travel and hospitality.

APIs and services
Web applications
Mobile applications
KYC and payment integrations
Security hardening
Managed servers
Offsite backups
Incident response
Annual SLA
Corporate sites
Launch sites
Business mailboxes
SPF, DKIM, DMARC
Newsletters and campaigns
Reoclo
Prawnwire

Four things we do well.

Pick one, or hand us the whole stack. Everything below is built the same way: a brief, a PRD you sign, then the work.

No surprises. That's the whole method.

Every engagement produces documents, not just code. That isn't bureaucracy. It's how you stay in control of something you didn't build yourself.

Brief and PRD
You tell us what you need, in your own words. We write back a PRD: what's in, what's out, the shape of the system, and what we're not sure about yet. Nothing gets built until you've signed it.
Build in the open
When something you depend on changes, you get a change notice before it ships: what changed, why, what to do, and by when. Your mobile team gets the same note we'd write for ourselves.
Run with reports
When production breaks, you get the root cause, the fix, what was regenerated or reconciled, and what still needs a decision from you, in a written remediation report. Not a Slack thread.

Why teams stay.

The people who build it are the people who run it.
No handoff to an ops team that has never seen the code. The engineers who shipped your system are the ones watching it in production.
You get paper, not promises.
A PRD before we start, change notices while we build, remediation reports when something breaks, and a clear statement every month.
We use what we sell.
This site runs on Reoclo and sends its mail through Prawnwire. We built both because client work needed them, and we run them every day.
We say the uncomfortable thing early.
If the brief asks for the wrong thing, you'll read that in the PRD, not find out after launch.

Built for our clients. Now yours too.

We needed a control plane for the servers we run and email we could trust. So we built them. They run our own work, and now they can run yours.

Reoclo
Private betareoclo.com
Deploy to any server. Zero lock-in.
Connect any Linux server you control, on any cloud or bare metal, and push to deploy, tail logs, restart, roll back and rotate secrets. It works through git, a REST API, and an MCP server for your agents. Our managed infrastructure runs on it.
Request access
reoclo
```
$ reoclo apps deploy web
queued   web   lagos-1
$ reoclo deployments stages d_7f3a
build    ok
push     ok
deploy   ok
$ reoclo apps logs web --follow
web  listening on :4321
web  GET /healthz 200
```
Prawnwire
Early accessprawnwire.com
Encrypted email on your own domain, with an API to send from it.
An inbox only your devices can decrypt, plus a transactional API for the product you build. SPF, DKIM and DMARC are set up for you. Bulk and campaign sends are refused at the API, so your password resets never share a reputation with anyone's newsletter. The mailboxes we provision for clients run on it.
Join the early access list
POST /v1/emails/send
```
$ curl https://api.prawnwire.com/v1/emails/send \
  -H "Authorization: Bearer pw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": "[email protected]",
    "to": "[email protected]",
    "subject": "Welcome aboard",
    "html": "<p>Thanks for signing up.</p>"
  }'
```

Some things we've handed over.

Names withheld. The details are what matter.

Fintech companies
More than one of these started the same way: a security audit of the entire stack, written up with what we found and a path to fixing each item. Each time, we were hired to do the fixing, then put on permanent retainer on the strength of the work. Disaster recovery followed the same arc: audit, fixes, retainer.
Handed over: Audit reports, the fixes, and a permanent retainer.
Payments company
We host and operate their production and staging with offsite backups under an annual SLA, on a fixed monthly retainer. They think about their product. We think about the servers.
Handed over: Production they don't have to think about.
Hospitality company
They needed to turn interest into customers: capture leads, reach them by email, meet them on mobile. We built tailored websites, put their business email on Prawnwire, and shipped a mobile app MVP. They capture users now, and sales have improved.
Handed over: Websites, mailboxes on Prawnwire, and an app MVP.
Media platform
We built the publishing platform behind two titles, then stayed on to host it and run its email campaigns.
Handed over: The platform, hosting, and campaigns on one monthly statement.

Questions we get asked.

Straight answers. If yours isn't here, ask us.

What happens first?

You send us a brief in your own words. We write back a PRD: what's in, what's out, how the system or site will be shaped, and what we're unsure about. You mark it up, we revise, you sign it off. Then we build against it.

How do you price work?

Two ways. Fixed scope for work with a clear end, like a site, an integration or a launch. A monthly retainer for ongoing engineering or for running your infrastructure. The contact form has budget bands in naira. USD is fine, just say so in the message.

Can you just run what we already have?

Yes. Managed infrastructure is its own service: production and staging servers, offsite backups, monitoring, incident response and an annual SLA, on a monthly retainer. We'll read the code before we agree to be on call for it.

What happens when something breaks?

You get the root cause, the fix that shipped, what was regenerated or reconciled, and what still needs a decision from you, in a written remediation report. Routine work shows up on a monthly statement, not as a surprise.

Do you work with companies outside Nigeria?

Yes. We work with international clients and we meet you where you are. Every client has a named project lead who is available as you need them. Because everything is written down, we also work well asynchronously: nobody has to be awake at the same time to know what's going on.

Where does our software run?

On servers you own or rent, with any provider, managed through Reoclo. Nothing is locked to us: the servers are yours.

Who owns what you build?

You do. It's written into the engagement terms you sign before we start.

Do you do design?

For websites, yes, with our design partners. You approve a lookbook before any code is written. For product work we design the system and the screens with you, and bring in a partner when a project needs more visual design than we should be doing ourselves.

Let's build something you won't have to worry about.

Tell us what you need to build or keep running. We reply by email, usually within one business day.

Start a project

[email protected]WhatsApp

Engineering scale. Engineering growth.

Four things we do well.

Product and backend engineering

Managed infrastructure

Websites and launch sites

Email and communications

No surprises. That's the whole method.

Brief and PRD

Build in the open

Run with reports

Why teams stay.

The people who build it are the people who run it.

You get paper, not promises.

We use what we sell.

We say the uncomfortable thing early.

Built for our clients. Now yours too.

Reoclo

Prawnwire

Some things we've handed over.

Questions we get asked.

Let's build something you won't have to worry about.