For compliance teams

DojiPad doesn't replace the pre-trade checks in your order system or your post-trade surveillance. It adds what neither holds: a record of the decision itself, made at the time and checked against your limits, before the order.

• the committed plan and its written reasoning;
• for a plan that would breach a limit: the figure, the limit, the price used and what it was measured against;
• what the trader was shown: the full figure, only whether they were near or over the limit, or nothing (a limit monitored internally);
• acknowledgements, append-only: who reviewed which breaches, and when;
• daily sign-offs;
• a stamp on each export (see the stamp). Opening any page that can be exported is logged as an audit event.

You give DojiPad the document that sets out your firm's limits. DojiPad proposes each limit, ready to be set up in the system. Each limit's threshold, and what it is measured against, must come from the document's own text. If they do not, the proposal says the limit cannot be expressed. It never shows a guessed number. DojiPad does not guess.

Each limit, once set up, is either switched on or not. When a limit changes, the old version is kept, and each limit finding records which version it was checked against. Every exported PDF carries a stamp. The stamp lists which limits are monitored and which are declared not monitored. So a gap in coverage is stated openly, never left unsaid.

Futures are sized in contracts, using a verified record of contract multipliers. A plan that cannot be measured this way is refused, not estimated.

Each group shows its worst breach, as a multiple of the limit. Three states are kept separate because they answer different questions. Open is the firm's state: a limit breach that no one has acknowledged yet. Unreviewed by you is this officer's own marker: what has arrived since this officer last looked. Acknowledged is the acknowledgement record: reviewed, on the record, with a name and a time.

Every acknowledgement is saved with the officer's name, the time, and the limit breaches it covers. Entries can only be added, never changed: DojiPad can't edit or remove one.

Every day, the system checks every active limit for every trader. Each result is one of three: within the limit, breached, or declared not measured. A limit that could not be measured is listed as not a pass. So the gap is visible, not silent.

Every oversight screen can be printed to PDF. Each PDF shows the as-of time and the officer who generated it. It shows the filter it was printed with (desk, name filter, status). And it carries the monitoring line, which names any limits that are not monitored.

Open means a limit breach that no one has acknowledged. The list of limit breaches, the desk overview and Analytics all show the same number.

Every oversight screen has the same filter bar: one desk or the whole organization, a name search, and status. The filter travels with the record. It is stamped on the PDF, so a filtered export says that it is filtered.

• We never hold your trade data: DojiPad runs in your firm's own cloud account, and nothing in it calls back to us.
• It doesn't sit in your execution path: it never touches an order.
• The trader's conversation with DJ, DojiPad's AI coach, is kept off the firm's screens by design: the firm's screens and reports can't retrieve the trader's side. It is stored in your firm's own database, so, as with any system your firm hosts, its database administrators could read it there. The firm's record is the committed plan and any limit breach found with it. Our regulatory memo sets out how we see that against recordkeeping rules; your counsel should confirm it for your firm. Paper III explains why this makes a better record.
• It does add a record you can show: the decision, the check and the review.

The full regulatory mapping, in a document your compliance team can file. You can have it before a briefing. It is delivered by email.

• The network layout of the private deployment, shown live in your firm's cloud account.
• What each part of the deployment can send out, and the evidence for each part.
• The separation between the trader's side and the firm's side, shown from an officer's seat and a trader's seat.
• Identity: how your Entra ID groups (your firm's staff directory) map to roles, and what each role can open.
• The records: where the audit trail is kept, and how it is exported.

The two-page security brief covers the boundary, the evidence, identity, and how long records are kept (retention): read it as a page or download the PDF.

• We complete operational due diligence questionnaires.
• Security reviews run live with your security team, under NDA (what a review covers).
• The deployment produces its own evidence: what is allowed to leave, and proof that the firm's screens and reports can't retrieve the trader's side.
• Your auditors can inspect DojiPad where it runs: in your firm's own cloud account.
• The list of findings from our own deployment rehearsal is available to your compliance team on request.

ARQNXS OÜ (Estonia), incorporation in progress.ARQNXS was founded in 2017 by Nigel van der Laan and is based in Amsterdam and Barcelona.

Company details on the About page →

• It doesn't block, restrict or route orders. Ever.
• We can't see your trades. Nothing in your deployment calls back to us.
• It doesn't read your traders' screens, email, messaging apps or orders.

These three statements are quoted from the product's own screens.