Testing and defence led by a published security researcher with five CVEs, including a CVSS 9.1 Mirai botnet kill-switch.
All security →SOC 2, ISO, and the Canadian privacy stack, run end to end with an independent auditor.
All frameworks →Original research, free tools, and plain-language guides on security and compliance, from a published security researcher.
Read the blog →SOC 2 for US founders and operators. The industry-standard SOC 2 Type 1 timeline is 90 to 150 days. We deliver in 75 by combining traztech’s control playbook, a partner readiness assessment, and a vetted CPA partner. Pricing undercuts Big 4 readiness engagements by 50% or more. We back readiness with auditor management and advocacy once the audit starts, and can layer on vulnerability management if continuous scanning needs to be part of the evidence.
The obvious question first: does it matter that we are Canadian. For this work, no, and the reason is that the frameworks are American to begin with. SOC 2 is an AICPA standard. HIPAA and PCI DSS are US regimes. ISO 27001 is international. None of them are Canadian instruments that need adapting at the border, and none of them care where your readiness partner is incorporated.
What does matter is who signs the report, and that is never us wherever we are based. A SOC 2 report is issued by a licensed CPA firm that must remain independent of whoever prepared you. We work with US audit firms regularly, we will introduce you to one, and the separation between preparation and attestation is the same on both sides of the border.
On reach: we run engagements across US time zones and we have people in Windsor, directly across the river from Detroit, which is one of the busiest commercial borders in North America. For Michigan and the Midwest that means same-day in person. Everywhere else it means the ordinary remote working most compliance engagements now use anyway, because evidence collection and control review do not require anybody in a room.
The one place our nationality is genuinely relevant is when you have Canadian exposure too. If you hold data on Canadians, PIPEDA applies, and Quebec Law 25 applies to anyone handling the personal information of people in Quebec regardless of where they are established. Most US firms treat that as an edge case. We do not, and running it in the same programme is cheaper than discovering it later.
The service itself is the same everywhere. Fixed scope, fixed price, and the same team. What changes by region is which requirement binds first and who is asking. The full detail is on the soc 2 compliance page, and prices are on the pricing page.
US enterprise buyers are the reason most of our clients need SOC 2 in the first place. The shape of it is always the same: a company wins real interest from a US enterprise, a vendor-security review lands in the middle of the deal, and everything parks until there is a report to hand over. The bar here is set by the buyer, not by a regulator, which is why it shows up as a questionnaire and a procurement gate rather than as a law you can look up.
We are a Canadian firm and we work with US clients cross-border, across US time zones. We do not keep a US office, and we are not going to pretend otherwise. What we do instead is coordinate around how you actually work, and establish presence for the length of the engagement where the work calls for it. What we bring is specific, repeated experience getting companies through US enterprise security review: what the questionnaire is really asking, which controls the reviewer actually checks, and what has to be true before the deal moves. We prep you to pass. Only an independent CPA firm can sign a SOC 2 report, and we will introduce you to one.
The industry-standard SOC 2 Type 1 timeline is 90 to 150 days. We deliver in 75 by combining traztech’s control playbook, a partner readiness assessment, and a vetted CPA partner. Pricing undercuts Big 4 readiness engagements by 50% or more. We back readiness with auditor management and advocacy once the audit starts, and can layer on vulnerability management if continuous scanning needs to be part of the evidence.
For the full service detail, see the SOC 2 Compliance page. For fixed-price productized engagements, see pricing.
We do. traztech is a Canadian security and compliance firm working with startups and SMEs on SOC 2 Compliance, led by a published security researcher with six disclosed CVEs. Engagements are fixed scope with published pricing, and the first call is free. The SOC 2 report itself is issued by an independent licensed CPA firm. We prepare you, run the programme and sit in the audit with you. We do not issue the report, and no readiness firm can.
The obvious question first: does it matter that we are Canadian. For this work, no, and the reason is that the frameworks are American to begin with. SOC 2 is an AICPA standard. HIPAA and PCI DSS are US regimes. ISO 27001 is international. None of them are Canadian instruments that need adapting at the border, and none of them care where your readiness partner is incorporated. What does matter is who signs the report, and that is never us wherever we are based. A SOC 2 report is issued by a licensed CPA firm that must remain independent of whoever prepared you. We work with US audit firms regularly, we will introduce you to one, and the separation between preparation and attestation is the same on both sides of the border. On reach: we run engagements across US time zones and we have people in Windsor, directly across the river from Detroit, which is one of the busiest commercial borders in North America. For Michigan and the Midwest that means same-day in person. Everywhere else it means the ordinary remote working most compliance engagements now use anyway, because evidence collection and control review do not require anybody in a room. The one place our nationality is genuinely relevant is when you have Canadian exposure too. If you hold data on Canadians, PIPEDA applies, and Quebec Law 25 applies to anyone handling the personal information of people in Quebec regardless of where they are established. Most US firms treat that as an edge case. We do not, and running it in the same programme is cheaper than discovering it later.
No. We are based in Toronto and work with companies across Canada and the United States. Readiness work is largely remote by nature: evidence, policies and control design do not require anybody in the room. Where physical and environmental controls are in scope, for example a data centre or an office in the audit boundary, we attend on site. We have run a dual-framework programme across three physical sites, so that scope is familiar rather than an exception.
Our pricing is fixed and published rather than quoted per city, because the work does not change with the postcode. What moves the number is scope: how many systems and sites are in the boundary, how much already exists, and how many frameworks you are running at once. The audit or assessment fee is separate and is paid to the independent firm that performs it. Every price we charge is on our pricing page.
It depends on the framework and on how much of the programme already exists. Our SOC 2 track runs on a 75-day readiness window and our ISO 27001 readiness track runs 16 weeks, both of which assume you can give the work real attention. A Type II adds an observation period on top, typically three to twelve months, because the auditor has to watch the controls operate. We will give you a realistic date on the first call rather than the one you want to hear.
Yes, and we frequently do. We manage the relationship, handle evidence requests and represent you through fieldwork. Where you have not chosen one, we run the selection: on one engagement, setting out a documented readiness position and confirming a prep firm took $11,000 off the quote, and across four firms bidding identical scope the highest number was 2.1 times the lowest.
Book a free 30-minute discovery call. We’ll tell you whether this engagement fits, what it would cost, and when we could start.
Book a callEvery readiness programme needs a control library, an evidence register, policies and a score for the board. Being quoted five figures a year for that is normal. Paying it is not.
| 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 | $11,000 off a five-figure quote on one engagement, for a documented readiness position | Nothing. The audit firm prices your readiness, not your tooling |
Pricing in the right column is what compliance automation platforms are publicly reported to charge; none of them publish a number, so treat it as a range rather than a quote. The $11,000 came off the audit firm's own number once the readiness position was documented (the engagement). Where a paid platform is the better buy, and the fuller comparison, is on the Workspace page.
Track record
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.
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 across 76 controls with zero exceptions, on a team of 15.