ProjectCommunications Infrastructure · 2026
Telephony
A provider-agnostic NestJS backend for SMS, voice, verification, lookup, phone numbers and A2P 10DLC. Product code talks to a capability, not a vendor SDK.
- NestJS
- TypeScript
- Twilio
- REST APIs
Communications Infrastructure · Project
Overview
Telephony provides one application-facing API over communications providers.
Capability-based API
SMS, voice, Verify, Lookup, phone numbers, messaging services, and conversations each have a provider-neutral interface and controller. Product code talks to a capability instead of importing a provider SDK directly.
Runtime Provider Selection
Environment variables choose the provider independently for each capability. A registry resolves that choice at request time, which means one deployment can route SMS and voice through different providers without changing the public controller layer.
Full Twilio Coverage
Twilio is the first complete adapter and also retains provider-specific routes for A2P 10DLC, TaskRouter, TrustHub, Studio, Proxy, Fax, short codes, subaccounts, credentials, recordings, usage, and webhooks.
Extension Path
Vonage, Plivo, and MessageBird modules define the next adapters as explicit stubs. Adding a provider means implementing selected capability interfaces and registering them, while existing routes and product workflows remain unchanged.
Next projectInfrastructure