Status and evidence
Avallo is a prototype, under active pilot in Australia in its design phase (begun October 2026). It is pre-revenue; no paying customers. This page sets out what is built, how it is tested, what is not yet shown, and how a pilot would prove the rest.
What is built, what is designed, what is next
Under active pilot in Australia (design phase)
Avallo is under active pilot in Australia, in its design phase (begun October 2026).
Built and tested
- The enforcement core, built to production standards
- The conformance suite
- Formal safety models
- The independent verifier
- Reproducible builds
Designed, built during the first pilot
- The limits workbench
- Approval and monitoring screens
- The policy drafting assistant
- Bank and NPP integration (designed, validated during the first pilot)
Roadmap, not built
- Merchant categories and per-purchase approval
- A gated provider edge for payment-provider flows
- Card issuer authorisation
How the enforcement core is tested
619 of 674
applicable cases pass in a 725-case conformance suite. The other 55 await payment-rail and distributed fault-tolerance work.
44 of 44
configurations in which formal mathematical models check the safety properties, all passing.
121 of 121
deliberately broken versions of its rules caught by the test suite.
- More than 250 deliberate faults caught across the build.
- An independent verifier recomputes every decision byte for byte.
- Builds are reproducible.
- An independent red-team review is complete. Its findings are being addressed.
What these results show, and what they do not
They show that the enforcement core applies its rules as specified under internal test, including when the rules are deliberately broken. They are internal results, not an external certification, and each figure describes a different check. They do not yet show Avallo running inside a bank's systems or on a payment rail. The 55 outstanding cases cover payment-rail and distributed fault-tolerance work, and the red-team findings are still being addressed. The screens and the drafting assistant are designed but not built. The pilot is where these are proved.
The pilot
Avallo is ready for a scoped, paid pilot within 90 days, hosted in Australia. It covers one consequential workflow, limits mapped from the organisation's policies, the approval and monitoring screens, and integration by API. It completes the payment-rail and fault-tolerance work, builds the limits workbench, approval and monitoring screens and drafting assistant, and starts in shadow mode alongside existing controls. Delivery depends on an agreed workflow, bank integration access and named delivery resources; the pilot fee, named delivery capacity and bank dependencies are agreed before commitment. Live payment release needs separate bank approval.
Design
Choose the workflow and map its limits from existing policies and delegations.
Shadow mode
Avallo runs alongside existing controls. Nothing is released until the organisation approves.
Prove value
Deliver the approval and monitoring screens, then measure the results.
Proposed measures, in shadow mode
- Share of requests that would proceed, require approval or be refused
- Estimated review effort avoided
- Time to reconstruct a decision
- Decision latency against the bank's tolerances
Compare decisions with the bank's expected outcomes. Also test incorrect decisions and outage recovery.
What the pilot must establish for the bank
Proposed acceptance conditions. Avallo does not by itself establish compliance.
- Operational risk (CPS 230). Validate payment release, replay handling and recovery after disruption, and agree the response when authority cannot be established.
- Security (CPS 234). Review red-team remediation, and agree access, incident handling and responsibility.
- Scams Prevention Framework and AFCA. For later business-customer workflows, assess how decision evidence supports relevant Scams Prevention Framework controls and AFCA investigations. The own-purchasing pilot tests the decision record, including a refused changed-payee request.
- Data, suppliers and privacy. Document hosting, support access and the model provider, and show how decision evidence supports the bank's automated-decision disclosures under the Privacy Act.
Who is building it
TrustWorks360 is a Melbourne company, operating since 2019, delivering data, privacy and AI governance solutions. It leads Avallo's productisation in Australia: adapting it to financial services, mapping policies into enforceable limits, bank system integration, regulatory mapping for the Scams Prevention Framework and APRA standards, and Australian hosting. Avallo will be commercialised through a planned majority Australian-owned joint venture.
Questions reviewers ask
Does Avallo use AI to decide whether an action goes ahead?
No. No language model makes the runtime authorisation decision. Decisions are deterministic rules: the same request under the same limits gets the same answer every time.
What happens if Avallo cannot confirm an action?
It fails closed. If authority cannot be established, the action does not proceed.
Does the agent hold banking passwords or keys?
No. The agent holds no reusable credentials. It proposes actions, and each permitted action needs a single-use Warrant. In a payment deployment, the bank integration must prevent release without a Warrant; the pilot validates this.
Where does Avallo run, and where is data held?
The proposed hosting is dedicated infrastructure in Australia, operated by or for the customer, with Australian data residency by default; operator, model and support-access arrangements are agreed with the bank. The control path uses agent identifiers, not customer identities, and holds no passwords, keys or reusable tokens. Handling of policy documents, approvals, evidence and support access is agreed with the bank.
How does it connect to our systems?
Through one API call in the execution path, before any action takes effect. Avallo is designed for integration with different agent systems; the first pilot validates the connection at the bank's payment release.
Is anyone using Avallo today?
Avallo is a prototype and pre-revenue; no paying customers. It is under active pilot in Australia, in its design phase (begun October 2026). We are seeking a first pilot with an Australian financial institution.
Start with one workflow
Avallo is ready for a scoped, paid pilot within 90 days: one consequential workflow, hosted in Australia. The pilot completes the remaining core work and builds the limits workbench, approval and monitoring screens and drafting assistant.