Meridian

Communications platform · control plane

The operational layer for sending a message.

Meridian is not a REST wrapper. It is the tenant, inventory, routing, metering, compliance, and webhook fabric that a CPaaS actually runs on — with a native API and a Twilio compatibility gateway that translates, never clones.

Seeded tenant · Aether Logistics · prepaid · il-central

Shared control plane

Org → billing account → project / subaccount → resource. Credentials, inventory, quotas, routing policy.

Independent data planes

Messaging, Voice/SIP, Verify. Separate lifecycles. Same tenant and meter.

Least-cost routing

Score = wq·Q − wc·Ĉ − wl·L − wf·F + wp·P. Direct + aggregator paths per market.

Translation gateway

Parser → canonical command → native service → serializer. /2010-04-01 is a skin.

MVP surface

What the first market has to ship.

Video, Conversations, Email, and Fax stay out of scope. Everything below is live in this console as an operational simulation — SIDs, DLR, usage events, and all.

  • SMS lifecycle + GSM/UCS-2
  • Messaging Services + sticky sender
  • Phone numbers + porting
  • Voice Call / Call Leg + TwiML
  • SIP trunks, CPS, IP ACL
  • Verify as orchestration
  • Webhooks HMAC + X-Twilio-Signature
  • Usage → rate → invoice
  • Prepaid / postpaid limits
  • Regulatory bundles
  • Fraud velocity + geo
  • Sandbox virtual carrier

Aether Logistics is already on it.

Three projects, Israeli and US numbers, Partner / Cellcom / Bandwidth routes, a Hebrew UCS-2 dispatch, and a STOP on the inbound desk.

Enter dispatch-prod