Loading…
What we build
These are the areas where Devx has technical expertise. They aren't services for sale: they are the foundation on which we build our own products.
Not every area has a public product today — when one does, it will be listed here.
Building and integrating AI models for specific problems — chosen for the task, not for the trend.
Problems we care about
How we approach it
We start from the task and the success metric; the model is an implementation decision. Where mistakes are costly, there is human review and continuous evaluation of the results.
Techniques and tools
OCR, classification, extraction, anonymization and document understanding.
Related products
No public product in this area yet. It's an expertise we use inside our other products.
Problems we care about
How we approach it
We treat a document as two layers — content and geometry. Understanding the structure comes before transforming the text; that is what makes it possible to return a usable document rather than a wall of text.
Techniques and tools
Tools that eliminate manual, repetitive processes.
Problems we care about
How we approach it
Automation starts with understanding the process as it really is, exceptions included. Automation that fails silently is worse than manual work — so every workflow has logging, reprocessing and alerts.
Techniques and tools
Complete products delivered over the web, with ongoing maintenance and improvement.
Problems we care about
How we approach it
A SaaS product doesn't end at launch. We design for whoever will be operating the system at three in the morning: reversible deploys, safe migrations and telemetry from day one.
Techniques and tools
Architectures that put data protection and control first.
Problems we care about
How we approach it
Privacy is decided before the code: which data, for how long, where, and who has access. Those answers become architecture requirements, not a policy page written at the end.
Techniques and tools
Billing, reconciliation and financial management built on Brazil's payment infrastructure.
Problems we care about
How we approach it
Money demands the same rigor as sensitive data: idempotent operations, reconciliation as the rule and no automated action without an audit trail. Whenever possible, money goes straight to the customer's account — with no custody in between.
Techniques and tools
Tools built for developers and technical teams.
Problems we care about
How we approach it
A good technical tool disappears into the workflow. We prioritize stable contracts, error messages that explain what to do, and documentation written for people in a hurry.
Techniques and tools
To avoid confusion
Being clear about what we don't do saves everyone time — including yours.
Agency
We don't build websites, campaigns or made-to-order projects.
Software house
We don't sell development hours or staff out teams.
Generic consultancy
We don't sell assessments; we build products that solve the problem.
Outsourcing
We don't run other companies' operations for them.