Git

Your data model belongs in Git.

Specly connects your project to a Git repository on GitHub or Azure DevOps. The model lives on the same branches as the code, and you see what changes before it is applied.

Specly
Git
main
main
new-pricing-model
new-pricing-model
How it fits together

Same branch, same name, in both places.

  1. 1

    Branch for branch

    A branch in Specly is a branch in Git, with the same name. Create new-pricing-model in Specly, and new-pricing-model exists in the repository too.

  2. 2

    Changes both ways, always with review

    Changes from Git show up as a review in Specly, and nothing is applied until someone merges them. The way to Git is a commit you start yourself.

  3. 3

    You own the access

    You choose the repositories Specly can reach: GitHub through a GitHub App, Azure DevOps through a service principal.

Work where you work

One model, several ways to work on it.

Questions and answers

What people often ask.

Which Git services does Specly support?
GitHub and Azure DevOps.
What format is the model stored in?
You choose per project: Specly JSON, ODCS contracts or both.
Does anything change without review?
No. Changes from Git show up as a review and are not applied until someone merges them, and nothing is written to Git unless you start a commit yourself.
Who controls access?
You do. You own the access and choose the repositories Specly can reach, and you can revoke it at any time.

See Specly in action.

Tell us how you work today, and we will show you how Specly could fit in.