Frequently Asked Questions
Exberry is a technology company that delivers a purpose built exchange infrastructure-as-a-service, regardless of asset class or opportunity. The core technology is deployed to enhance existing exchanges’ limited capabilities or to serve as the base for trading new digital assets.
Our core matching engine has been designed not only to compete with the technology used by the biggest exchanges in the world, but also as light-to-deploy, integrate and operate, and is therefore an excellent fit for start-ups and anything in between.
Our technology and software engineering heritage combined with our strategic business counsel means Exberry can quickly scale with business growth, and is easy to integrate into new and existing ecosystems through well-documented APIs and easy-to-access sandboxes.
Exberry technology provides matching engines ideally suited to support every type of marketplace in traditional and digital assets including:
- Traditional financial markets
- Digital securities
- Alternatives (e-sports, synthetic instruments, property, art, wine, etc.)
- Risk and reinsurance
- Climate change and carbon exchanges
- Environment, social and governance opportunities
- Prediction markets (Gaming & gambling, iSports, marketplaces)
Exberry is agnostic to asset classes. Traditionally, equities can be seen as exchange contracts with two “legs”, with each leg representing one side of the exchange (i.e. equity in one leg, and quoted currency in the other leg). In Exberry, instruments can contain any asset in either leg. Trading on yield, currency, futures, options and other derivative instruments are all supported.
How long does it take from application to launching an exchange?
Our sandbox is available on a continuous basis, which means a new site can be up and running within weeks. In addition, our use of modern APIs enables integration work to be completed within a few weeks.
You can start now by linking to our API specs and sandbox.
If you want to talk to us, please fill out the form and we’ll be in touch.
In an ideal world, you provide us with the below information; but we understand that many of these details will not be known at start, so share as much information as you can, and our flexible and elastic service will scale with you.
1. What are your trading hours?
2. How many instruments are traded in the system?
3. How many server-to-server API connections to exchange API are there?
4. How many resting orders are in the system at any given time?:
4.1. In total
4.2. For the most traded instrument
5. How many trades (i.e. matched orders) per day are expected, please provide:
6. How many orders are sent to system in total :
6.1. On average day
6.2. On peak day
6.3. Maximum per second
7. How many orders are sent to system in the most traded instrument:
7.1. On average day
7.2. On peak day
7.3. Maximum per second
1. For how long will you need immediate access for the below data:
1.1. Orders history
1.2. Market data history (orders messages)
1.3. Audit records
2. For the time frame that is after the answer on the above question, what is your preference:
2.1. Backup it on physical media
2.2. Make it accessible ad hoc per request (with few hours response time)
1. What are your DR requirements in terms of:
1.1. Geographical separation
1.2. Response time to bring system up from DR environment
1.3. Updated interval (should it be hot DR or can it be only upon X minutes?) that business terms can accept.
1. Select deployment environment:
2. Deployment type are (more details can be found in the Change Management document)
2.1. Fully managed
We charge via a monthly subscription fee, and a ‘per messages’-based fee for higher volumes. A one-off set-up fee will also be incurred.
Does Exberry support a mobile version?
Exberry is cloud agnostic and can run anywhere. We do this by running modern APIs which enable easy integration with Apps.
We intend to be the first in the world to offer a fully self-serviced matching engine.
Our vision is to offer end-to-end exchange infrastructure that extends upstream and downstream to integrate with EMSs and OMSs, engage risk and reg tech firms, and also flows down into post trade, custody and settlement irrespective of asset class.
JSON is a cost-effective, easily integrated solution that is widely used in non-financial market applications. If you are not latency sensitive and you want to get a micromarket up and running really fast, JSON is a great fit as it is used industry-wide and is supported by most technology platforms.
The Reliable User Datagram Protocol (UDP) is a transport layer protocol used In computer networking. Reliable UDP solves the problem of low latency and high throughput communication between nodes, and is used within the Exberry platform.
Because regular UDP is based on a Fire-and-Forget (one-way) message exchange pattern that continues to operate without waiting for a response, you run a risk of packet loss (the failure of packets to reach their destination on a network). UDP, however, is much faster than the Transmission Control Protocol/Internet Protocol (TCP/IP) networking protocol. That’s where Reliable UDP comes into play.
Reliable UDP simulates TCP behaviour (where we expect to get a return response), but instead of relying on the OS buffers and SYN-ACK (synchronize-acknowledge) protocol built into TCP, we handle it on application level using a Memory-mapped file that has the ability to read and write much faster. This Memory-mapped file can index, write and commit the reliable UDP protocol, as well as keep track of the packets and their order while writing the file, so it will only ask to retransmit a packet in case of packet loss.
Exchange matching systems have been traditionally developed to serve either a specific customer, or a few specific markets. This type of system was focused on delivering performance and product features, rather than the ability to scale. This integral difference is at the heart of why legacy vendor system delivery projects tend to take so long, with upgrades prone to risk and additional expense.
Exchange matching systems, whose architecture has been developed with a focus on scalability from the outset, are capable of delivering any number of different and unique deployments. This approach is based on combining elements of microservices, Kubernetes, and B2B models in order to create an ecosystem in which the matching engine resides.
Software-as-a-Service (SaaS) is a webservice model that has provided a revolutionary new way of thinking and designing software from that of traditional licensed-based software distribution models. With SaaS, it is possible to build architecture that scales to better serve all different sizes of customers, and can be released within a much shorter time frame.
Kubernetes, also known as K8s, is an open-source system for automating deployment, scaling, and management of containerised applications. For more information: https://kubernetes.io/