Our team

Five backgrounds. One view of risk.

Our team comes from agentic AI, banking, regulated industries, chip making, and software development. Each of those fields learned, often the hard way, how to let powerful systems act without losing control of them.

That mix is why our approach is different. We understand the technology, how enterprise products are actually built and bought, what regulators and auditors expect, and where hardware sets the limits.

Five backgrounds on the team, agentic AI, banking, regulated industries, chip making, and software development, combine into the AgentTrustCore platform.

Where we come from

What each field taught us, and where you see it in the product

  1. Agentic AI

    Built and broke autonomous agents

    What we learned there

    We have shipped agents that call tools, chain decisions, and act without a person in the loop. We have also watched them fail: prompt injection, runaway tool loops, and confident actions on wrong assumptions.

    • Agents fail at the action, not the answer
    • Prompt-level guardrails are easy to talk around
    • Behaviour drifts with every model and prompt change

    What it changes in AgentTrustCore

    TrustCore checks the tool call itself, outside the model, so a manipulated prompt still cannot reach a system it is not allowed to touch.

    See it in TrustCore
  2. Banking

    Ran systems that move money

    What we learned there

    In banking, no single person can approve their own payment. Limits, maker-checker approvals, and segregation of duties exist because mistakes are expensive and fraud is constant.

    • Every action needs an owner and a limit
    • Approvals scale only when routing is automatic
    • Model risk is reviewed like any other risk

    What it changes in AgentTrustCore

    Agents get the same treatment as staff: scoped authority, amount thresholds, and escalation to a named approver when a request goes above them.

    See it in Enterprise Agents
  3. Regulated industries

    Answered to auditors and regulators

    What we learned there

    In healthcare, insurance, and financial services, being right is not enough. You must show who did what, under which rule, and that the rule was approved. Evidence is the product.

    • If it is not recorded, it did not happen
    • Policies need version history and sign-off
    • Audits arrive months after the decision

    What it changes in AgentTrustCore

    Every decision is written to a signed, append-only evidence ledger, and policies are versioned so you can prove which rule applied on any given day.

    See it in Evidence Center
  4. Chip making

    Verified silicon before tape-out

    What we learned there

    You cannot patch a chip after it is manufactured. Semiconductor teams verify exhaustively before release, test against tolerances rather than happy paths, and treat a missed edge case as a recall.

    • Verify before release, not after incidents
    • Measure against tolerances, not averages
    • Hardware limits are real budgets

    What it changes in AgentTrustCore

    Veridict runs agents through test suites before they ship and blocks releases that fall outside tolerance. PrivateStudio is sized to run on your own hardware with a tight latency budget.

    See it in Veridict
  5. Software development

    Shipped developer platforms at scale

    What we learned there

    Security that slows engineers down gets switched off. The tools that last fit into existing code, CI pipelines, and on-call routines with almost no ceremony.

    • Adoption is a product feature
    • Policies belong in version control
    • Start in observe mode, then enforce

    What it changes in AgentTrustCore

    TrustCore installs with a few lines of SDK code or a gateway, keeps policies as code, and lets teams watch decisions before switching enforcement on.

    See it in Documentation

Where the backgrounds meet

The best ideas come from two fields at once

Few teams have a bank risk officer and a chip verification engineer in the same design review. These are some of the features that came out of those conversations.

Banking+Agentic AI

Agents with spending limits

A refunds agent can approve small amounts on its own. Anything larger goes to a finance approver, exactly as it would for a new employee.

Regulated industries+Software development

Compliance that lives in the repo

Policies are reviewed in pull requests, and each merge becomes an audit record. Engineers and auditors look at the same history.

Chip making+Agentic AI

Release gates for agent behaviour

A new prompt or model version is tested like a new chip design. If it regresses on safety tests, it does not ship.

Chip making+Regulated industries

Running where the data lives

Some customers cannot send data to a cloud model. PrivateStudio and the self-hosted control plane run inside their own data centre.

Bring your background to the team

We hire people who have run real systems under real constraints.