EN
Appearance

To remember this theme on future pages, allow saved preferences. Cookie preferences

Could not save. Check that your browser allows cookies and try again.

Talk to sales
MenuClose
Talk to sales

Preferences

LanguageEnglish
AppearanceSystem
Appearance

To remember this theme on future pages, allow saved preferences. Cookie preferences

Could not save. Check that your browser allows cookies and try again.

Security and engineering

Engineering that is measured and proved

What your risk and technology teams will ask before signing, answered with facts: the same screening always gives the same answer, one customer does not take the others' place, a repeated call does not become a double screening, and every rule is a test. Every statement carries its source and date.

In numbers

p99 of candidate retrieval on the production server, over the real corpus of 378,746 parties
10.2 ms
Source: dembli search engine performance report, Oct 12, 2026
failed queries across nine runs on the production server, with up to 32 clients at once
0
Source: dembli search engine performance report, Oct 12, 2026
properties of the search engine proved mathematically by machine: ten for every input in their domain and three for every input up to a size fixed in the proof
13
Source: dembli search engine proof index, Oct 9, 2026
p95 latency budget of a whole screening, from request to receipt
300 ms
Source: dembli search engine specification, Oct 9, 2026

01 · Determinism

The same screening, the same answer. Today, tomorrow and at the audit.

An auditor who reruns a screening must find the same result. That is why candidate retrieval runs on an engine dembli wrote to always answer alike.

  • Same query, same candidates

    The same index and the same query bring the same candidates, in the same order. Ties break by the entity's identifier, and nothing depends on threads, segments or the order data arrived in.

  • Proved, not just tested

    That the order of results never depends on chance, and that every tie has a rule, is proved mathematically by machine for every valid score, not just tested.

  • Protected identifiers kept out of the index

    A protected document number enters the search index only as a fingerprint, never as text. Names, subjects and documents never reach the logs.

  • Rebuildable without loss

    The index is derived from the platform's records. If it is lost, it is rebuilt without fetching any source again and without losing data.

02 · In production

Measured on the production server. With the real corpus and the platform serving.

A whole screening's latency budget is 300 ms at p95. Candidate retrieval, the step that searches the corpus, uses a small part of it, even with 32 clients at once.

Candidate retrieval on the production server, median of 3 runs
Clients at onceQueries/sp95p99Failures
1 client2958.3 ms10.2 ms0
8 clients1,38615.7 ms20.1 ms0
32 clients1,63031.4 ms36.6 ms0

How it was measured

  • dembli's production server, an Intel Core Ultra 7 265, with the platform serving at the same time.
  • The engine in a container capped at 8 cores and 3 GiB.
  • 378,746 parties of the production corpus and 20,000 subjects drawn from it, queried through the platform's own client and query template.
  • Nothing was written to production's databases; only counts and latencies left the server.

Source: dembli search engine performance report, Oct 12, 2026

03 · Isolation

One customer does not take the others' place. Not even past its limit.

Every API request passes four gates, all in memory, before any work is done. A customer past its own limit is refused without taking the others' capacity.

  • Each organization's limits

    Each organization has its own rate and number of requests at once, as its contract says. Past them it gets a 429 with Retry-After.

  • Capacity shared by contract

    When capacity is short, each organization keeps its share, in proportion to what it contracted. A place given back goes first to whoever is below its share, and test keys are the first to yield.

  • Each organization's data kept apart

    Every query over an organization's data must name the organization. A test reads every query in the code and fails the one that does not; the exceptions are listed, each with its reason.

  • Overload without collapse

    Past capacity, the API answers what it admits and refuses the excess within a second, with a 503 and Retry-After, instead of leaving everyone waiting. The limit adjusts itself to latency.

04 · Integration

Retrying a call is safe. And every notice arrives signed.

Networks drop, clients retry, endpoints slow down. The API is built so that none of it turns into a double screening, a lost notice or one customer delaying another.

  • Idempotency

    A create repeated with the same Idempotency-Key within 24 hours gets the first answer back, marked Idempotent-Replayed. Nothing is screened again and no second receipt is kept.

  • Signed webhooks

    Every monitoring change arrives signed as Standard Webhooks. When a secret is rotated, the previous one keeps signing through the overlap, so no notice goes unverified.

  • Fair delivery across endpoints

    Each delivery pass takes at most four notices per endpoint, oldest first. A slow or unreachable endpoint does not delay the others' notices.

  • A contract that never breaks silently

    The API contract is versioned. A change that breaks a client is refused by the contract check, unless a decision is recorded and published in the changelog, written in Portuguese, Spanish and English.

05 · Gates

Code does not ship without proof. Every rule is a test.

The rules that protect customers do not depend on anyone remembering them: each is a test that fails the code that breaks it.

  • A bad file publishes nothing

    Every source file is checked whole before anything is written. If it fails the quality gate, nothing is published and the last good state keeps being served.

  • Accuracy measured before a change

    A new matcher configuration ships only with a reference baseline measured under it on the real corpus; a test fails one that ships without. The evaluation fails a change that loses more than a point of accuracy or names 5% more people and companies that are not the one sought.

  • Migrations while the database serves

    A test requires every migration to build indexes without locking tables and to validate constraints outside the transaction. Each is applied, rolled back and applied again before it lands.

  • Fuzzing on every source

    Every source reader has golden-file tests and fuzz tests, which feed the code random and malformed input.

06 · Security

Secure by construction. Not by promise.

  • A record that is never rewritten

    Each screening keeps its receipt, the question and the answer, and every decision an analyst records on a result. The API can insert and read these records but never change or delete them; a new decision does not erase the earlier one, which stays as history.

  • Post-quantum cryptography

    The customers you ask us to monitor are encrypted with hybrid cryptography that already resists quantum computers: ML-KEM-768 with X25519.

  • A minimal image

    The platform runs in a minimal image, with no shell, no package manager and no OpenSSL, as an unprivileged user, which shrinks what an attacker can use. Build images and actions are pinned by hash.

  • A content policy that never loosens

    The console runs only its own scripts or scripts identified by hash. A weaker policy is refused, and uploaded documents are served sandboxed.

The performance figures were measured on the production server. Every other statement is a property the code guarantees by a test or a proof. Algorithms and internal structures stay with dembli.

Bring these questions to the call

Talk to sales and bring your risk and technology teams: we show each of these guarantees in practice.

Talk to sales