Hosted
Per workspace, monthly
We run the control plane, managed runners, storage and upgrades. You bring the team and the feature requests.
- Managed runners
- Upgrades and backups
- Support from the people who built it
The SDLC, as software
A state-driven delivery platform that carries a feature request through governed states to a verified release. Agents do the work, people hold the gates, and the record is the truth.
Hosted or self-hosted- backlog feature_request
- design prd
- design approval design_package
- development implementation_package
- automated qa qa_report
- manual review review_report
- ready release_candidate
- released
State is the truth.
Artifacts are the record.
Feature request → Artifact → Workflow run → Transition → Job → Runner → Output artifact → Next transition
Every feature request becomes an artifact. A workflow run carries it through governed states. Each transition starts a job, a runner does the work, and the job returns another artifact.
Agents talk to each other through those artifacts, never through conversational memory. What shipped is what the record says shipped.
How it runs
-
A request becomes an artifact.
backlog
A feature request is written down as the first artifact of a run. Nothing moves until it exists.
-
Agents design. A person approves.
designdesign_approval
Research, PRD and design package are produced by agents. Design approval is a human gate; the run waits for it.
-
It is built and checked twice.
developmentautomated_qamanual_reviewescalated
Development runs as jobs on runners. Automated QA runs first, manual review second. Failures escalate instead of slipping through.
-
It ships as a release candidate.
readyreleased
Ready means every gate passed and the record says so. Released is the last state, and the start of the next request.
What is in the box
-
Workflow engine
Nine governed states, explicit transitions, one run per feature request.
-
Artifacts
Eleven artifact types, from feature_request to release_candidate, as the system of record.
-
Agents
Research, plan, design and build jobs bounded by skill files and policy definitions.
-
Runners
Self-hosted or managed. Online, busy, offline, disabled: the runner state is visible.
-
Gates
Design approval and manual review stop the run until a person acts.
-
Audit log
Every transition, job and artifact, with its actor: user, agent, system or runner.
-
Project memory
Context that persists across runs, so the next request starts where the last one ended.
Two ways to run it.
Everything we run for clients is the Sydeso platform: states, artifacts, agents, runners, gates and the audit log. You can run it too.
Self-hosted
Free · BUSL-1.1
Clone the repository and run it on your own infrastructure for internal or personal use. Postgres, Redis and S-3 compatible storage.
- Self-hosted runners
- Your data stays with you
- AGPL-3.0 from 1 June 2030
Source available
The core platform is public under the Business Source License 1.1. Self-host it for internal or personal use today. On 1 June 2030 it converts to the GNU Affero General Public License v3.0. Read the source on GitHub ↗
Today Business Source License
BUSL-1.1
- Read, modify and self-host the source
- Internal and personal use at no cost
- No hosted offering to third parties
From 1 June 2030 GNU Affero General Public License
AGPL-3.0
- Free software under copyleft
- Run it for anyone, including as a service
- Share your changes under the same licence
Change date 2030-06-01 Change licence AGPL-3.0-or-later
Run it with us.
Tell us what should ship first and we will run it on the platform, hosted or on your own infrastructure.
Start a project