Spring Voyage - A CVOYA project

Spring Voyage is now open source. Read the launch announcement — The boat is in the water.

About

Spring Voyage is developed by CVOYA and led by Savas Parastatidis. For news, examples, and the wider project, visit spring.voyage.

Introduction

Spring Voyage is an open-source human–AI agent collaboration platform. Humans and agents work together toward a goal in a domain, as members of the same team, each with their own roles, responsibilities, and expertise. Agents organize into composable units, connect to external systems through pluggable connectors, and communicate via messages.

The platform does not orchestrate. It prescribes no workflows and no fixed way of working — how a team communicates, collaborates, and organizes is left to the instructions its agents are given. What the platform provides instead are the building blocks teams need:

• Communication primitives for interactions and conversations.
• Memory tools that keep a per-engagement history of interactions (between two or more participants).
• Directory tools for discovering members, roles, and expertise.
• Isolated execution environment for agent runtimes — which can use domain-specific tools and, if necessary, host their own orchestration frameworks: LangGraph, Microsoft Agent Framework, CrewAI, Google ADK, OpenAI Agents SDK, Ruflo, Gas Town, and more.
• Policy management for team behavior — interaction boundary enforcement, work projection/summarization via a team leader, and more (still in progress).
• Connectors for integration with external systems (currently GitHub and Slack).
• CLI and web portal for managing the platform, configuring agent teams, monitoring budgets, and gaining insight into team operations and engagements.

Install

Spring Voyage runs on Linux or macOS with Podman 4+.

curl -fSL https://github.com/cvoya-com/spring-voyage/releases/latest/download/install.sh | bash

Two prompts: DEPLOY_HOSTNAME (default localhost) and an optional GitHub App registration — press Enter to accept both defaults. When it finishes, open http://localhost and the portal guides you through the rest.

For flags, TLS, troubleshooting, and updates see the operator deployment guide.

Getting Started

After installing, open the portal at http://localhost — the new-unit wizard walks you through everything, including LLM credentials, GitHub or Slack integration, and other configuration. No CLI required to get going.

When you want to go deeper:

• Your first unit and agent — the same flow from the spring CLI: create a unit, send it a message, add an agent member.
• Spring Voyage OSS — a ready-made dev team — install the built-in spring-voyage-oss package: a unit with engineer and program-manager agents that pick up work from a GitHub repository.

Operating Spring Voyage

Day-2 operations — status, logs, restart, updates, and uninstall — run through the voyage wrapper that the installer puts on your PATH (start with voyage status). The operator deployment guide covers the full command set plus TLS, multi-host topology, secrets rotation, updates, and troubleshooting; the three-tier secret model (platform / tenant / unit) is documented in Secrets.

Documentation

• Getting Started — first unit, first message
• Spring Voyage OSS quickstart — install the built-in dev-team package
• Operator guide — install, configure, day-2 ops, secrets, troubleshooting
• User guide — spring CLI and web portal
• Concepts — units, agents, connectors, messages, skills
• Architecture — how the concepts are realised as a running system
• Releases & container images — versioning plus the canonical list of published GHCR images and their tags
• Bring your own agent image — ship a custom agent CLI on the published base image (ADR-0027)
• Documentation index — everything

Project Status

Spring Voyage is in alpha and in active development. Pull Requests are welcomed and encouraged. A lot of functionality is already in place:

• Infrastructure — container-based hosting, an actor concurrency model, reliable message delivery, and more.
• Functionality — create teams of agents, compose the system prompt given to them, MCP tools for message-based communication, directory services, engagement-scoped memory access, and more.
• CLI and web portal — user interfaces to manage teams of agents and engage with them.
• Connectors — GitHub and Slack (personal workspace) integration.

Forward-looking work and live progress — what's in flight, what's queued — live on the GitHub milestones and in issues across cvoya-com/spring-voyage.

Open Core Model

Spring Voyage follows an open-core model. This repository is the complete, fully functional platform — agents, units, messaging and routing, connectors, the package system (including the built-in spring-voyage-oss package), CLI, web portal, A2A, ephemeral cloning, observability, and basic cost tracking — with the multi-tenancy infrastructure included and configured as a single-operator identity model.

Commercial extensions (multi-user sign-in, OAuth/SSO/SAML, cloud-style tenant provisioning, billing, and advanced features) are developed separately and are not part of this repository.

Security

Found a vulnerability? Please follow the responsible-disclosure process in SECURITY.md — do not open a public GitHub issue for security reports.

Contributing

Contributions welcome. Please read:

• CONTRIBUTING.md — development workflow and CLA
• docs/developer/setup.md — prerequisites, building, running locally
• CONVENTIONS.md — coding patterns (mandatory)
• CODE_OF_CONDUCT.md — community standards

To build the platform from source or hack on it locally:

git clone https://github.com/cvoya-com/spring-voyage
cd spring-voyage

Host prerequisites (.NET 10 SDK, Podman, Dapr CLI; optional Node.js / Python — everything else runs in containers) and the local-dev loop are in docs/developer/setup.md. Architecture, project layout, and where to put new code are in docs/developer/overview.md. Operators do not need to clone the repository; the installer is the supported install path.

License

Spring Voyage is licensed under the Business Source License 1.1.

What this means:

• Free to use for personal projects, development, testing, and internal non-production use
• Free for production except for offering it as a competing managed AI agent collaboration service
• Converts to Apache 2.0 on 2030-04-10 (four years from initial release)

See LICENSE for the full terms and NOTICE for third-party attributions.