What is Veracity?

It’s a DVCS (like Bazaar, Git or Mercurial).

It also has a bunch of features no other DVCS has (like a decentralized database).

It’s open source (Apache License v2).

Open Source? How are you guys gonna make money?

The core of Veracity will be open source, but we plan to sell other products and services on top of that core.

So which parts are going to be kept proprietary?

Enterprisey stuff. Repo storage in SQL Server and Oracle. Visual Studio integration. Servers with fine-grained configurable policies.

Who is SourceGear?

We’ve been building and selling version control and bug-tracking products for 12 years.

We sold our Teamprise division to Microsoft in 2009.

We are privately held and located near the campus of the University of Illinois at Urbana-Champaign.

Hey, you guys make Vault! Are you abandoning it?

Heck no. It’s, like, 100% of our revenue. And there are still thousands of teams on SourceSafe that need to be rescued from their plight.

Are you dogfooding yet?

Indeed. We’ve been using Veracity for our own development since May 24th, 2010.

So is Veracity ready for ME to actually use it?

Yes! Head over to the download page.

Where can I get the code?

You can grab a tarball from download.sourcegear.com/Veracity/nightly or clone from the public repository at http://public.veracity-scm.com/repos/veracity.

What languages is Veracity written in?

C and Javascript.

What is the build system?

CMake.

Cross-platform is a high priority for us. CMake allows us to generate Visual Studio build files on Windows as well as traditional makefiles for the Unixy platforms.

Can I contribute?

Not yet.

We don't have everything figured out yet for us to accept patches and code contributions.

What is “Sprawl”?

Before we decided on Veracity as the product name, Sprawl was the project code name. Instances of this name can still be found lingering around.