Source available: read it, check it.
Vando’s code will be public, so anyone can read it and check what it does. The code isn’t public yet. It’s coming soon, and this page will link to it.
It is released under the Functional Source License (FSL-1.1-ALv2). That is a source available licence. It is not an open source licence as the Open Source Initiative defines one, and we won’t call it that. This page says what it lets you do.
Coming soon: the repository opens at launch.
What is in it.
The parts you run, and the writing that says how they should behave.
- The apps and the command line.The phone apps, the laptop extension and the
vandocommand for your computer. - The server.The part that holds the scrambled copy and passes your asks along.
- The crypto package.The code that locks and signs things on your devices.
- The specs.The documents that define the system: the crypto, the policy engine, the protection model, the attacker matrix and the decisions we have settled.
The licence, in plain words.
This is a summary, not the licence. If the two ever differ, the licence text wins.
- You may read, audit, build, change and run it.For yourself, inside your own organisation, for teaching and for research. Any purpose is allowed except the competing use below.
- You may not compete with it.You can’t offer Vando, or something substantially like it, as a product or service that competes with ours.
- It becomes Apache 2.0 after two years.Each release turns into Apache 2.0 two years after it is published. After that, the usual Apache 2.0 freedoms apply to that release.
- Some parts are freer already.The crypto package is Apache 2.0 from the start, and the test vectors are CC0, which means no rights reserved.
- The name stays ours.The name Vando, the logo and our domains are trademarks. A fork has to use a different name.
- Self-hosting isn’t supported.You can read and build the server. We don’t offer help running your own, and the apps are made to talk to ours.
How to check what you install, and what you can’t.
Better you hear the limits from us.
- Tests that check our claims.The repository will carry tests for what we say: the attacker matrix, the test vectors and the canary tests. You can run them yourself.
- Rebuilding an app from the source isn’t ready.Builds that you can reproduce byte for byte are not available yet. We are working on them, and we won’t claim them until they exist.
- iPhone builds can’t be reproduced.Apple’s process for the App Store doesn’t allow it, so for the iPhone app you rely on reading the code and on Apple’s checks.
- Public code doesn’t prove what our servers run.You can read the server’s code, but you can’t see which version is running. That’s why your devices sign every yes and check each other’s, instead of trusting the server. How it keeps you safe →
Found a security problem?
Write to security@getvando.com. Please don’t open a public issue, so we can fix it before anyone can use it against other people.