Contact

Talk to the people who wrote it

Whether you're evaluating Open Exchange, planning a deployment, or need something built on top of it: book a call or write to us. You'll talk to an engineer, not a funnel.

Book a callinfo@openexchange.devOpen a GitHub issue

Grab a slot on the calendar for a live conversation, or email if async is easier — either way you reach the engineers directly.

What to include

A few lines are enough. The most useful things to tell us:

  • What you're building, and roughly who it's for.
  • Where you are today: evaluating, prototyping, or already running something.
  • What you need from us: a question, a deployment, an integration, a review.
  • Any hard constraints: latency targets, jurisdiction, timeline.

Found a bug or want a feature in the open-source stack? A GitHub issue on the matching repo is the fastest route; we triage those in the open.

Security reports
Please don't put vulnerabilities in a public issue. Email us directly and we'll take it from there; the process is described in each repo's SECURITY.md.
What we help with
  • Architecture consulting
    We help you decide how Open Exchange fits your product, your latency budget, and your compliance setup before you commit.
  • Custom configuration
    Markets, tick sizes, risk limits, auth modes, cluster layout: tuned to your case instead of the defaults.
  • Deployment and setup
    From a fresh environment to a running, monitored stack, with backups and runbooks in place.
  • Performance tuning
    OS tuning, driver profiles, and load testing on your hardware, with honest before-and-after numbers.
  • Security reviews
    A hard look at your deployment: auth, network exposure, secrets handling, and the edges where exchanges usually get hurt.
  • Legacy migration
    Planned, rehearsed migrations off an existing engine, with balances reconciled to the unit before you cut over.
  • Support and SLAs
    Ongoing help from the people who wrote the code, under support agreements with response times we'll commit to in writing.
  • Team training
    Your engineers learn the architecture, the operations playbook, and the sharp edges directly from us.
  • Custom feature work
    New order types, connectors, or integrations built into the stack properly, not bolted on.
Open Exchange

The open-source core to launch your own exchange. Fast, fault-tolerant, built in public.

v0.4.0-beta

Apache 2.0 · Beta software: the public API is frozen, but it has not had an external security audit yet and should not hold production money until it does. Open Exchange is the infrastructure you build an exchange on; KYC/AML, custody, fiat, identity, and compliance are the integrator’s responsibility.