Skip to content

Security testing for AI agents and voice agents.

Hands-on testing of LLM features, RAG, agents, MCP tools and phone agents, before your customer's security review. Fixes arrive as pull requests your engineers review and merge.

Signs every report
Named lead tester
For example 4 of 20
Reproduced as a rate
Within 90 days
Retest included
Reported the same day
Critical findings

Mapped to the standards your buyers check

  • OWASP LLM Top 10
  • OWASP Agentic Top 10
  • MITRE ATLAS
  • SOC 2
  • ISO 27001
  • CSA AICM
  • HITRUST AI
  • PCI DSS 11.4

Services - Testing for the parts of your product that talk, act and remember

Scanners are good at the standard web checklist. The risk in an AI product sits in chains: injected text, an agent decision, a tool call, another customer's data. That is the part we test by hand.

AI agent security test

From $6,500AI agents

Your agent can call tools. We find out who else can make it.

Hands-on testing of LLM features, RAG, agents and MCP tools. We follow injected instructions all the way to a tool call and check what leaks between your customers.

Learn more

Voice agent security test

From $8,500Voice agents

We call your agent and test what a caller can make it do.

We phone your AI agent, try to break it, and check the parts a simulated caller cannot see: recordings, tool authorization, telephony and consent.

Learn more

SaaS review with fix pull requests

From $6,500SaaS review

Proof that one customer can never see another.

A multi-tenant security review for Next.js, Supabase and Firebase apps. Every confirmed finding ships with a pull request your engineers review and merge.

Learn more

After the test: SOC 2 readiness and a fractional security lead for the same team.

How it works - Scope, test, fix and retest

Everything in writing, with dates. You always know what we test and what we must never touch.

/ 01

Scope

You answer six questions in writing and we send a written quote within one business day. No discovery call is required, though we are happy to have one.

/ 02

Test

A certified tester, named in your proposal, works through your AI features, agents, phone agents and tenant boundaries by hand. Scanners cover the standard list so human time goes to chains and business logic.

/ 03

Fix and retest

The report arrives within three business days of the last testing day, together with fix pull requests for confirmed findings.

A security test is only worth what your customer's reviewer accepts. We write every finding so it can be reproduced, fixed and retested.

Lukas Čeponis, Founder

What you get - Evidence your customer's security reviewer can accept.

Not a list of scanner output. A report written to be sampled, fixes your engineers can merge, and a letter you can send.

  • A report your auditor can sample. Scope, method, dates, every finding with severity, proof and the exact fix. Written so an auditor can trace a finding from discovery to closure.
  • Fix pull requests. Confirmed findings ship with a pull request and a regression test. We open them from a fork or a branch you protect, your engineers review and merge, and we never hold merge or deploy rights.
  • Free retest within 90 days. A tester who did not write the fix confirms it holds, and the report is updated with before and after evidence.
  • Signed attestation letter. A one page letter for your customers and investors, signed by the lead tester, with an ID your customer can check with us.
  • Questionnaire answers. We answer the pentest and AI lines of the questionnaire your customer sent, each one pointing to the part of the report that proves it.

Independent by design - We write the fix. You stay in control.

Fixes as pull requests close findings fast. These rules keep the evidence independent, and they are written into every scope.

  • Independent. You review and merge every fix. The person who wrote a fix never retests it, and the letter states who wrote it.
  • Evidence first. Every finding is reproduced before it reaches the report. We write what the evidence proves and what it does not.
  • Scope before invoice. The price is agreed in writing before we start. If the scope changes, we agree the change in writing first.
  • No guarantees we cannot keep. A test is a point in time review of an agreed scope. We never promise that nothing can go wrong.

Pricing - Between a scanner and a large firm

Starting prices are on the pricing page. Your price is agreed in writing before we start.

Automated pentest tools

$1,500 to $4,000

Fast and cheap. Strong on the standard web list, weak on agent chains and business logic.

Wardkey

$6,500 to $12,000

A certified tester named in your proposal, fixes as pull requests, retest and a signed letter.

Large human-led firms

$10,000 to $16,000+

Deep, but quoted, slower to start and rarely write your fixes.

Who tests your product

  • Certified testers

    Every test is led by a certified tester. You see the name and certification in your proposal, before you sign.

  • Named on the report

    The lead tester is named on the report and signs the attestation letter on behalf of Wardkey LLC.

  • Same lead, start to retest

    One lead tester stays with your test from the first day to the retest. Fixes are retested by a tester who did not write them.

Evidence from our team's previous work

Our team's previous work. Client names stay private, the numbers come from the engagement record.

A full audit of a multi-tenant voice and chat AI platform

Security and compliance audit

A production platform where businesses run AI phone and chat agents for their own customers, with telephony, payments and thirteen CRM integrations.

Read more

Two critical cross-customer bugs in a B2B SaaS

Grey-box penetration test

A B2B platform used by 340 business customers, tested with partial access (grey box).

Read more

FAQ - Questions buyers ask

Will my SOC 2 auditor accept your report?

Auditors look for scope tied to your systems, a named method, dated testing, findings with severity and evidence that fixes were retested. Our reports are written to that list.

Who writes the fixes, and how do you stay independent?

We open pull requests from a fork or a protected branch, your engineers review and merge them, and a tester who did not write the fix retests. The attestation letter says who wrote each fix.

Do you test production?

We start with staging or dedicated test tenants. Production is tested only with your written risk acceptance.

Where are you based?

Wardkey LLC is a United States company. Testing is performed from the EU. We do not take work that requires US-person testers, such as FedRAMP, CJIS or ITAR scope.

How long does it take?

Most tests start within two weeks of the signed scope and take four to eight tester days. The report follows within three business days.

What if you find nothing?

Then the report says exactly what was tested and how, which is what your customer's reviewer needs to see.

Latest research

What voice agent platforms leave to you

October 12, 2026

Three defaults to check before your AI phone agent goes live: recordings that never expire, caller identity and tool authorization.

Read more

Testing tenant isolation in RAG systems

October 5, 2026

Why a vector store shared by all your customers needs the same isolation tests as your database, and how we run them.

Read more

Send us the questionnaire your customer sent.

We will tell you which lines a test answers, in writing, within one business day.

Who we are

  • CompanyWardkey LLCWyoming, United States
  • TestingPerformed from the EUFor clients in the US and Europe