ATAIMO EDEM · ENGINEERING & ARCHITECTURE

Complex systems.
Clear thinking.

Architecture that holds up in the real world.

I connect architecture, hands-on engineering and customer ownership to make enterprise API platforms work — and keep them working.

LAGOS, NIGERIA · WORKING GLOBALLYSCROLL TO EXPLORE
01API Management02Solutions Architecture03Cloud & Kubernetes04Customer Engineering

From friction
to forward motion.

Tools built from the problems
that show up in production.

All projects

The portfolio is
part of the work.

A running system, from identity and private conversations to infrastructure and mail.

Explore the platform
Ataimo platform infrastructureGitHub source feeds Actions, Docker Hub images and Terraform, Ansible and Helm delivery. Greenfield provisions infrastructure; existing stacks receive app-only updates. Traffic progresses from external clients to Envoy Gateway, then a row of portfolio, Grafana, Keycloak, Redpanda Console and Mailu services, then PostgreSQL, Redpanda broker and Prometheus. These internal components run on one Azure VM with K3s. SMTP2GO is outside the VM, an external outbound port 25 workaround using TLS 587. SMTP and IMAP bypass HTTP ingress. Moving signals illustrate direction and are not live packet traces.ONE AZURE VMK3s · Helm · Docker containersINGRESSAPPLICATION SERVICESDATA · EVENTS · METRICSSMTP / IMAP · direct mail accessGitHub repositoryGitHub ActionsDocker HubTerraformAnsibleHelm + kubectlClientEnvoy GatewayPortfolio + workerGrafanaKeycloakRedpanda ConsoleMailu + webmailPostgreSQLRedpanda brokerPrometheusSMTP2GOEXTERNAL WORKAROUNDTLS 587 · outbound port 25 blockedNot hosted on the Azure VMcert-manager + Let’s Encrypt · Azure DNS · single node, no high availabilityGitHub → Actions → Docker Hub · fresh: Terraform + Ansible · existing: app-only Helm rolloutArrows show request, database, event and metrics-query direction. Prometheus scrapes the cluster independently.
Client → ingress → services → data · signals illustrate flow, not live traffic
Portfolio + workerapp

Next.js · consultation approvals · private chat · transactional outbox

One platform.
Connected by design.

Containerized Next.js on a single Azure VM, orchestrated with K3s and deployed through Helm. Envoy Gateway routes encrypted traffic; cert-manager manages Let’s Encrypt certificates through Azure DNS.

Explore the source on GitHub

GitHub Actions tests and publishes the app and worker to Docker Hub. Fresh deployments use Terraform for Azure and Ansible for K3s; existing deployments update only the application through Helm and kubectl.

Portfolio · HTTPS
ataimo.com
Identity · HTTPS
keycloak.ataimo.com
Dashboards · HTTPS
grafana.ataimo.com
Console · HTTPS
redpanda.ataimo.com
Webmail · HTTPS through Envoy
webmail.ataimo.com
Mail · SMTP / IMAP directly
mail.ataimo.com

Mailu adds webmail.ataimo.com and mailbox access through mail.ataimo.com. Outbound email travels through SMTP2GO over TLS on port 587 because Azure restricts outbound SMTP on port 25. Port 22 is SSH, not SMTP.

A window into the running system.

Public infrastructure measurements, collected from Prometheus.

Fetching measurements…

CPU utilization
Unavailable

Node usage · 5-minute average

Memory utilization
Unavailable

Used / total node memory

Running pods
Unavailable

Across the Kubernetes cluster

Node uptime
Unavailable

Time since the last node boot

Refreshes every 30 seconds; readings expire after two minutes. Infrastructure resource measurements only. Single node, no high availability.

The busiest workloads.

CPU is a 5-minute average; memory is the container working set. 1,000 mCPU = one CPU core.

View all pod measurements ↗

Fetching pod measurements…

See the whole system.
Solve the right problem.

Good engineering connects the technical detail to the people who depend on it.

Explore my expertise
  1. 01

    Understand the context

    Start with the customer, the constraints and the system as it actually runs.

  2. 02

    Trace the connections

    Follow requests across APIs, identity, infrastructure and data to find the root cause.

  3. 03

    Make change repeatable

    Turn the solution into a practical tool, a clear architecture or a dependable migration path.

Ataimo EdemATAIMO EDEM / LAGOS → GLOBAL

Engineering depth.
Human perspective.

I work at the intersection of enterprise customers, complex infrastructure and API platforms. My work combines hands-on engineering, architecture guidance, production troubleshooting and customer advocacy.

At Tyk, I support enterprise customers across EMEA — from architecture and implementation through upgrades, migrations and long-term platform evolution.

A difficult platform problem?
Let’s think it through.

LET’S TALK

Architecture reviews · API platforms · Cloud & Kubernetes