RAMIL.ORG Independent systems building and technical operations

AI-native systems builder & technical operator

I build systems that run without babysitting.

I turn messy operational workflows into reliable software — across infrastructure, APIs, internal tools, data platforms, automation, and AI.

Selected systems

Systems, not portfolio pieces.

Each case study starts with the operational problem — then shows how the system was made reliable enough to own.

01Selected system

AI-powered email infrastructure observability

MX Sentinel

A production operations layer that helps mail operators understand why delivery is failing — before the incident becomes a support queue.

Correlates SMTP telemetry, DNS changes, DMARC data, reputation signals, and incidents. Deterministic evidence comes first; AI assists with diagnosis.

GoEvent-drivenObservabilityAI diagnostics
Read case study
02Sanitized production architecture

AI-native business operations platform

Northstar

A sanitized demonstration of production architecture for turning fragmented commercial workflows into one accountable operating layer.

Connects research, qualification, AI drafting, human review, campaigns, client workflows, payments, reporting, and role-based operational visibility.

FastAPIPostgreSQL / pgvectorHuman reviewAudit trails
Read case study
03Selected system

AI video production engine

Video Automation Service (VAS)

A system that turns a topic or script into a finished video through an AI editorial layer and a deterministic rendering pipeline.

AI plans. Deterministic systems execute. Structured edit plans, workers, provider fallbacks, asset reuse, cost controls, and recovery make the pipeline operable.

FastAPIRemotionFFmpegWorker architecture
Read case study

How I work

Understand → Model → Build → Operate

The correct action should be the easiest action.

01

Understand

Map the actual business process before writing code.

02

Model

Define authoritative data, workflows, failure states, and human responsibilities.

03

Build

Use the simplest appropriate tool: application code, automation, AI, or infrastructure.

04

Operate

Deploy, monitor, recover, document, and improve.

AI should assist judgment, not replace authority where mistakes are expensive.

Architecture philosophy

Practical by design.

Good systems clarify what happens next — including when something fails.

01Deterministic core, probabilistic edge.

02Business state belongs in proper software, not prompt memory.

03Use AI where reasoning adds value.

04Use automation where the workflow is deterministic.

05Humans approve consequential decisions.

06Make failures visible and recoverable.

07Keep systems boring where boring is safer.

08Do not add another SaaS tool unless it solves a real problem.

Foundation

I came to AI from production systems, not the other way around.

I’ve spent 17+ years building and operating web and infrastructure systems: hosting, Linux, cPanel / WHM / WHMCS, migrations, and hundreds of production environments. That operational history shapes how I build AI-native platforms now.

View experience
17+years building and operating systems
100swebsites and production environments
NowAI and internal-platform work, grounded in operations

Technical range

Enough range to make good trade-offs.

I work across the seams where most internal systems become difficult.

Systems

Linux, Docker, networking, hosting, monitoring, deployment

Backend

Python, FastAPI, Go, Node.js, TypeScript

Data

PostgreSQL, Redis, ClickHouse, pgvector, SQL

AI

LLM APIs, tool calling, RAG, structured outputs, agents, human-in-the-loop systems

Operations

Queues, retries, idempotency, auditability, observability, failure recovery

Integration

REST APIs, webhooks, Gmail, Google Workspace, payments, CRM, third-party SaaS