Spring Voyage is source-available under BSL 1.1 and converts to Apache 2.0 in 2030. You run it yourself — there is no hosted service, and we are not going to pretend otherwise.
Spring Voyage is source-available.
Read the source. Modify it. Redistribute it. Run it in production — including commercially, inside your own company, on your own infrastructure, for your own work.
This is a broader grant than most people expect from a non-OSI licence. For the overwhelming majority of users there is no practical restriction at all.
Offer Spring Voyage to third parties as a competing managed agent-collaboration service — that is, a service that lets other people create, manage, and run teams of AI agents using Spring Voyage as its core.
That is the entire restriction. It exists so that the company that builds the platform is the one that gets to run it as a service.
On 10 April 2030, the licence converts to the Apache License 2.0 and the restriction disappears. At that point Spring Voyage is open source in the full sense — and that conversion is written into the licence itself, not a promise in a blog post.
There is exactly one way to run Spring Voyage today: yourself. That path is real and supported.
$ curl -fSL https://github.com/cvoya-com/spring-voyage/releases/latest/download/install.sh | bashLinux (x64, arm64), macOS (Intel, Apple silicon), and Windows x64, with checksums.
Cvoya.Spring.Cli, published by CVOYA.
One VPS or a cluster. Your database, your secrets, your agent runtime. Nothing phones home.
Spring Voyage Cloud is not in development. There is no waitlist, no beta, and no pricing — because there is nothing to price.
If enough people want a hosted service, we will build one. If that is you, tell us what you would need it to do: info@cvoya.com or the discussion board.