How does Caffeine work?

Caffeine is a new internet protocol for app network traffic. We've taken HTTP, TLS, and TCP, and re-engineered them into a tightly integrated and faster networking stack.

We send the same data you do today, just with less overhead. So if you're already doing compression and image size reduction, our technology can take you beyond the best practices.

Internet protocols don't innovate because they need interoperability with Netscape Navigator. But if your app is talking to your backend, you don't have to choose a legacy protocol. You can choose one that delivers a better experience for your users.

Our tooling provides seamless translation between Caffeine and legacy protocols, so your existing network code is just a 15-minute upgrade, and you can adopt Caffeine when and where it makes the most sense for your users.


Typical iOS Networking stack

Client

HTTP

TLS

TCP

IP

Caffeine networking stack

Client

Caffeine

TCP

IP


Legacy protocols were designed by committee over many decades to handle all the usecases on the internet: dial-up, broadband, and cellular. VoIP, broadcast, and web. LAN, datacenter, and WAN. IE, Chrome, and FireFox. So many usecases force these protocols to be a jack of all trades, but a master of none.

Caffeine is a vertically integrated protocol, narrowly focused on app developers. We cut away the legacy that app developers don't use, and we eliminate the redundancies between protocol layers that were designed separately years ago. We add techniques known for years in real-time audio processing and high-frequency trading to move data faster.

The result is a streamlined protocol where no byte is wasted. And a fresher and more engaging experience for your users.

Security

Apps are faced with an unfortunate choice: do I use HTTPS to keep my data secure, or do I use plaintext for superior performance?

Caffeine provides strong security without the performance cost. Based on the trusted security technology of NaCl, Caffeine provides all the guarantees of traditional HTTPS traffic, and quite a few more – like PFS, and certificate pinning – out of the box, without the performance overhead.