CPaaS stands for communications platform as a service. It is the label for buying messaging and voice as an API rather than building relationships with carriers and platform owners yourself.
The term is not defined by a published standard. The definitions in circulation come from analyst firms and from vendors, as part of market categories they maintain, so the boundary of what counts is drawn differently depending on who is drawing it, and several of those glossaries are not publicly readable. That is worth knowing before anyone tells you a product is or is not one.
What does the label actually name?
A specific piece of work you would otherwise do yourself.
Strip the vocabulary and the category describes a provider standing between you and the networks that deliver messages. Without one, sending SMS at scale means carrier contracts and connections in each market, number supply and its registration paperwork, per-country rules about what may be sent and by whom, and the operational apparatus to keep delivery working. With one, it means an HTTP request.
The same shape repeats per channel. WhatsApp and RCS have platform owners rather than carriers, and the work becomes approvals, template review and business verification, but the position is identical: somebody holds the relationship and exposes it as an API.
That is the durable content of the term. Everything else about it is positioning.
How would I evaluate one?
By what it absorbs rather than by what it is called, since the API is the easy part.
Five questions that separate providers, all checkable:
- Where does the number come from, and who registers it? Buying a number is easy. Getting it approved to send in a given country is the work, and a provider that hands that back to you has left the hard part with you.
- What happens when a channel changes its rules? Channel policies move. Whether that arrives as a platform change or as your incident is the difference.
- Is the failure detail useful? A delivery failure that says only "failed" cannot be acted on. One that names a cause can. Bird's SMS filtering page is an example of what that reporting looks like when it is honest about its own gaps.
- Is the interface documented as a contract? A published OpenAPI spec is a different commitment from a documentation site.
- Is pricing per country visible before you commit? Message pricing varies enormously by destination, and a provider whose rates you cannot see until you are a customer is telling you something.
Is CPaaS the same as omnichannel?
No. They are answers to different questions, and a product can be one without the other.
CPaaS is about who runs the telecom. Omnichannel is about whether your channels share state. A provider can expose six channels through one API while each keeps its own contact list and its own consent record, which satisfies the first and not the second. Omnichannel vs multichannel covers how to test the second claim.
The neighbouring acronyms, CCaaS and UCaaS, sit in the same vocabulary and describe contact-centre and internal-communications products rather than developer APIs. They share the "as a service" suffix and very little else.
Where does Bird stand on it?
Against the pricing model rather than against the capability, and it is worth reading the argument rather than the headline.
Bird has published a position under the title "The end of CPaaS", and the claim inside it is narrower and more specific than the title suggests. The argument is that messaging has commoditised, that margins on it are heading to zero, and that the pricing practices built on buyers being unable to compare rates across countries and carriers are what is ending:
On one side, they have been able to charge unnecessarily high fees because pricing is complex and it is difficult for buyers to monitor prices across all countries and carriers.
Nobody is arguing the underlying capability is going away. What is being argued is that selling it at an opaque margin is.
That is a position, not a definition, and this page keeps the two apart on purpose. The practical thing a buyer can take from it is the test in the previous section about visible per-country pricing, which is the same argument stated as something you can check. Bird's own rates are published per country on the pricing pages rather than quoted on request.