Send the form below and it reaches an engineer rather than a queue: an evaluation enquiry is read by someone who can answer it, and a live incident by someone who can reproduce it from the journal. Email works just as well if you would rather hold your own copy of the thread, and there is a telephone in office hours for the conversations that are faster spoken than written.
Nothing here is a qualification questionnaire. Four lines about what you are trying to open is enough to get a useful answer back, and the awkward questions are welcome earlier rather than later.
Demonstrations, market-model questions, the evaluation guide, pricing and scoping, and functional queries or technical advice about the Mehrex Trading System. If you are working out whether the platform fits your market, this is the address. It is also the channel named for technical account management once you are a customer.
Open an email with the scoping questions prefilled →Live service incidentsIncident and problem management for customers running a live venue, under agreed response targets. Use it for anything affecting an operating market: an unexpected reject, a member unable to connect, a market that has halted. Not the address for evaluation questions — those will simply be forwarded, more slowly.
Open an incident email with the fields prefilled →Call for evaluation and commercial questions while the office is open. For anything affecting a live market, write to support@finblocks.tech as well as calling — the response targets run against the written record, and the thread is what gets worked from.
Map data © OpenStreetMap contributors
It is a working session rather than a presentation. We run a configured venue, you ask for the awkward cases, and we show them — or say plainly that the platform does not do that yet.
We enter orders and let an aggressive order sweep the resting side under price–time priority, so you can see how price, order type, volume disclosure and time resolve against each other — including an iceberg keeping its hidden volume out of public data while participating fully.
An operator configures an instrument, a tick table and a session timetable in the browser, publishes it as a versioned reference-data bundle, and halts and resumes an instrument. You see the maker–checker approval step as it happens.
A pre-open call with the Indicative Equilibrium Price recalculated as orders arrive, then the uncrossing itself, then the closing price becoming tomorrow's static reference price.
We replay the sequence of commands that produced everything you just watched, and the fills, average prices and book states come out identical. This is the part evaluators tend to want twice.
None of it needs to be final, and approximate answers are fine. With these six, the first conversation is about your market rather than about ours.
Nothing between the first email and a live market is a surprise. Each phase has named outputs, and the next one does not start until they exist.
First. After a demonstration and one scoping conversation, once both sides think the venue is a fit.
Second. Once the written market-model specification is agreed on both sides and the delivery scope is settled.
Third. When the conformance runs and dress rehearsals say your members are ready, not when a date on a plan arrives.
