Media kit

A printable one-pager, and copy-ready bios.

Everything on this page is designed to be printed to PDF or copied straight into a profile. Nothing here is marketing copy — it is the same record as the evidence hub, in a shape that fits a form.

Full evidence hub

Omeiza Okuta

Open Source Architect & Platform Engineer

okuta.omeiza@gmail.com
United Kingdom — working remotely across EU / UK time zones

Open Source Architect building light, sustainable developer infrastructure and local-first CI/CD automation.

Products

  • CI Kit — Run your CI on your laptop, before you push.
    99 s on a 2022 intel laptop, against 43–48 s on a runner
  • api-mock-services — Stand-ins for the outside world.
    50–51 MB every mock running, one process
  • Automation Gateway — Air-gapped workflow execution as declarative JSON, with an audit trail that stays on the host.
    0 ships as a folder — no package manager

Recognition

  • CI Kit — run your CI on your laptop, before you push — GitHub, 2026
  • api-mock-services — stand-ins for the outside world — GitHub, 2026
  • Published documentation sites for both projects — GitHub Pages, 2026
  • The Silent Bill: How Remote CI/CD Drift Destroys Startup Engineering Momentum — Substack / Dev.to, 2026-09-18
  • Architecting Local Sandboxes for Interswitch and Paystack Integrations, Completely Offline — Substack / Dev.to, 2026-08-27
  • The earlier body of published work, 2013–2025 — TechLiaison, 2013–2025

Writing

Links

  • GitHub — https://github.com/omeiza-workspace
  • LinkedIn — https://www.linkedin.com/in/omeiza-okuta

Open to platform engineering and developer infrastructure work — Available for contract, fractional and permanent roles in platform engineering, developer experience and infrastructure tooling. Also available to speak and to review infrastructure work.

Full evidence: https://omeiza-workspace.github.io/evidence/

Copy-ready

Unified bios for every channel

The same narrative, four lengths. Use the one that fits the field you are filling in.

One line — X bio, GitHub profile

Open Source Architect building light, sustainable developer infrastructure and local-first CI/CD automation.

Short — 160 characters, LinkedIn headline or X

Open Source Architect. Creator of CI Kit, api-mock-services and an air-gapped automation engine — a local CI gate, a dependency-free mock engine for payment APIs, and declarative workflow execution with an audit trail. I publish how every number was measured, including the ones I threw away.

LinkedIn about section

Open Source Architect building light, sustainable developer infrastructure and local-first CI/CD automation. Creator of CI Kit, api-mock-services and an air-gapped automation engine. I write about DX, CI/CD drift, air-gapped systems and reproducible measurement — and publish what I do not claim.

X / short-form bio

Open Source Architect. CI Kit, api-mock-services and an air-gapped automation engine. Deterministic CI gates, dependency-free mocks for payment APIs, declarative workflow execution — and every number published with how it was measured.

Long — portfolio, conference bios and speaker profiles

I am an Open Source Architect and platform engineer working between the UK and West Africa. My work is in the unglamorous layer of infrastructure: the tools that decide whether a team waits forty seconds or forty minutes for a green build, and the services that keep an enterprise running when the network does not. I build three open-source projects. CI Kit gives a repository a local gate that runs the same scripts its GitHub Actions workflow runs. It came out of an incident worth being honest about: 28 of the last 30 runs in a workspace had failed, and not one of them had failed on code — GitHub had been refusing to start the jobs over a spending limit, every run failing in about six seconds. Nobody could tell the difference between a red build and a build that never ran. The local gate answers the same question in about a hundred seconds, and it says why. I measured the honest version too: on identical work it takes 99 seconds on a laptop against 43–48 seconds on a GitHub runner. It is not faster. It is a guarantee of feedback, and the evidence document has a section on what is not claimed. api-mock-services is one dependency-free Node process that stands in for eighteen third-party providers — Stripe, Paystack, Interswitch, Flutterwave, Monnify, YouVerify, Smile ID, Twilio, Resend, Xero and the rest. It replaced four containers: 50 MB against 250 MB, 0.0% idle CPU against 7.9%, and 1.4 seconds to the first request against 20 and rising. The footprint is a build gate, not a README claim — the build fails above 100 MB. The Automation Gateway is an air-gapped Windows Service that runs enterprise workflows from JSON blueprints instead of controller code, with plug-in auto-discovery, RBAC, feature toggles for break-glass recovery, and every step attempt written to a transactional SQLite audit trail. Zero external dependencies, no build step, and a defined fallback when a component is unreachable. All three are permissively licensed, all publish their evidence, and all ship the harness that produced the numbers. I write long-form essays on CI/CD drift, offline-first integration testing and reproducible measurement, cross-posted to Substack and Dev.to, and I keep a public archive of everything I have written since 2013.

LinkedIn headline

Creator of CI Kit, api-mock-services & the Automation Gateway | Specializing in Developer Experience (DX), Local-First Infrastructure, and Air-Gapped Platform Engineering.

LinkedIn

What to pin in the Featured section

Three items, in this order. A recruiter who clicks one lands on a different part of the argument each time.

Content loop

Weekly posting calendar

Every post leads with a technical problem, carries the evidence, and points at the repository. Never a bare link.

Week 1 LinkedIn The origin story, with the evidence

The pipeline went red because the bill was due

“Twenty-eight builds in a row failed. Not one of them failed on code.”

On 21 October we used the last of our 2,000 included GitHub Actions minutes, with eleven days left in the cycle. Every job from that point either cost money per minute or did not start at all. The largest repository in the workspace had 28 failing runs out of the last 30, all of them in about six seconds, all of them with the same annotation: the job was not started because the spending limit needed increasing. It looked exactly like a broken build. It was an empty account. CI Kit is the answer: the checks that do not need a shared machine now run on the developer's own laptop, in about a hundred seconds, for nothing.

CTA: The full write-up, with the annotation and the numbers, is on my site. Link in the comments.

Week 2 LinkedIn Problem → evidence → CTA

A red build is not always a red build

“Our pipeline was red for a week. Not one of those 28 failures was a code failure — the jobs never started.”

GitHub had refused to start the jobs because of a spending limit. Every run failed in about six seconds. At the pull request level a red build is a red build, so the week looked like ordinary breakage. What I built to find out what was actually happening is now open source, and I wrote up the incident — including the measurement I threw away.

CTA: The full write-up, with the numbers and the harness, is on my site. Link in the comments.

Week 3 X Terminal screenshot + one number

Benchmark release

“Idle CPU, four mock containers vs one dependency-free process:”

7.9% → 0.0%. Memory 250 MB → 50 MB. First request 20 s and rising → 1.4 s. Same mocks, one process, no dependencies. The footprint is a build gate now — the build fails above 100 MB, so the number cannot quietly stop being true.

CTA: Open source: github.com/omeiza-workspace/api-mock-services

Week 4 LinkedIn Architecture breakdown + directory-tree image

Business logic as data, on a host with no internet

“Here is the layout of an air-gapped automation engine that runs enterprise workflows from JSON instead of controller code.”

The engine core is immutable and lives in its own module scope. Workflows are pure JSON, so a business rule changes by editing a file rather than by shipping a deploy. New integrations are *.plugin.ps1 files that get auto-discovered — the core is never edited to add one. Every step attempt, including retries, is written to SQLite so an auditor can trace a self-healed run. Zero external dependencies, no build step, no internet in the request path.

CTA: The full architecture write-up, with the layout and the design decisions, is on my site.

Week 5 X Milestone + thanks

Repository milestone

“CI Kit just crossed [N] stars.”

Started this because I watched a team fail 28 builds in a row without anyone noticing the jobs had never run. Thank you to everyone who has filed an issue — particularly the ones that told me the toolchain check was hiding a class of real failures. Open to issues and PRs.

CTA: github.com/omeiza-workspace/ci-kit

Cross-pollination

How the channels link to each other

Every channel points to every other channel. A visitor should be able to arrive from any one of them and reach the whole set within a single click.