What we have built and how it behaves in production
Six systems running for real customers. Each one states its actual maturity and what it does not solve.
A knowledge base that keeps company data inside
ProductionStaff ask in their own words and get an answer from internal documents, with a link to the source. The whole system runs on the customer's own server.
Web accessibility audit with a concrete list of fixes
ProductionAutomated checking of all 55 WCAG 2.2 level A and AA criteria, plus a vision model's assessment of whether the alternative texts actually say anything.
Seventy Windows machines, managed by a sentence
ProductionInstead of a console, an instruction in plain words. The agent proposes a plan, waits for approval, and only then acts — with signed updates and rollback.
Server access without anyone holding the keys
ProductionA jump box holds the SSH credentials; both the agent and the administrator work through an approved API. Linux infrastructure managed from a browser, with no keys on the laptop.
Three legacy systems, one question
ProductionA read-only layer over Firebird and MS SQL exposing named queries as JSON. The user does not need to know which system holds the data.
Leaving proprietary BI without losing the data
PilotMapping the flows inside Qlik and building an independent data layer on ClickHouse that can be queried in plain words.