CPaaS stands for communications platform as a service. It's a cloud provider that gives developers APIs for texts, calls, video and chat, so they don't build carrier connections themselves. For SMS, a CPaaS sells you the pipe: you write the code, handle registration and own the compliance.

The term is old enough that it means different things to different vendors. Some mean a raw messaging API, and some mean a full contact-center toolkit. The useful question isn't "is it CPaaS" but "how much of the work does it leave to me." For a buying framework, see how to choose a CPaaS SMS provider.

What a CPaaS usually gives you

  • Messaging APIs. Send and receive SMS and MMS, usually over REST.
  • Phone numbers. You can buy, port and manage them from the same account.
  • Delivery reports. Webhooks tell your code the status of each message as it changes.
  • Other channels. Voice, verification, sometimes chat apps and email.
  • Pay as you go. Per-message or per-minute pricing.

What it usually leaves to you

JobTypical CPaaSYou build
Carrier registrationOffers forms or an APICollect customer data, handle rejections
Consent recordsNot stored per contactYour database
Opt-out handlingBasic STOP at the number levelSync across channels and tenants
Quiet hoursOften noneTime zone logic
Per-customer isolationSub-accounts, with effortBilling and onboarding UI
Inbox and UINoneEverything customers see

That gap is why teams building a CRM or vertical SaaS often end up writing thousands of lines around a raw API. Build versus buy for SMS infrastructure walks through the tradeoff.

Where Ready sits

We make Ready, a messaging API and platform for software companies that text for their own customers. It's a thin, transparent layer over a messaging provider's carrier connections. Each customer gets a sub-account with its own numbers and registration, and Ready adds TCPA and Do Not Call scrubbing, number validation, opt-out handling, quiet hours and webhooks. Ready is narrower than a full CPaaS: SMS and iMessage, plus calling with the Ready Dialer. It isn't a video or chat toolkit. It isn't the right fit if you need many channels from one vendor. See why Ready isn't a Twilio wrapper.

Cost thinking

CPaaS prices look low per message, then add up with numbers, registration and compliance work. Ready charges $0.0075 per segment plus a $0.0045 carrier fee, with registration at $25 a month per customer and a number at $2 a month. Compare total cost to launch and run, including your own engineering time. The SMS API pricing guide helps.

Frequently asked questions

Is CPaaS the same as UCaaS? No. UCaaS is a finished business phone and meeting product. CPaaS is building blocks for developers.

Do I need a CPaaS to send texts? You need a connection to carriers, which a CPaaS or an aggregator provides.

Is an SMS API a CPaaS? An SMS API is one piece of a CPaaS, which usually bundles voice and other channels too. See what an SMS API is.

Next step

List the jobs in the table above that you'd rather not build, and test each vendor against that list.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.