Built for black hat.Working for you.
A custom model, fine-tuned on datasets no one else can get access to, attacks your systems the way real adversaries would. A second model fixes what it finds. Then the attacker checks the fix holds.
Continuous Adversarial Verification for banks, payments, crypto and insurers. 24/7, inside the scope you authorize.
Attackers won’t wait foryour next security test.
AI makes sophisticated attacks easier to repeat. Annual assurance cannot protect a business that changes every day.
Test. Report. Wait.
The report describes yesterday’s systems. New code, integrations and access arrive tomorrow.
Defend. Challenge. Keep learning.
Continuous code defense and adversarial verification, working against the same changing business.
In financial systems,a software flaw becomes a business event.
An access-control failure is not just a technical score. It can expose money, confidential information and the trust the business depends on.
- Money moves.Payments and assets
- Who can approve a payout, change a destination or cross an account boundary?
- Information carries value.Identity and confidentiality
- Who can reach customer records, financial documents or privileged business data?
- Trust is operational.Continuity and accountability
- What happens to service, regulatory obligations and customer confidence when a control fails?
Security teams need evidence of business impact, not another unprioritized list.
One model attacks.The other protects.
Two model roles run continuously. One finds the path in, like an attacker would. The other checks code and changing systems, and closes the path out. Then the attacker challenges every fix, independently.
Adversarial verification
Attack
- Investigate reachable weaknesses.
- Chain them the way a real attacker would.
- Establish the potential business impact.
Continuous defense
Defend
- Check code and changing systems.
- Prepare and action remediation.
- Return each change for verification.
Both, in register
Verify
- Challenge the fix independently.
- Close it only when the path is gone.
- Carry the lesson into the next investigation.
Small weaknesses, chained into money.
Averith chains business logic: how access rules, APIs and money movements combine. Several findings that each look minor can add up to access to privileged accounts or funds. That is the risk signature matching alone does not show you.
- AST-031Session token accepted after role changeLow
- AST-036Sequential payout identifiers in a partner APILow
- AST-039Payout edit checks the account, not the ownerMedium
- AST-042Change another customer’s payout destinationCritical
Everything an attacker brings.Working inside your scope.
An assistant answers questions. Averith acts like an adversary: specialist agents probing an estate in parallel, chaining what they find, and handing every path to a defender that closes it.
Live simulation of a synthetic estate. Red agents attack and chain; green closes and verifies.
A custom model, fine-tuned on datasets no one else can get access to.
Non-public and dark-web intelligence, historical hacks and exploit behavior, and our own research and outcomes. Shaped by how real systems fail, not by what is on the open internet.
Tooling that lets it act like an attacker, not just answer like one.
Specialist agents investigate in parallel. A separately fine-tuned decision model reads the evidence for each vulnerability class and chooses the next move: test, chain, fix or verify.
Systems that keep it current, and keep it remembering.
New exploits are matched against your deployed estate as they surface. With memory on, every investigation starts from what Averith already learned in your environment.
Not another scanner.Not a once-a-year test.
How Averith compares with how each of the usual options typically works. Individual products vary.
| Dimension | Annual pentest | Scanners | General-purpose AI agents | Averith |
|---|---|---|---|---|
| The brain | A human team, for a fixed window | Rules and known signatures | A general-purpose model | A custom model fine-tuned on datasets no one else can get access to |
| How often | Usually once or twice a year | Scheduled or continuous scans | On demand or on a schedule | Always on, 24/7 |
| What it finds | What fits in the engagement window | Mostly known vulnerability patterns | Exploitable bugs in what you point it at | Business-logic chains into money and privileged access |
| Who fixes it | Your team, from a report | Your team, from a ticket queue | Your team, often with a suggested fix | A defending model prepares and actions the fix, with your approval or within your permissions |
| Proof the fix holds | Usually the next test | The next scan | A retest, often on request | The attacking model challenges it, independently and continuously |
| What it keeps | A report | Scan history | Varies by tool | Customer-scoped memory of what worked, what was blocked and why |
The exposure is financial.Not merely technical.
About $30 billion: aggregate potential financial exposure from vulnerabilities we found and reported, each weighed by what an attacker could reach.
- Business-critical findings
- 100+
- Technology environments tested
- 80+
- Retained fixes verified closed
- 95%
Anonymized cases
Evidence under NDA
A live, unauthenticated path into business APIs on a national-scale estate. The same class of weakness at a top-5 bank, a top-10 exchange, a national payments rail and international processors.
PHP2Shell: identified and patchedin two minutes.
When PHP2Shell leaked, Averith identified and patched deployed environments within two minutes of the announcement. Intelligence, exposure and patch worked as one loop.
Know the attack
Track new exploits, attack patterns and non-public intelligence.
Find the exposure
Find which deployed environments the new issue reaches.
Close the path
Prepare and action the fix within agreed permissions.
Prove it holds
Challenge the fix, then keep what is learned.
See the risk. Follow the agents.Control the action.
- Business impactSee the estimate and its basis, not just a severity score.
- Agent visibilityFollow active agents, new specialists and their work.
- Human controlInspect evidence before approving a change.
Human-in-the-loop by choice.Autonomous within agreed boundaries.
You choose where a person must approve, and where Averith can act without waiting for one.
| Stage | Human-supervised | Autonomous |
|---|---|---|
| Investigation | Agents investigate within the approved engagement. | Agents investigate continuously within the approved engagement. |
| Remediation | A person reviews the evidence and approves the proposed action. | Agents action fixes within your pre-authorized permissions. |
| Verification | The adversarial side checks whether the approved fix holds. | The adversarial side checks the change and continues the loop. |
| Accountability | Human decisions remain part of the evidence trail. | Autonomous actions remain part of the evidence trail. |
Autonomy changes who approves an action. It does not remove the scope.
Security that remembers.Protection that gets smarter.
The advantage is current intelligence and accumulated understanding, not access to a generic model.
A separate model decides what to do next.
Finding a weakness is one task. Choosing the next action is another. A separately fine-tuned decision model focuses on specific vulnerability classes: what the evidence means, what matters next, and which test, fix or verification to run.
Memory of working with you, not just the latest prompt.
With memory enabled, Averith brings relevant lessons from earlier work into new investigations in your environment.
What carries forward with customer memory Area Starting cold With Averith memory Approaches Rediscover setup and investigation patterns. Bring relevant operational lessons into the next investigation. Obstacles Repeat approaches that were already blocked. Use prior constraints to inform the next attempt. Guidance Keep working from an outdated lesson. Replace earlier guidance as new experience is recorded. Memory is opt-in and scoped to each customer. Prior lessons guide an investigation; they never replace fresh evidence or expand authorization.
Banks, payments, crypto and insurance.Africa and the Middle East first.
Built in South Africa, against some of the most demanding financial systems on the continent. If it works here, it travels.
- BanksPayouts, account boundaries and privileged access.
- Fintech and paymentsAPIs and money movement between partners.
- Wealth platformsCustomer assets and confidential records.
- CryptoCustody, withdrawals and exchange logic.
- InsurersNow holding the identity, data and payments banks carry, as insurance and banking converge.
How an engagement starts and grows
- Authorized discovery
Prove
A scoped, authorized engagement produces concrete findings and evidence.
- Executive case
Business case
Evidence is translated into business impact for the executive buyer.
- Integration
Deploy
Forward-deployed engineers integrate Averith into your environment.
- Contract
Always on
An annual enterprise contract for a deployed 24/7 managed service.
- Growth
Expand
Add systems, business units and group companies as value is demonstrated.
Built by people who havedone this work.
Averith is built in South Africa by security and fintech practitioners who have spent their careers inside the systems they now protect: banks, payment platforms and exchanges.
We work with security leaders who need proof that matters to the business, and with partners who can help us bring it to more institutions.
For investors
Averith is raising to turn proven capability into enterprise contracts. Capital goes to two priorities:
- 1Compute, model training, evaluation and infrastructure.
- 2Forward-deployed engineers who integrate Averith inside clients and expand adoption.
See what an attacker can reach. Then watch it close.
A briefing walks your security and executive teams through how an authorized proof engagement works on your systems.