Portrait of Gabriel R Mogaji

Rotense

Gabriel R Mogaji

Senior Software Architect

$ web · mobile · desktop · cli · security · 12+ years

I design systems that have to stay correct in production, and I build them across software engineering: web, mobile, desktop, CLI tools, security, and the pipeline that ships them.

Build

Apart from a consultation

A session is a review. These are the things I build, under a separate agreement once the shape of the work is clear.

Web applications

Browser products with the system behind them kept correct.

Mobile applications

Phone applications on the same system as the web.

Desktop software

Installed products that still have to stay correct after the first release.

CLI tools

Tools you run from a terminal, built for a job a person repeats.

Software systems

The product itself: the parts that have to work together in production.

Software security

Hardening auth, APIs, payments, secrets, and the path that ships them.

CI/CD

The path from a commit to a release you can explain.

IoT hardware

A little. Enough to connect a device to the software around it.

Stacks

What I build with

  • TypeScript
  • Python
  • Java
  • C#
  • ASP.NET
  • Spring
  • Spring Boot
  • Spring AI
  • Modern PHP
  • Symfony
  • Machine learning
  • AI
  • AML
  • Cursor
  • JetBrains / VS Code

Practice

What I will actually take on

A consultation is useful when the design is about to harden and the cost of being vague is real. These are the areas I will take on in a session.

CRM systems

Records, pipelines, and the work between teams. I design the platform a company actually runs on, and keep the edges clear.

Fintech systems

Wallets, ledgers, transfers, and reconciliation. I decide which system may change a balance, and what a person can see when it does.

AML

Monitoring, screening, and case handling. A score can rank a case; it should not be the only record of why money was held.

AI and machine learning

Scoring, assistants, and document work beside the ledger. I look at the data, the decision, and what happens when the model is wrong.

Software security

Threats at the edges that matter: auth, secrets, payments, APIs, and release paths. I harden what an attacker would actually try.

Enterprise

Several teams, one set of boundaries. Integration, identity, and a design another team can operate after the review is over.

Featured project

Reton

This is the company I'm building. Reton is a digital wallet. It holds the balances and a double-entry ledger. Interswitch is the payments company underneath: cards, transfers, and bill payments.

  1. Wallet

    Balances a person can see, and a timeline they can follow.

  2. Ledger

    Double-entry. Stricter than the status codes coming back from the rail.

  3. Rail

    Interswitch moves the money. It does not own the wallet.

Open the Reton project

WalletLedgerRail