Need help with EventStore?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

4.3K Stars 597 Forks Other 7.1K Commits 294 Opened issues


The stream database optimised for event sourcing

Services available


Need anything else?

Contributors list


The open-source, functional database with Complex Event Processing in JavaScript.

This is the repository for the open source version of EventStoreDB, which includes the clustering implementation for high availability.


Information on support and commercial tools such as LDAP authentication can be found here: Event Store Support.

CI Status







Documentation is located in the

folder. It's orchestrated in the separate documentation repository. It's available online at

Read more in the documentation contribution guidelines.


We have a community discussion space at Event Store Discuss. If you prefer Slack, there is also an #eventstore channel in the DDD-CQRS-ES Slack community.

Release Packages

The latest release packages are hosted in the downloads section on the Event Store website: Event Store Downloads

We also host native packages for Linux on Package Cloud and Windows packages can be installed via Chocolatey (4.0.0 onwards only).

Building EventStoreDB

EventStoreDB is written in a mixture of C#, C++ and JavaScript. It can run on Windows, Linux and macOS (using Docker) using the .NET Core runtime. However, the projections library (which uses the V8 javascript engine) contains platform specific code and it must be built for the platform on which you intend to run it.

Windows / Linux

Prerequisites - .NET Core SDK 5.0

Build EventStoreDB

Once you've installed the prerequisites for your system, you can launch a

build of EventStore as follows:
dotnet build -c Release src
The build scripts:
are also available for Linux and Windows respectively to simplify the build process.

To start a single node, you can then run:

dotnet ./src/EventStore.ClusterNode/bin/x64/Release/net5.0/EventStore.ClusterNode.dll --insecure --db ./tmp/data --index ./tmp/index --log ./tmp/log -runprojections all --startstandardprojections --EnableAtomPubOverHttp

Note: The build system has changed after version

, therefore the above instructions will not work for older releases.

Running the tests

You can launch the tests as follows:

dotnet test src/EventStore.sln

Building the EventStoreDB Clients

The client libraries are located in their own repositories, refer to their specific instructions.

gRPC clients: * Go: EventStore-Client-Go * .Net: EventStore-Client-Dotnet * Java: EventStoreDB-Client-Java * Node.js: EventStore-Client-NodeJS * Rust: EventStoreDB-Client-Rust

TCP clients: * .Net: EventStoreDB-Client-Dotnet-Legacy * JVM: EventStore.JVM * Haskell: EventStoreDB-Client-Haskell

Note: the TCP protocol is being phased out.

Building the EventStoreDB web UI

The web UI repository is a git submodule of the current repository located under


The web UI is prebuilt and the files are located in src/EventStore.ClusterNode.Web/clusternode-web. However, if you still want to build the latest web UI, there is a parameter in the
) and
) scripts to allow you to do so.

Building the Projections Library

The list of precompiled projections libraries can be found in

. If you still want to build the projections library please follow the links below. - Windows - Linux - macOS


Development is done on the

branch. We attempt to do our best to ensure that the history remains clean and to do so, we generally ask contributors to squash their commits into a set or single logical commit.

If you want to switch to a particular release, you can check out the tag for this particular version. For example:

git checkout oss-v6.0.0-preview1

Read more in the contribution guidelines.

Proto Changes

If you update the protos, continuous integration will fail. After ensuring the proto change is backwards compatible, please run

./ commit
at the root of this repository.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.