The project

About Soda OS

Software should keep fitting the business that uses it. Soda OS helps companies build and keep improving software around their own workflows, with AI coding agents, persistent Projects and review on infrastructure they operate.

Illustrative company operating model

How the work stays with your company
DepartmentOwn the requirementsDefine the rules · accept the result
IT + developersOperate and interveneInfrastructure · accounts · policy · preferred tools
Company-operated infrastructureSoda OS

AI development → review → continuing improvement

Persistent ProjectsRepository collaboration

Software that keeps fitting your work.Requests · approvals · onboarding · beyond

Company responsibilities and lasting development infrastructure.

For departments and IT together

Departments own business requirements and acceptance. IT operates the shared factory, accounts and policies; developers can intervene with their preferred tools. Start with internal requests, approvals or onboarding, while retaining broader repository and development use.

Explore examples

A company-operated software factory

Soda coordinates authorised development and review. Your company chooses its infrastructure and operating responsibilities. CanLang supplies optional business foundations and can also be used independently.

Explore the platform

Public maintainer

The public maintainer.

Public maintainer: @vinchdev on X/Twitter.

Find the maintainer on X/Twitter @vinchdevSoda OS source on GitHub Source code, issues and releases

Source and licenses

The projects behind Soda OS.

Open source projects with their own purpose, source and license scope.

One factory, distinct projects.Each source retains its own license scope.

Soda’s NOTICE on GitHub distinguishes inherited and third-party material; bundled components retain their own terms. Its Fountain source manifest on GitHub identifies the maintained fork. These identifiers describe source-license scope; applications and other distribution components retain their applicable terms.

Inspect the work

Source, releases and documentation.

Inspect the source, releases and on-site handbooks.

Questions and problems

Get help.

Start with the guide for your task. For a project question, bug report or suggestion, use the relevant GitHub issue tracker. If you use a company installation, your operator handles its access and operation.

Illustrative help routes

Choose the owner of the question.
Public projectFactory problem → Soda OSLanguage problem → CanLangRead the handbook, then report a reproducible issue.

Find the person or project responsible for your question.

Company access

Contact your company’s operator or application owner for installation access and account permissions.

Read connection guidance
Soda setup and factory work

Installation, Projects, coordinated work and recovery.

Soda handbook Soda OS issues on GitHub
CanLang

Installation, diagnostics and language behavior.

CanLang handbook CanLang issues on GitHub
Your app’s business rules

Start with your department’s workflow owner and developer or operator. A reproducible platform or language defect belongs in that product’s tracker.

Documentation or product suggestions

Use the relevant product tracker above, with the page link or workflow context.

GitHub issues are public. Include product/release, route or platform, steps, expected and actual results, and a small redacted diagnostic. Keep credentials, private backups, raw environment dumps and confidential company records out of public reports. How to report a useful problem.

Help us learn

Tell us about your workflow.

Share an anonymised description in the relevant public product tracker, using these three questions.

  1. 01

    What were you trying to build?

    Describe the workflow, its users and the outcome you needed, without company records.

  2. 02

    Which step did you reach?

    Explain what worked, where you stopped and the smallest redacted example of the problem.

  3. 03

    What would make the next attempt useful?

    Name the information, example or product behavior that would help you continue.

Soda OS issues on GitHub CanLang issues on GitHub

Feedback is not automatically a testimonial. Publishing a person’s identity, company name, quote or case study requires separate permission.

Website measurement

Website visits and actions are separate from installation or company adoption.

Collection is disabled on this website. It loads no analytics provider. The configured collection, when activated separately, is hosted Plausible page reporting and five explicit actions: setup choices, ISO download clicks, successful installer copies, first-use instruction links and help links. It excludes entered text, source code, credentials, private hostnames and persistent company or user identifiers. It introduces no telemetry in self-hosted factories or created applications.