One system
One development appliance to operate.
Soda combines Fedora, curated development tools, private connectivity, SSH, project discovery, and Git into one opinionated development appliance.
Soda for teams
One development server for the team. A separate workspace for every developer.
Deploy Soda OS on cloud compute or server hardware your organization controls. The owner or technical lead chooses where it runs and who administers it. Each developer explicitly selects Set up for me for every project they need, creating a separate developer-project workspace.
- Cloud compute or server hardware
- Direct SSH through a private network
- Built-in or existing Git repositories
Cloud development serverShared foundationSoda OS
Alice · website
Alice · API
Bob · website
Why teams add Soda
Provide a shared foundation without prescribing every developer’s setup.
Put the operating system, curated development tools, project catalog, and shared compute in one place. Developers keep their preferred computers while the team shares one development foundation.
Shared resources
One place for the work that benefits.
Keep compute, project processes, databases, agents, and project services the team chooses to run on the Soda machine.
Developer freedom
Keep the tools at each developer’s desk.
Developers keep their editors, terminals, browsers, and local computers. Soda does not require remote desktop or a single client setup.
The team model
How one shared machine supports independent work.
Soda provides one shared development foundation without putting everyone in one working directory.
Layer 01
Shared foundation
The machine, operating-system image, system tools, compute, storage, private-network access, and project catalog.
Layer 02
Shared by a project
The repository reference and project services the team chooses to run on the machine.
Layer 03
Created per developer-project pair
A Linux workspace account, home, complete clone, dependencies, data, caches, and processes.
Soda is designed for a trusted team on a private network. Separate Linux accounts and developer-project workspaces reduce accidental interference; they are not a security boundary for hostile multitenancy.
From machine to workspace
A clear path from owner to developer.
Owner, administrator, and developer describe responsibilities, not necessarily different people. In a smaller team, one person may hold more than one role.
- 01
Choose the foundation
The owner or technical lead chooses the machine, private network, and administrators.
- 02
Prepare Soda
An administrator installs Soda, enrolls it in the Tailnet, creates Linux accounts, and operates image updates.
- 03
Add projects
The team creates a repository on Soda or connects one from its current Git host.
- 04
Set up a workspace
A developer selects Set up for me and receives a separate workspace, complete clone, and SSH command.
- 05
Develop with familiar tools
Editors, terminals, coding agents, SCP, and SFTP connect directly over OpenSSH. Git collaboration stays with the canonical host.
Familiar systems stay in charge
Soda joins the tools. It does not replace them.
The Soda OS dashboard makes projects discoverable on the machine. It does not replace repository permissions, branches, reviews, issues, or releases.
- Linux
- Accounts, groups, permissions, homes, files, and processes
- Tailscale
- Tailnet membership and private reachability when used
- OpenSSH
- Authentication and SSH sessions
- Cockpit
- General system administration
- bootc
- OS-image deployment and updates
- Canonical Git host
- Repositories, permissions, credentials, and collaboration
- Soda
- Appliance composition, project catalog, dashboard workflow, and workspace setup/removal conventions
Create a repository on Soda or connect one from its current Git host. Repository permissions and Git credentials remain with the canonical Git host and the developer’s ordinary Git setup.
Cloud deployment
Server and cloud
Put a development server within reach of the team.
Deploy Soda OS on Scaleway cloud compute or server hardware your organization controls. The organization operates the instance, private-network access, accounts, and updates; developers connect with their existing tools over SSH.