Runwork
All Features
Govern · Versioning

Roll back any change

Every change to an app becomes a Git commit, whether your agent made it or a person did. Break something and you roll back instead of starting over.

Get Started

What Versioning gives you

Git-Based Storage

Apps are stored as real Git repositories. Every change is a commit you can inspect.

Commit History

See every change with a timestamp and a message, and follow how the app got to where it is.

Rollback Support

Restore any previous version in one step. A bad change never costs you the app.

GitHub Export

Push the code to your own GitHub repository and keep it wherever you want.

Template Updates

When base templates improve, the updates merge into your apps with a 3-way merge that keeps your customizations.

Why Versioning matters

How Versioning works

Versioning in Runwork treats your apps as proper software projects with full version control. Every change, whether your own AI agent made it or someone edited the code directly, becomes a Git commit with a timestamp, message, and complete diff of what changed.

You can browse the entire evolution of an app: how it started, what changed along the way, and why. When something breaks, the history points at the exact change that caused it. When you need to understand a decision, the commit message tells the story.

Rollback means a mistake never sticks. If a change breaks the app, roll back to any earlier version; code, configuration, and structure all revert together. That is what makes it safe for your team, and your team's agents, to experiment.

GitHub export extends this further. Push your app's code to your own GitHub repository for additional backup, code review workflows, or collaboration with external developers. The code is not locked into Runwork: you own it, and you can take it wherever you need.

Template updates ride on the same machinery. When Runwork improves a base template (security patches, new capabilities, UI fixes), the update merges into your apps with a 3-way merge that keeps your customizations, the same way you would update a dependency in traditional development. A deployment then pushes the updated app live.

Frequently Asked Questions

How does versioning work in Runwork?
Every change to your app is stored as a Git commit using isomorphic-git. Each commit includes a timestamp, message describing the change, and complete diff of what was modified. You can browse the full history, compare versions, and understand exactly how your app evolved over time.
Can I undo changes and roll back to a previous version?
Yes. Roll back to any previous version of your app instantly. The entire app state, including code, configuration, and structure, reverts to that point in time. This lets you experiment freely knowing you can always return to a working state if something goes wrong.
Can I export my code to GitHub?
Yes. Push your app's code to your own GitHub repository. This provides additional backup, enables code review workflows with your team, and ensures you own your code completely. Your work isn't locked into Runwork. You can take it wherever you need.
How do template updates work?
When Runwork improves base templates (security patches, new features, UI improvements), those updates are offered to your apps via 3-way merge. Your customizations are preserved while you receive the improvements, the same way you would update a library in traditional development.

Use Cases

Undoing breaking changes Auditing code history Collaborative development Code review

Related Features

Apps Automatic Backups Permissions

See How Teams Use Versioning

CTOs Agencies Product Teams

Ready to try Versioning?

One shared cloud under the AI tools your team already uses.

Get Started Explore More Features