DEV Community

Cover image for Hello, Dev.to: the three S's of regulated software, and the backend I'm building
Niyi Gbodimowo for Kilimanjaro

Posted on Edited on

Hello, Dev.to: the three S's of regulated software, and the backend I'm building

In the 90s in England, my mates and I spent endless nights tearing apart computers and rebuilding them one component at a time. Twenty-five years later I'm still doing something similar, except the computers are backends and the components are the controls regulated customers ask for.

Hi, I'm Niyi. I'm a Nigerian-British deep-tech engineer, an optimist, and the founder of Kilimanjaro. I'm writing from Lagos, Nigeria, and a good part of what I care about is a better future for Nigeria. This is my first post here, so let me say who I am and what to expect.

The path here

I fell in love with tech in those nights of tearing computers apart, coding in Pascal, then C, C++ and Java. I earned my degree in Computer Science at the University of Bristol, and it has been an unending stream of languages, frameworks and security standards ever since.

My first startup was an ad-tech company. Then I built a software consultancy, and then a BaaS for some of the biggest regulated companies in Africa, architecting critical software for multi-billion dollar banks, pension funds, and asset managers, which is what led my meandering journey to Kilimanjaro.

The three S's

Over 25 years I've learned that, in regulated industries, three things rule: stability, security and standards. Your software must keep running, protect sensitive data and pass audits. Teams that ship a working prototype usually find out how much that costs when the first regulated customer sends a 100-line feature checklist, and the backend has to be rebuilt to answer it.

Kilimanjaro is my answer: a backend where those controls are part of the services from the first day, so you don't rebuild. You get a database, files, real-time streams, AI guardrails, serverless compute, encryption, access control and an audit trail as one set of services, with the rules about where data lives and who can touch it built in. If you want details, the docs have them.

What you'll find here

I'll try to post regularly, in two kinds.

The journey. What we decided, what we got wrong and what changed our minds. The names we corrected, the pages we hid until they were true, the questions customers ask that no tutorial prepares you for.

Fixes for hard problems. The strange ones. The bug that only appears under a particular region setting, the encryption question that sounds simple and is not, the business problem nobody warned us about. Each post says what the symptom looked like, why it was hard, what caused it and how we fixed it, so you can fix yours faster than we did.

Kilimanjaro's own blog, the Summit Log, is where the practical how-to material lives. Here I'll tell the stories behind it.

Over to you

If you're building enterprise apps, I might be able to chip in some advice on questions like:

  • How do I get through the dreaded 100-line feature checklist that procurement sends?
  • How do I implement field-level encryption ahead of a PCI DSS 4.0/4.0.1 audit?
  • How do I avoid GDPR violations by sharding per-user data across regions?
  • How do I talk to an HSM through PKCS#11 or KMIP?

Tell me in the comments. The best ones become posts.

Thanks for reading, and see you next Thursday.

Niyi

Top comments (0)