Evidence before interface
We build the evidence path first and the screen on top of it. A number without a source is a liability, and an alert nobody can interrogate gets muted within a month.
About Aureza Labs
One team, from sketch to production.
We build software that solves operational, financial and communication problems — and AI that explains causes rather than only detecting events. Fifteen products, ten industries, one standard.
What we actually do
We take the awkward projects — the ones with a warehouse, a regulator or a plant floor attached.
Consumer apps are well served. What is underserved is the operational middle: a recycling facility running on paper travellers, a NOC drowning in alarms, a quality unit reconstructing an investigation from four disconnected systems.
Those projects share a shape. There is real-world data nobody has correlated, a legacy system that cannot be replaced, an environment hostile to software, and a user who will abandon the product in a week if it slows them down. We have built fifteen of them, and the patterns repeat.
Audit trailIMMUTABLE
09:41 · retrieved SOP-4471 rev CSYSTEM
09:44 · hypothesis proposedSYSTEM
11:02 · hypothesis rejectedQA-114
11:26 · determination signedQA-007
Weeks to daysEvery claim sourced
BatchResolve · audit trail In a regulated environment every retrieval, proposal and acceptance is recorded immutably — designed to be handed to an inspector rather than reconstructed for one.
How we decide
Six positions we hold
These are not values on a wall. Each one has cost us work at least once, which is roughly how you tell a position from a slogan.
Scope is subtraction
The most valuable thing discovery produces is the list of what we are not building. Every feature that survives has to earn its place against the ones we cut.
Design for the environment
Gloved hands, poor signal, steel racking, night shifts, a screen in direct sunlight. The environment is a requirement, not a footnote.
You own the result
Source, infrastructure, documentation and pipeline are yours from the first commit. We would rather be re-hired than be difficult to leave.
Say the uncomfortable thing early
If a project should not be built, or a chain is not the answer, or the data is not there yet, we say so in week two rather than month six.
Ship, then keep shipping
Launch is a stage, not a finish line. The products we are proudest of are the ones still getting better three years later.
The team
Eight disciplines under one roof
No subcontracting, no handover between agencies. The people who designed it are the people who build it and the people who deploy it.
Product design & UX
Flows, prototypes and design systems — including the empty, error and offline states most teams skip.
Mobile engineering
React Native and native iOS and Android, built offline-first where the environment demands it.
Frontend engineering
React and TypeScript, accessible to WCAG 2.2 AA and held to performance budgets in CI.
Backend & platform
APIs, data models, tenancy and permissions, designed to survive the second and third customer.
Data engineering
Pipelines, warehouses and reconciliation, so the reporting layer agrees with the source systems.
Applied AI & vision
Multimodal models, retrieval and evaluation harnesses — always with the evidence path attached.
Infrastructure & edge
Cloud, on-premise and industrial edge deployment, defined as code and handed over in full.
QA & release
Automated suites, device matrices, load testing and staged rollout with a rollback plan.
Start here
Tell us what you run.
Describe the operational problem in a paragraph. We will reply within two business days with what we would build, roughly what it costs, and what we would cut.