← Back to portfoliothe systems

What I actually work on

Nine services I designed, and still answer for.

If you don't write software, here's the honest summary: when a large company needs to reach a few hundred thousand customers by call, SMS or WhatsApp, something has to decide who gets contacted, on which channel, how fast, and then prove it happened. This is that something.

For everyone else: inbound feeds, a core orchestrator, egress gateways and a realtime agent runtime. Pick a node — each one is something I designed, bootstrapped or own end to end.

IngressCoreEgressAgent runtimeTenant isolatedclick a node
Allocation & Payment Ingestwebhook-ingestCallback Multiplexerdlr-multiplexerOrchestration Enginecomm-coreShared Contract Layercommon-dtosCRM Translation Gatewaywebhook-egressLink Tracking Servicelink-trackerRealtime Agent Simulatoragent-simulatorVoice & Text Agent Runtimeagent-runtimeIsolated Tenant Processortenant-callbacks
Core

Orchestration Engine

comm-core

The monolith that owns campaign execution, communication batching, context assembly and analytics export. Every outbound call, SMS and WhatsApp message starts or ends here.

  • A batch handler with channel-wise multiplexing and a dual-path pipeline: a fast path for single ad-hoc triggers, a batch path for everything else.
  • A throttled executor that splits huge trigger arrays into staggered sub-batches sized to each vendor's TPS ceiling.
  • Batch lifecycle APIs — status reporting without N+1, atomic cancellation under row-level locks, and redial that copies only retryable triggers into a new batch with clean lineage.
  • Context layer refactor: a single read facade, side-effect-free builders, and ORM models that never cross the API wire.