Frequently asked questions

The questions buyers ask most often before a 30-Day Finding. Cross-references link to the source page: security controls at /security, the substrate inventory at /integrations, the pipeline at /methodology.
LAST UPDATED: July 9, 2026

For investors

What does Zamski do?

Zamski shows you what you are buying before you wire the money, and whether the story still matches every quarter after. Technical due diligence from the target company's operating history, not the snapshot assembled in a data room.

What sits in a Zamski report?

Every sealed report states what the record confirmed, what it contradicted, and what we could not observe. Every claim resolves to a specific artifact in the target's own systems.

How is Zamski different from a data room review?

A data room is a snapshot assembled by the seller. Zamski reads what the company created without knowing anyone would one day examine it. Code, messages, tickets, calendars, AI sessions. Read together, they become a record no prompt can recreate.

Who is Zamski for?

Private equity and venture deal teams running technical diligence, and fund CFOs who route to them. Post-close monitoring on portfolio companies and pre-sale prep are the two adjacent motions.

Access and data

What access does Zamski need?

Read-only OAuth on the source systems that produce the substrate signal. Zamski requests the minimum scope on every integration and holds no write permission on GitHub, Slack, Jira, or calendar sources. Details at /security.

What systems does Zamski read?

Five categories of source: code activity, task and project state, conversation patterns, calendar density, and customer signal. The connector list per category is on /integrations. How the signals combine into a brief is on /methodology.

How long is data retained?

30-Day Finding data is deleted 30 days after delivery, or sooner on request. Pilot data is deleted on pilot close. Subscription data retention is defined per DPA. See /security.

Can we delete our data?

Yes. Write to eli@zamski.com and deletion runs against the org's substrate. The 30-day retention window is a ceiling; earlier deletion is honored on request.

Is customer data used to train models?

No. LLM calls run as inference only. Customer content is not used to fine-tune any model.

Security and compliance

Is Zamski SOC 2 audited?

Zamski completed a SOC 2 Type II audit performed by Sensiba LLP. Audit period December 17, 2025 through March 18, 2026. Continuous controls monitoring runs through Vanta; controls detail lives on the trust center.

Where is data processed?

Primary hosting is AWS. Region residency and LLM subprocessor detail are documented at the trust center.

Do you support government or CUI workloads?

Not yet. Authority-to-operate posture, CUI and PII handling, contract vehicles, and FedRAMP posture will be published as Zamski, Inc.'s SAM.gov registration completes and initial pilot engagements land. Direct inquiries welcome at eli@zamski.com. See /government for the current posture.

Product

How is Zamski different from AI workflow platforms, or from running an AI coding agent ourselves?

Zamski does not accelerate work. It produces the executive read on how the work is progressing, with citations back to the substrate. Language models translate verified evidence into readable prose. They never decide what is a fact, and never decide whether two facts corroborate.

Verdicts on a claim are rule-driven, and the rules split by direction. Positive verdicts belong to the substrate: zero supporting facts reads not-found regardless of the model's opinion. Negative verdicts (contradicted, out-of-scope, not-found) follow the verifier, a language-model read of the retrieved evidence pool; it can conclude that the retrieved facts do not support the claim, and that conclusion stands even when candidate facts exist. Detail at /methodology in the "Where the language model sits" section.

What does a brief look like?

Sample briefs are on the landing page, one per illustrative company. Every fact in a sample brief carries a citation to its underlying artifact. All numbers are illustrative; none of these are real customers. Open one at zamski.com/#sample-briefs.

How fast is the first finding?

The 30-Day Finding is one executive-grade read on the engineering organization, delivered free on real customer data. Details at /30-day-finding.

What does it cost?

Subscription pricing is scoped to organization size and DPA terms. Write to eli@zamski.com for a quote.

Something else?

If your question is not here, write to eli@zamski.com.

© 2026 Zamski, Inc. · Veteran owned · SOC 2 Type II attested.

Denver, Colorado.

Cookies

How Zamski uses cookies

Zamski uses strictly necessary cookies to operate this website. We also use one optional analytics cookie (PostHog) to understand how visitors arrive and which pages they read, so we can write better. We do not use advertising or targeting cookies, and we do not sell visitor data.

You can accept analytics, decline them, or tailor your preferences. You can change this any time from the Cookie settings link in the footer. Read the Cookie Notice for the full detail.