Cap'n Proto isn't really the magic that makes everything work, it's just a communications layer that is designed to facilitate Sandstorm's security model -- nam

Cap'n Proto isn't really the magic that makes everything work, it's just a communications layer that is designed to facilitate Sandstorm's security model -- namely, Capability-Based Security. Here's some relevant links: https://sandstorm.io/how-it-works#capabilities https://sandstorm.io/how-it-works#capabilities https://sandstorm.io/news/2014-12-15-capnproto-0.5 https://sandstorm.io/news/2014-12-15-capnproto-0.5 Note that Sandstorm does not require that apps store their data in Cap'n Proto format. Rather, the app communicates to the outside world via Cap'n Proto. Also note that many other protocols -- especially HTTP -- can be layered on top of Cap'n Proto, allowing apps that don't know anything about Cap'n Proto to operate. Here's how HTTP-over-Cap'n-Proto is defined, BTW: https://github.com/sandstorm-io/sandstorm/blob/master/src/sandstorm/web-session.capnp https://github.com/sandstorm-io/sandstorm/blob/master/src/sa... The key advantage of using Cap'n Proto is that it allows Sandstorm to be aware of all of the connections that exist between apps, so that it can tell the user which apps are talking to which other apps and how those apps discovered each other, and give them the opportunity to revoke those connections.