Practical overview
When it fits
Use Core as a technical starting point when building or operating a self-hosted cryptocurrency exchange and you can configure its services and deployment environment.
Who it is for
- Developers building a self-hosted cryptocurrency exchange backend.
- Teams adapting a matching engine or microservice foundation for a custom exchange.
Documented uses
- Start from an exchange backend foundation rather than build every core service from scratch.
- Build and start the project using its Maven and Docker Compose instructions.
Requirements & limits
The source repository is public and identifies the project as MIT-licensed.
- Core is infrastructure for building an exchange, not a consumer-facing trading venue.
- The documented setup requires both Maven and Docker.
- The repository provides an extensive environment-variable configuration list covering application services and integrations.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build and start Core with Docker Compose
Build the project and start its services using the repository's documented Maven and Docker Compose workflow.
Before you start
- Maven
- Docker
- A clone of the Core repository
- A root-level .env file configured with the required environment variables
Steps
Clone the repository and change into the cloned directory.
Create a .env file in the project root and add the required environment variables.
Run mvn clean install.
Build the Docker images using the documented Docker Compose files.
Start the project with the documented Docker Compose files, then use docker ps to check service health.
Expected outcome
The project’s services are started through Docker Compose, with docker ps available to inspect their health.
Guide limitations
- The environment-variable list includes settings for multiple integrations; configure the values required for the deployment.
- The guide documents setup commands but does not establish deployment suitability or successful execution in a particular environment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 8 October 2026
- Original website title
- opexdev/core · Official homepage title · retained in its source language

