The CPaaS Company
Insights
Independent, source-cited writing on cloud communications — original research alongside the best work published elsewhere.
11 pieces
Consent is a data model, not a checkbox
A boolean cannot answer the question a regulator asks, and cannot answer the question your own send path needs answered either.
The five layers of a communications stack, and which one you are actually shopping for
Most evaluations compare transport, which is the commodity layer. The four above it are where programmes succeed or fail.
Video without a vendor: what peer-to-peer actually removes
For small calls, the media server is optional. Understanding when it stops being optional is the whole decision.
WebRTC in plain terms
What the browser gives you for free, what it does not, and the three acronyms you cannot avoid.
Choosing a channel per message, not per programme
The channel decision belongs at send time, driven by intent, region and what consent you hold — not to a procurement meeting eighteen months earlier.
When to build messaging infrastructure, and when not to
A decision framework based on what actually breaks in production, rather than on a feature comparison.
Latency you can actually feel
The network is rarely the slow part. Template approval, queueing and carrier acceptance dominate wall-clock time, and only one of them is under your control.
The support queue as a system, not an inbox
Routing rules, service-level targets and the distinction between first response and resolution — the machinery that separates a support function from a shared mailbox.
A consent architecture that survives an audit and a vendor migration
A schema, a set of invariants, and the three queries every send path and every regulator eventually asks.
Federating systems without merging them
When several products serve genuinely different audiences, consolidation destroys the thing that made each one good. Published contracts do the same job without the loss.
The gap nobody fills: service-to-service identity
Every platform in this category issues credentials to humans and to applications. Almost none can express 'system A is acting on behalf of customer B, with these permissions, until this moment'.