Community

Built in the open, on purpose

Everything foundational here is open source — not as marketing, but because systems that shape the future of work must be inspectable. Contribution is how you join.

Adopt a sandbox project

Sandbox projects are running experiments that want users with opinions. Run one, break it, file exactly what hurt.

Try a guide, file the friction

Every quickstart that fails silently is a bug. Following a guide end-to-end and reporting where it lied is a first-class contribution.

Write an RFC digest

Our repositories carry deep RFC corpora. Digesting one for the research zone — context, decisions, results — helps everyone who arrives after you.

Bring a workload

The governed stack is built for real fleets. If you run agents in production and want governance without lock-in, we want your constraints.

Channels

Where to find us

GitHubgithub.com/tsok-org
Emailteam@tsok.org

FAQ

Straight answers

Is TSOK a company?: It is a lab run as a community. Some projects have commercial surfaces (managed clouds, licensed fleet tooling) that fund the open work — the defaults are open source.
Can I use the projects commercially?: Mostly yes: cores are Apache-2.0 or MIT. A small set of fleet components ship under BUSL-1.1 and convert to Apache-2.0 automatically after three years. Each repository states its terms plainly.
How do projects graduate?: Documented gates, not vibes: real docs, tests or conformance evidence, a stated security posture, and at least one real user. The Sandbox page shows the lifecycle.