Software Engineer · Technical Founder · Systems & Product Builder

I build software companies, platforms, and the infrastructure underneath them.

I'm the CTO & Co-Founder of Ruut, where we're building an AI-native communications and business platform spanning customer engagement, programmable voice, messaging, email, marketing automation, CRM, and AI agents.

I'm also building Inkwell — a from-scratch rethink of what WordPress might look like if it were designed today.

Over the last 12+ years, I've worked across fintech, SaaS, communications, embedded systems, IoT, infrastructure, and consumer products.

These days, I'm especially interested in AI agents, programmable communications, developer infrastructure, identity, modern publishing systems, and products that require going several layers beneath the API.

Ruut is an AI-native communications and business platform for modern teams.

We're building infrastructure and products around:

• 💬 Omnichannel customer communication
• ☎️ Programmable voice and CPaaS
• 🤖 AI agents for support, sales, and operations
• 📧 Email and SMTP infrastructure
• 📣 WhatsApp, SMS, and email marketing
• 🧠 CRM, workflows, and automation
• 🔐 Identity and authentication infrastructure
• 🔌 Agent-to-system integrations and tooling

Ruut has processed 10M+ customer messages, powered 500K+ conversations, and served businesses with cumulative contact bases exceeding 1M contacts.

We've been building it from the ground up — bootstrapped, revenue-generating, and used by businesses in production.

Inkwell is my answer to a simple question:

What if WordPress were rebuilt from scratch today?

Not redesigned.

Rebuilt.

Inkwell is a modern CMS and publishing platform built around a Rails-native architecture:

Ruby on Rails
Hotwire
Turbo
Stimulus
Tailwind CSS
ViewComponent

The architecture rethinks several assumptions inherited from traditional CMS platforms.

Instead of shortcode-heavy content, Inkwell uses structured blocks.

Instead of loosely defined extension points, it uses a typed hook system.

Instead of bolting plugins onto the side, plugins are designed as Rails Engines.

Instead of treating themes as giant bundles of logic, themes are built around view paths and presentation primitives.

The goal is not to create "WordPress in Rails."

The goal is to rethink what a flexible, extensible publishing system should look like with modern application architecture.

Some of the areas I'm actively exploring include:

• Block-based content architecture
• Plugin systems
• Theme architecture
• Runtime extensibility
• Modern admin UX
• Publishing workflows
• Developer-friendly hooks and APIs
• CMS performance
• Hotwire-first interfaces
• Rails as an application platform

Inkwell sits at the intersection of product design, framework architecture, extensibility, and publishing infrastructure.

One area I've gone particularly deep into is telecommunications.

I'm building Ruut Voice, our programmable communications infrastructure for developers and AI agents.

That work involves:

PSTN
SIP
FreeSWITCH
Kamailio
WebRTC
CPaaS
SIP Trunking
Call Routing
Media Streams
Voice AI
AI Agents
MCP

I'm fascinated by the idea that an AI agent should be able to make a phone call, navigate a phone system, speak to a human, transfer calls, receive events, and take actions as naturally as it calls an HTTP API.

An open-source exploration of what a modern Heroku / Railway-style PaaS can look like when built around Dokku, Rails, containers, and modern infrastructure primitives.

An exploration of identity as infrastructure.

The idea combines:

• SSO
• OAuth / OIDC
• Passkeys
• Credential management
• Cross-device identity
• Agent-assisted authentication

The broader question is:

What should identity look like when both humans and AI agents need to authenticate into software?

I care more about systems than stacks, but you'll regularly find me working with:

Languages

Ruby · TypeScript · JavaScript · Go · Python · PHP

Backend & Application Architecture

Ruby on Rails · Node.js · PostgreSQL · Redis · Sidekiq · Hotwire · Turbo · Stimulus · ViewComponent

Infrastructure

Docker · Linux · Traefik · Dokku · Proxmox · AWS · GCP · Cloudflare

Telecommunications

FreeSWITCH · Kamailio · SIP · WebRTC · PSTN

AI

LLMs · AI Agents · MCP · Voice AI · ASR/TTS · Multimodal Systems · Local Inference

Hardware

ESP32 · Arduino · Embedded Systems · IoT

Right now, I'm spending a lot of time thinking about:

• AI agents that can actually do things
• Voice as an interface for AI
• Agent ↔ human communication
• Agent ↔ agent communication
• Programmable telecommunications
• Modern CMS architecture
• Plugin and extension systems
• Publishing infrastructure
• Local and open-source AI
• Multimodal systems
• Developer tooling
• Authentication and digital identity
• PaaS and deployment infrastructure
• Rails as a platform for ambitious software
• Building deep infrastructure rather than stopping at third-party abstractions

I enjoy going several layers beneath the API.

If something interesting looks like magic, my first instinct is usually to figure out how it works — and occasionally build my own version.

I like working across the entire stack:

Idea
  ↓
Product
  ↓
Interface
  ↓
Application
  ↓
Framework
  ↓
Infrastructure
  ↓
Protocol

I've worked on everything from product interfaces and Rails applications to payment systems, publishing platforms, distributed infrastructure, SIP routing, AI systems, and embedded hardware.

For me, engineering isn't just writing code.

It's understanding enough of the system to make the right trade-offs — and knowing when the existing abstraction should be replaced entirely.

I'm interested in collaborating on ambitious projects around:

AI infrastructure · developer tools · telecommunications · Rails · CMS architecture · distributed systems · identity · open-source AI

If you're building something technically difficult or slightly unreasonable, we'll probably have something to talk about.

LinkedIn: https://ng.linkedin.com/in/ezeani-emmanuel Email: monaoffice20@gmail.com Ruut: https://ruut.chat

I'm still the kind of engineer who can disappear down a rabbit hole because I wanted to understand why something works.

The only difference now is that the rabbit holes occasionally turn into products, platforms, and companies.