Who builds your tools, since when, and under what registration.
Ludolith builds custom artificial intelligence tools and integrates AI into systems that are already in place. Our teams have been shipping to production since 2023. This page states what a third party can verify about the company, and what the company does not publish.
Since 2023, build after build
The first AI tool our teams put into production dates from 2023: a document chain, in a line of work where human review stayed mandatory. Everything we do today descends from that constraint. The legal form followed the work, it did not come first.
Year 2023
First production release
A document processing tool shipped into the commissioning organisation's real system, with mandatory human review before signature. The pattern has not changed since: the machine prepares, a person signs their name to it.
Year 2024
Integration becomes the second delivery mode
Enough builds had shown that new software is not always the right answer. Plugging AI into the ERP, the fleet system or the accounting software already in place becomes a delivery mode of its own, with the same method and the same contract.
Year 2025
Two products of our own, so we can show everything
Minealyze and QuestFable both went into production in 2025. Both are designed, built and operated by our teams. They exist for a precise reason: a build under a confidentiality agreement can show neither its code, nor its reports, nor its initial failure. These two products can.
Year 2026
Eight builds published, durations and figures included
Eight records are described on the Proof page, by sector and by size, each with its duration and two measured results. No organisation named, no logo: our agreements forbid it.
A production date is verified inside the commissioning organisation's system, not on this site. That is why the page also publishes what can be checked without us: the NEQ, and two online products the company publishes.
The roles a build runs through
A build runs through the same five roles whatever its domain. The business changes from one sector to the next, the method does not. These are the roles named in the contract and in the build ledger you receive, with the person accountable for each one named in your copy.
Design
Turns a business need into a tool that has an end criterion. This role spends the first days on your premises, watching the actual gesture rather than reading a feature list, then writes the scope, the deliverables and the thresholds before the first line of code.
Engineering
Writes the code, the tests and the evaluation suite. This role freezes the measuring instrument before the first model call, then publishes the baseline to the commissioning organisation, including when it is bad. Across the eight published builds, it was bad three times on the first pass.
Production
Deploys into the real system, with its access, its data and its failures. This role watches the first weeks, measures the effect against a control group when volume allows, and refuses the release when a threshold set at scoping is not held.
Security
Attacks the tool before a third party does, against a copy of the environment. This role writes down what stays open, keeps the security page and the subprocessor list current, and answers your risk team's questionnaires.
Data
Decides what goes into the tool, what does not, and where it stays. This role maps the flows before the build starts, writes the processing register, and puts up the partitions when personal or regulated data is involved. It is the role that says no most often.
No person is named on this site and no photograph appears on it. Names travel in the contract and in the build ledger you receive, where they let you call someone, not in a showcase.
Legal existence, verifiable by you
Ludolith is the business name of 9558-3936 Québec inc., NEQ 1181697518, a corporation registered with Quebec's enterprise registrar. You can verify that registration yourself, for free, by querying the register. Do it before you talk to us: a registration takes a minute to check, a sales promise does not.
- Business name
- Ludolith
- Legal name
- 9558-3936 Québec inc.
- NEQ
- 1181697518
- Legal form
- Corporation (société par actions)
- Register
- Registraire des entreprises du Québec
What attests the capability, object by object
Five objects. Each one exists somewhere other than this page, each one states what it attests, and each one carries the link to where it is documented.
Eight delivered and published builds, plus two artificial intelligence products designed, built and put online by our teams.
- Attests
- End-to-end capability: design, code, deployment and operation stay inside the company, with no handover to a third party. The eight builds add up to 139 weeks of building, 17 on average from scoping to production.The eight builds and the two products
A Folia-compatible Java plugin, written, tested and published by our teams.
The detail of this object lives in the proof file: the compatibility constraints, the third-party server interface and the end-to-end harness are described there line by line.
- Attests
- Non-trivial engineering outside the web: per-region concurrency, a third-party server interface, compatibility constraints that do not negotiate.The proof file
An internal pentest on a product the company publishes: about 103 offensive proofs of concept, 6 weaknesses found and fixed.
6 weaknesses fixedSECURITY-REPORT.md report
What this figure does not say
Internal pentest on a game-server product, run 100 % locally against a copy of the environment. This work does not describe the infrastructure on which a client's data would be hosted.
- Attests
- Offensive discipline applied to our own code, before a third party had to ask for it. The same role attacks the tools we build for you, against a copy of your environment.The security page
A release gate measured and published, including its initial failure at 40 out of 50.
40/50frozen corpus, committed before the first model call
- Attests
- That the method has already run on a real build, including the day it said no. It is the same gate on all eight builds: threshold set at scoping, baseline before any fix, result after.The published measurement, initial failure included
A machine-verified coverage matrix: 343 features inventoried, 0 unaccounted for.
343 inventoried, 161 mapped, 182 excludedmachine-verified coverage matrix, recount test
- Attests
- The refusal of approximation: a test rejects any recount mismatch and any exclusion reason outside the closed set.The proof file
What we cannot do
We do not do 24/7 operations, on-call, embedded site reliability, regulatory advice or model training from scratch. We also do not publish the names of the organisations that engage us: the eight builds on the Proof page are described by sector and by size, with their durations and their figures, never by a logo. Saying no to a scope is the fastest signal of competence, and it saves you from discovering the limit in month three.
What happens next
You know who builds, since when, under what legal name, and what we turn down. The rest gets decided out loud.
Six written questions first, then real slots on the same page. Free, 30 minutes.
The measurements, their threshold, and their instrument.