Screenata

SOC 2 · HIPAA · ISO 27001

Compliance that gets done, not just tracked.

Vera, your AI compliance agent, collects evidence through APIs, screenshots, and guided procedures, follows up with owners, and signs every artifact for the auditor you pick. You review and approve.

See pricing
SOC 2HIPAAISO 27001ISO 42001GDPR

Animated product demo: Screenata scans your systems, assesses SOC 2 readiness, remediates gaps, collects your review and sign-off, and delivers a signed audit package to your auditor.

I really like… the focus on reducing manual work instead of just giving users another compliance dashboard to manage. The AI agent approach… feels more like having an assistant working with you instead of just showing you tasks.
GRC consultantUsing Screenata with clients
SOC 2 Type II program100%
  1. Scan
  2. Policies
  3. Evidence
  4. Gaps
  5. Pack
Ready for your auditor

From first scan to audit report.

Vera writes the policies, collects the evidence, works through the gaps with your team, and assembles a signed audit package. You approve; your auditor issues the report.

Typical platform$12–25K/yr

Screenata · per framework

$5,988/ year

Every moduleNo per-seat fees

One published price, every module.

$5,988 a year per framework, with no per-seat fees. Year one to SOC 2 Type II runs $22⁠–⁠33K all-in, versus $49⁠–⁠70K doing it yourself on Vanta or Drata.

okta-mfa.json

Jun 30, 06:00 · Okta API

CC6.1
SHA-256 · RFC 3161 · signed
Verified

A report your customers can trust.

Every artifact is mapped to a control, dated, and signed, so any auditor can verify it independently. When an enterprise buyer's security team reads it line by line, the proof holds up.

The difference

Other tools track the work. Vera does it.

A dashboard hands you one more list to manage. Vera works alongside you like an assistant: she scans, writes, chases, and files, and you approve what she did.

A GRC dashboardTracks the work
  • Write the Access Control PolicyYou
  • Collect Okta MFA evidenceYou
  • Follow up on overdue evidenceYou
  • Re-run the S3 encryption checkYou
  • Answer the prospect's security questionnaireYou
  • Assemble the audit packYou
Your part: all of it.
Screenata Does the work
  • Write the Access Control PolicyDone
  • Collect Okta MFA evidenceDone
  • Follow up on overdue evidenceDone
  • Re-run the S3 encryption checkDone
  • Answer the prospect's security questionnaireDone
  • Assemble the audit packApprove
Your part: review and approve.

01 · Policies

Scan first. Then write what you can prove.

Vera assembles context from GitHub, AWS or GCP, your IdP, and existing evidence before a single policy is written. The overpromise checker flags hard commitments unsupported by what she found, before your auditor does.

  • Policies grounded in real IAM policies, branch protection, and MFA settings
  • Overpromise detection, the #1 audit failure mode, caught at draft time
  • All 8 SOC 2 foundational deliverables, right-sized for startup teams
Access Control Policy · draft
2 flagged

Acme Corp enforces multi-factor authentication through Okta for all administrative access to production systems. verified

Production access is reviewed quarterly by the security team to remove stale entitlements. overpromise

Vera flagged this claim

No quarterly access review evidence found in the last 12 months across Okta and GitHub. Soften to "periodic reviews as needed", or commit to quarterly and let me schedule them.

Soften languageSchedule quarterly review

02 · Evidence

Automate evidence collection beyond APIs.

API integrations are table stakes and cover about 30–40% of a SOC 2. The rest lives in screens and walkthroughs that other platforms hand back to you as a to-do list. Screenata captures those too, and evidence collected once counts toward every framework it satisfies.

01

API Automation

Cloud, code, and identity providers scanned on a schedule. Every check maps to a control and is signed on arrival.

What every platform does.

Weekly scan

Providers

  • Okta
  • AWS
  • GitHub
  • Google Cloud
  • Datadog

Checks running

  • MFA enforced for admin accountssigned 6:00 AM
  • S3 default encryption on all bucketssigned 6:00 AM
  • Branch protection on mainsigned 6:00 AM
  • CloudTrail retention 365 dayssigned 6:00 AM
  • Alerting on production errorssigned 6:00 AM

Controls satisfied

  • CC6.1Passing
  • CC6.7Passing
  • CC8.1Passing
  • CC7.2Passing
  • CC1.4Passing
650+ checks · 60+ providers · on a schedule

02

Screenshot Automation

Settings pages and admin consoles with no API, the evidence teams still screenshot by hand. Click the extension, or let a procedure trigger it on schedule. Captured, redacted, quality-checked, signed, filed.

Where most platforms hand the work back to you.

Screenshot automation
Screenata extension
CapturingCapturedCaptured 2026-09-14 06:00:12 UTC

What happens next

  1. Capture1440×900 · time-stamped
  2. Redact1 field masked
  3. Vision checkQuality 9 / 10
  4. SignSHA-256 · RFC 3161
  5. FileCC8.1 · Change management
Re-captured on schedule · evidence never goes stale

03

Procedure Automation

Multi-step work with an owner per step, proof attached as you go, and a sign-off at the end. The run itself becomes the signed evidence record.

Where most platforms hand the work back to you.

Quarterly backup restore test
Trigger

Quarterly schedule

Apr 1 · 09:00run #4
Step

Restore snapshot to staging

Sarah log
Vera

Compare row counts

Running…2,418,902
Condition

Counts match?

Approval

CTO signs off

MarcusPendingWaiting
Evidence

Signed record

A1.2
If noskip

Open incident

yesyesno

Vera: Counts match on both sides. Routed to Marcus for sign-off.

Results recorded as you work · every run is a signed record

Plus inbox ingestion: forward an email or drop a file in Slack and it files itself.

The evidence collector extension

03 · Slack & email

Compliance requests without another login.

Your team shouldn't have to sign in to one more platform to finish a request. Files dropped in Slack or emailed to your workspace address are filed as evidence and matched to the right test. Nobody has to open the dashboard.

  • Email your workspace address: attachments are filed as evidence, and Vera replies
  • Owners get a reminder before work is due and an alert when it's late
  • Daily freshness checks: fresh, stale at 90 days, expired at 120
Slack, Acme Corp

compliance

8 members · pinned: SOC 2 program

Today
Screenata
ScreenataAPP6:30 AM

Daily compliance briefing · Mon Apr 28

  • Readiness 84% (+12 vs last week)
  • 1 blocker: CC6.1, Okta access review evidence stale (92d)
  • 2 warnings: CloudTrail Q2 export missing, S3 encryption check needs re-run
  • Next: ask @priya for the access review export
Screenata
ScreenataAPP9:04 AM

Weekly cloud scan · 500 checks

  • 499 passed · 1 new finding
  • S3 bucket logs-archive missing default encryption
  • Drafted remediation ticket, needs your approval to apply.
Reply to #compliance

04 · Proof

One sentence. One claim. One test. One signed artifact.

Screenata links each policy sentence to the control it satisfies, the test that checks it, and the signed evidence that proves it. Your team can see why a requirement exists and exactly what proves it. Your auditor can verify the artifact outside Screenata.

  • Trace any policy, claim, control, or test through to its evidence
  • Each test says what to provide and how your auditor will judge it
  • Per-file SHA-256 manifests, RSA/ECDSA signatures, RFC 3161 timestamps
  • Open Attest, the open evidence spec, with a free verify CLI

Policy sentence

Administrative access requires MFA through Okta.

Access Control Policy / §3.2

extracts a testable claim

Policy claim

MFA enforced for admin accounts

CC6.1 · IA-2 · IMPLEMENTED

verified by a control test

Control test

Okta MFA policy verification

Native API check · 24h freshness

produces a signed artifact

Evidence artifact

Signed Okta API response

SHA-256 + RFC 3161 timestamp

SHA-256RFC 3161verify outside Screenata

How it runs

A week of compliance, run by Vera.

Scheduled agents do the checking, following up, and filing. You approve the parts that need a human.

  1. Monday · 6:00 AM

    Cloud and code scan

    Checks run across AWS or GCP, GitHub, and your identity provider. Every result maps to a control.

    499 / 500 passed
  2. Every day · 6:00 AM

    Evidence freshness check

    Each artifact is checked against its window. Fresh, stale at 90 days, expired at 120.

    3 going stale
  3. Every day · 6:30 AM

    Briefing in #compliance

    Readiness, blockers, and the one thing to do next, posted where the team already reads.

    Readiness 84% · 1 blocker
  4. Every day

    Follow-ups sent for you

    Owners get a reminder before a test is due and an alert when it's late. Work nobody owns routes to the test's owner role.

    2 reminders · 1 SLA alert
  5. When a check fails

    Fix recommended

    Each failing check comes with the recommended fix and the steps to apply it. The finding closes on its own once the nightly re-check passes.

    Re-check passed · closed
  6. Audit window

    Signed pack assembled

    Policies, evidence, and a manifest. Your auditor verifies the signatures independently.

    SHA-256 · RFC 3161

Also included

Everything else in the box.

Trust Center, vendor management, questionnaires, and the rest. Included in the price, not sold as line items.

  • S3 buckets encrypted
    MFA on all admins
    CloudTrail retention 365d

    650+ automated checks

    Cloud, code, and identity scans on a schedule. One check counts toward every framework it maps to.

  • ppriya@acme.com
    ssam@acme.com
    aalex@acme.com

    People & training

    Onboarding, training, and policy acknowledgments per employee.

  • MacBook
    RDS
    S3

    Asset inventory

    Laptops, cloud resources, and SaaS accounts with owner and encryption state.

  • contractor@ext.io

    Admin · idle 71d

    KeepRevoke

    Access reviews

    Quarterly reviews pulled, routed for approval, and filed by Vera.

  • trust.acme.com Live
    SOC 2 Type II
    HIPAA

    Trust Center

    A public page built from live evidence. Prospects stop emailing for the report.

  • AWSLow
    OpenAIMedium
    StripeLow
    DatadogLow
    TwilioMedium

    Vendor risk

    Every vendor with a risk tier, DPA status, and their own SOC 2 report.

  • Do you encrypt data at rest?

    Yes. AES-256 on all RDS and S3.

    Sourced from CC6.7

    Security questionnaires

    Answers drafted from your controls, with the control ID attached.

  • Risk card

    RSK-002

    Ransomware on production

    Inherent 20 · Residual 8

    Risk register

    Findings from Wiz, CrowdStrike, AWS Security Hub, Snyk, and GitHub land here with severity and the affected system.

  • Auditor viewread-only
    Signed evidence pack
    Manifest verified

    Auditor portal

    A read-only view of controls, evidence, and the signed pack for the auditor you pick.

What auditors need first

“Until we have all the policies in place, the risk assessment completed, system description completed, a timestamped network diagram, a vulnerability scan report, we wouldn’t be able to begin with control testing.”

A SOC 2 auditor

Screenata delivers all eight of those artifacts before your observation window opens. And because two recent collapses broke trust in AI compliance, we answer with architecture, not adjectives.

Credentials never touch our database

Cloud provider keys live in Azure Key Vault, retrieved at scan time, never cached or logged. A breach of us is not a breach of you.

Read-only by construction

No write scopes on your repos or cloud. Source code is scanned in memory and never persisted. We cannot change your infrastructure, by design.

Evidence you can verify yourself

RSA/ECDSA signatures, RFC 3161 timestamps, SHA-256 manifests, BYOK. An open spec and a free verify CLI, no account needed.

What it costs

$5,988 a year per framework, against a $42–178K year one.

Flat and published at $499/mo per framework for a standard startup audit scope, typically up to 50 employees and one legal entity. Scale & Enterprise is custom-priced for complex programs and includes SAML SSO. The auditor stays independent either way.

You are not paying for a dashboard. You are paying for the work.

See pricing

SOC 2 Type IIYear one · auditor $7–15K on every path

  • Excel + DIY

    Platform $0 · ~440 hrs

    $73–81K

  • Vanta/Drata + DIY

    Platform $12–25K · ~200 hrs

    $49–70K

  • Vanta/Drata + vCISO

    Platform $12–25K · vCISO $5–120K · ~120 hrs

    $42–178K

  • Screenata

    Platform $6K · 60–80 hrs

    $22–33K

FAQ

The questions technical founders ask first.

Concrete architecture, real workflows, and proof over category claims.

What makes Screenata different from Vanta or Drata?

Most compliance platforms track the work: the dashboard shows what's missing and a person goes and does it. Screenata's agent does the work. Vera scans your infrastructure, composes policies from what's real, collects evidence, runs scheduled checks at 6 AM, and delivers everything through Slack, email, GitHub, and your terminal. And where evidence comes from is different: every platform reconstructs it after the work; we're building the one where the work produces it.

Does Vera actually do work without someone clicking buttons?

Yes. Daily 6:00 AM evidence freshness checks, daily 6:15 AM readiness snapshots, weekly Monday cloud and code scans, and annual risk refreshes all run on scheduled jobs; quarterly access reviews are scheduled and orchestrated by Vera, with a human certifying each one. Vera flags stale evidence, drafts delegation messages, scopes remediation, and posts agent reports. You approve actions; you don't run them.

How are policies generated?

Screenata scans first, then writes. We pull context from GitHub, AWS or GCP, your IdP, existing evidence, and your company profile, then generate policies grounded in what we found. The overpromise checker flags hard commitments (like 'quarterly access reviews') we cannot verify in evidence, before you ever ship them to an auditor.

Can auditors trace claims back to proof?

Yes. Each claim in a policy is anchored to a specific sentence and linked to the control test that verifies it. Each test has its evidence submissions, and each submission references a cryptographically signed artifact. An auditor can hover any claim in a policy, see the test that proves it, and verify the evidence package independently with a signed manifest.

What happens to evidence packages?

Evidence exports are tamper-evident: SHA-256 per-file hashes, RSA or ECDSA digital signatures, RFC 3161 independent timestamps, and BYOK support so enterprises can sign with their own keys. We're publishing the format as an open spec with a free verify CLI so anyone can check a Screenata pack without an account.

How do you collect evidence that integrations can't reach?

Three channels, not one. API scans cover about 30–40% of a SOC 2 across cloud, code, and identity providers. The browser extension captures screenshots of settings pages and workflows, redacts sensitive fields, runs a vision quality check, signs the capture, and re-captures it on a schedule. Guided procedures walk a teammate through steps like a backup restore test and record results and attachments as they work. Most platforms only offer the first channel and hand the rest back to you as a to-do list.

How much does SOC 2 cost with Screenata compared to other platforms?

For a company under 50 employees, year one to a SOC 2 Type II runs $22–33K with Screenata, $73–81K in spreadsheets done yourself, $49–70K on Vanta or Drata done yourself, and $42–178K on Vanta or Drata with a vCISO, counting the auditor, the platform, any consultant, and your team's time at $150/hr. The auditor fee is the same on every path, and you choose and pay the auditor directly. Spreadsheets save the licence and cost more than it in hours: your team builds the tracker, gathers every artifact by hand, and re-checks every control each month because nothing monitors it.

Do I need compliance expertise to use Screenata?

No. Every test explains what to provide, which evidence items are required, and how your auditor will judge it, and you can ask Vera about any requirement in plain language. The lineage view traces a policy, claim, control, or test through to the evidence that proves it, so you can see why something is required. When a check fails, it comes with the recommended fix and the steps to apply it, and the finding closes on its own once the nightly re-check passes.

Do we have to collect the same evidence again for each framework?

No. A single test maps to controls in every framework it satisfies, so evidence collected once counts toward SOC 2, HIPAA, and ISO 27001 at the same time. The controls view shows what else each test satisfies, so you can see the reuse instead of taking it on faith.

Can I use Screenata in Slack?

Yes. Files dropped in Slack are saved as evidence and matched to the tests they support, and escalations and SLA alerts post to Slack. You can also email your workspace address: attachments are filed as evidence and Vera replies. The dashboard is there for auditors and deep dives; day-to-day requests get done where your team already works.

Is the evidence Vera produces auditor-ready?

Yes. Every artifact is mapped to specific Trust Services Criteria or HIPAA safeguards, signed with SHA-256 + RFC 3161 timestamps, and traceable from policy claim → control test → submission → vault artifact. Auditors get a structured pack, not a folder of screenshots, and can verify integrity independently with a free CLI. We design the output for what auditors actually look for in fieldwork: completeness, attribution, freshness, and tamper evidence.

Do you work with vCISOs or compliance consultancies?

Yes, Screenata is built to make your practice more profitable, not to replace it. vCISO firms resell or refer Screenata to their clients. Vera absorbs the policy writing, evidence chasing, and status reporting that eats 60% of your hours, so you can take on 3x the clients at the same headcount while keeping the advisory relationship and the margin. You get a firm-admin account across your client tenants. See screenata.com/for-vcisos for the partner program.

Which frameworks do you support?

SOC 2, HIPAA, ISO 27001, ISO 42001, and GDPR. Our control model uses a shared canonical catalog so a single MFA scan satisfies SOC 2 CC6.1 and HIPAA §164.312(d) at the same time, and the same scan maps across the other frameworks you run. You collect evidence once instead of paying for each framework separately.

Connect and see

Your next enterprise deal is going to read the report.

Connect GitHub and cloud read-only. Vera shows your control matrix, policy gaps, stale evidence, and prioritized next actions before you commit to anything.

See the product