A fixed-price gap analysis, remediation through to your audit, and upkeep after it. All in a workspace you keep.
All compliance →Led by a published security researcher with five CVEs. One standard report, letters for your buyers, and retests of your fixes.
All security →To the people you sell to, raise from or answer to.
All industries →Original research, free tools, and plain-language guides on security and compliance, from a published security researcher.
Read the blog →If you ship an LLM or agent application, attackers are going to probe it with prompt injection, jailbreaks, and tool-abuse tricks. We red-team it first.
Delivered with our testing partners, global and Canadian, this is hands-on adversarial testing of how your model, prompts, and tools behave under attack.
Comparing providers? See how the Canadian penetration testing market compares.
You learn how your LLM or agent actually behaves under adversarial pressure (where it leaks, gets jailbroken, or misuses its tools), with a prioritized, reproducible list of fixes before an attacker finds the same holes.
Red teaming is open-ended adversarial testing focused on how the model and its guardrails behave: injection, jailbreaks, tool abuse. AI penetration testing is more structured, typically mapped against the OWASP LLM Top 10. Many clients do both.
It is delivered with one of our testing partners who specialize in offensive and adversarial testing including LLM red teaming. We work with both Canadian and global firms and put the one that gives you the best value on your engagement; for Canadian clients that usually means a local firm priced in CAD. You get that offensive depth plus our governance and remediation context.
Yes. Tool abuse and excessive agency are core to the test. Where a model can invoke functions or act on data, that is exactly where we push hardest.
A findings report with each issue’s severity, reproduction steps, and a concrete fix, so your team can remediate rather than just receive a score.
The price above covers the work. It also covers where the work lives, which most buyers are quoted separately as an annual platform subscription.
| traztech Workspace | Other GRC platforms | |
|---|---|---|
| Licence cost | $0. Free forever, no card, no paid tier | $7,500 to $50,000 a year, on an annual contract |
| Control library, evidence register, policy templates, risk register, vendor questionnaires, readiness scoring | Included | Included |
| What it costs inside an engagement with us | $0. You need a workspace either way | Unchanged. The subscription sits on top of the fee |
| What it does to your audit quote | A documented readiness position the audit firm can scope and price against | Nothing. The audit firm prices your readiness, not your tooling |
Platform pricing is a publicly reported range, since none of them publish a number. The fuller comparison, including when a paid platform is the better buy, is on the Workspace page.
Book a free 30-minute call. We’ll tell you whether it fits, what it costs, and when we can start.
Book a callNot ready to scope this yet? Open a free Workspace and score yourself against the framework first. It is the same register we work from during an engagement, so nothing you do there gets thrown away.
See what the Workspace does →Free PDFs, no card
SOC 2 readiness, ISO 27001 gaps, incident response and vendor security, as PDFs you can print or forward. Free, no card.
From Jacob Masse, principal of traztech: the files by email, then a few short notes over the next month. No spam, unsubscribe in one click.
Track record
We would rather show you the work than a wall of logos. Here is what is behind the advice.
Five published CVEs. CVE-2024-45163 (CVSS 9.1) is a flaw in the Mirai botnet itself, which gave defenders a way to shut down attacker infrastructure. CVE-2026-42626 takes HP ENVY 5000 printers offline from any unauthenticated device on the same network.
The printer is the one that matters on a compliance page: an asset nobody counts as a computer, on a flat network, downed by a device that never had to log in. Auditors ask how controls fail. We have found out first-hand.
At Humera, a venture-backed US security company, Jacob built the compliance programme in-house from nothing: no report, no policies, no documented controls. It ended in a Type II attestation with zero exceptions.
The platform stayed in production throughout, which is the part most readiness projects get wrong: controls are easy to design and hard to retrofit onto a system people already depend on.
For a Waterloo data centre operator we ran SOC 2 Type II and ISO 27001:2022 together rather than one after the other, across a production campus, an AI compute platform and a self-hosted collaboration stack. Scoped so further Ontario and Quebec sites enter as they reach production. Findings delivered and remediated.
For an Ontario medtech company putting an AI clinical assistant in front of practitioners, we ran the gap analysis and built the evidence programme behind their SOC 2.