Sturdy Documentation

Sturdy is an open-source version control platform that allows you to interact with your code at a higher abstraction level. This provides an ergonomic, real-time workflow for individuals and teams.

In Sturdy, developers perform actions that are directly mapped to their intent, rather than thinking about the underlying data structures. For example: "Ship this code to production" instead of "Create a branch, stage files, make a commit, push to remote, merge, etc.".

The dynamics of teams at tech companies are different from those of most open source projects. The biggest difference is in how closely people collaborate with each other — at a software shop you already synchronize, share knowledge and plan together. Sturdy is built specifically for this workflow.


There are three versions of Sturdy:
  • Sturdy in the Cloud lets you code and collaborate in real-time with your team.
  • Sturdy Enterprise lets you run your own Sturdy instance in your own environment.
  • Sturdy OSS is an open-source version of Sturdy that gives you all of the core functionality of Sturdy, but with some advanced features missing (OAuth, incremental migrations to Sturdy, etc).

Want to take Sturdy for a spin?

Get started on Sturdy Cloud, or run in Docker:
docker run --interactive \
    --pull always \
    --publish 30080:80 \
    --volume "$HOME/.sturdydata:/var/data" \

Sturdy is built on top of low-level Git data structures, so your code is always stored in a well-compatible format, and allows you to easily migrate your team to Sturdy, even partially if you want.

You can use Sturdy by yourself and benefit from an optimized workflow even without anybody else on your team using it. Sturdy has a bridge integration with GitHub that allows you to interact with your existing projects.

On the other hand, as more people from your team use Sturdy, it also becomes possible to benefit from a frictionless exchange of ideas — give code suggestions, early feedback.


Collaboration in Sturdy is built around two core principles:

  • Continuous feedback over traditional code review
  • Small incremental changes over big-bang releases

Continuous feedback reflects the reality of working together — getting help and suggestions on an early version of the code is more effective than review of a "completed" work. This means creating an environment which fosters experimentation and working in the open.

Shipping small incremental changes is proven to increase speed of development as well and reduce the risk of deployments. Sturdy makes shipping of small and incremental changes the intuitive default. It embraces continuous delivery and trunk based development.