Talk to an engineer
Data centre racks

The technology stack behind top performers.

Who we are

A senior team that builds its own
complex systems and runs them.

Behind the timeline below sit our own engineering teams, a hardware research laboratory and a 24/7 network operations centre. Other companies bring us the problems that need deep engineering. How we work →

2017

The team comes together

Senior engineers who had known each other for more than thirty years in the field teamed up to build a crypto exchange.

2019

First exchange live

When the market moves, a slow exchange loses money. We built a fast, secure one: a high-performance matching engine and live WebSocket market data.

2020

Our own private cloud

We designed our own private cloud from the CPU to the network, built around the work it actually does. Less hardware, more speed, a smaller bill.

2022

MCQuote v1

Depth and price levels are worth nothing once they are old. MCQuote collects an uninterrupted, low-latency feed from many exchanges and locations, then analyses and executes.

2024

Exchange platform, rebuilt

Perpetual futures, hedging, P2P and an Earn Center give traders more reasons to stay, on a faster platform. The people running the exchange get an advanced campaign, coupon and affiliate system for marketing, and a back office that calculates every number in real time.

2025

Three locations

Zurich, Frankfurt and Istanbul keep us close to the financial centres our clients trade in, on low-latency links. If one site fails, the other two are untouched — they share no power grid, no city and no jurisdiction.

2026

MCTX completed

Your developers should be building your product, not chasing chain upgrades, node failures and the next exploit. MCTX gives them one generic API. Maintaining and monitoring the nodes is our job, not theirs.

TODAY

Swiss-headquartered

We are Swiss-headquartered now, with a bigger team. All of it runs on our own infrastructure in Zurich, Frankfurt and Istanbul.

We do not publish performance numbers. We prove it on your system.

You will not find client logos or testimonials here, and that is a decision. Our clients run regulated and competitive businesses, and they buy our discretion along with the work. A logo proves nothing about how a system behaves under your load. Everything below happens before you sign anything.

Proof of Performance

Before you commit, we run a live load and stress test of the platform with you.

You set the test We run it live, with you You keep the evidence

Cloud cost analysis

We start from your actual bill, not from a calculator, at $10,000 or more a month of public cloud spend. Where the workloads suit it, that is up to 50% lower cloud costs.

You send one month's bill We map it workload by workload You keep the analysis

Scoped assessment

Name one process question you cannot answer today. Our SAP Signavio specialists mine the event data your systems already produce.

You name one question We mine the data you already have You keep the written answer

We do not publish client names. Ask, and we will share relevant references under NDA — we reply within 2 business days.

FAQ

Frequently asked questions

  • Yes. Send us a scope and you get an indicative figure in writing within 2 business days, before any call. The model is not metered: no per-user fee, no per-identity-check fee, no per-request quota, no per-admin-seat charge and no separate maintenance contract. What moves the price is the delivery model you choose, the modules you switch on and how much of the running we do. All of it is in writing before you commit to anything.
  • Yes. It is called a Proof of Performance session and it runs against a real deployment on defined hardware. You set the scenarios and the load. We run it live with you, and we cause failures on purpose while you watch — a node dropped, a venue disconnected, a database primary lost. You keep the measurements and the configuration that produced them, so you can hold every other supplier to the same test. It comes before you commit, and it is a standing offer rather than a favour.
  • Yes, in the on-premise model. It runs in your data centre or your own cloud tenancy, with your keys and your data, and there is no call-home dependency on us to keep trading. You get the runbooks, the upgrade procedures and the fork playbooks with it, because infrastructure you cannot operate without us is not infrastructure you own. Source access and exit terms are commercial terms, and we put the exact wording in front of you before you sign. See MCEX in detail.
  • Yes. The engineer who answers your first technical question is the one who designs your system, and they stay on the account afterwards. We do not operate a pyramid and we do not place people by the day. You meet the specific people before you commit, in a technical conversation rather than a credentials presentation.
  • Yes. A Switzerland-only or Germany-only design is written into the agreement, including which sites may hold replicas, backups and log data. Administrative access can be pinned to the same jurisdiction, with the controls, the logging and the on-call arrangement that make the constraint real rather than a sentence. It costs something in response time and in price, and we tell you what it costs before it becomes a requirement.
  • Yes. The Unified Order Book in MCQuote aggregates centralised and decentralised crypto exchanges and traditional trading platforms into a single deeper book, read from several data centres at once. You connect to MCQuote, and we build and maintain the connectors, the normalisation and the reference data as the venues change them. Your venue accounts, your credentials and your relationships stay in your name.
  • Yes. The same MCTX API call works on every chain we support, so you do not write a new integration for each one and you do not run a node. Adding a chain is normal work for us rather than a special project, because the framework was built to be extended. Ask about your specific chains and you get a direct answer, including where support is production-grade today.
Contact

Talk to an engineer.

Fill in the form and our engineers will review your current cloud costs, workloads and infrastructure goals. Your message goes to people who work on these systems, not to a queue, and we reply within 2 business days.

Full name is required.
Enter a valid email address.
Select an area of interest.
We reply within 2 business days.

We use what you send us to answer your enquiry and for nothing else. No newsletter, no drip campaign, and your details are not passed to a reseller or sold to anyone. Full detail in the Privacy Policy; company details in our legal notice.