Scenario demos

See the kind of AI-agent exposure CapitalGuard is built to surface.

These simulated demo results show the buying context, risk signals, recommended controls, and best-fit license path without inventing customer stories.

Find My License View Sample Report

Demo evidence without fake customer proof.

Scenarios are simulated examples, not customer testimonials.

No private customer repository, company name, secret, or finding is shown.

Every paid scan still requires ownership or written authorization.

CapitalGuard detects exposure and recommends precautions; it does not guarantee complete protection.

Founder

Pre-launch SaaS repo

A founder team is preparing to let AI coding tools work across docs, app code, and deployment scripts before launch.

Risk score

82/100

Severity

High

Best fit

Growth License

EUR 149

Continue

Signals found

Prompt instructions embedded in docs and issue templates

Agent-readable deployment notes with environment references

Missing policy file for protected paths and approval gates

Precautions

Add prompt-injection review to the launch checklist

Block sensitive deployment paths from agent reads

Install starter policy rules before expanding AI access

Agency

Agency client onboarding

An agency needs a repeatable security packet for several client repositories before introducing AI-assisted delivery.

Risk score

88/100

Severity

High

Best fit

4 Pro Licenses

Reviewed

Continue

Signals found

Different client repos use inconsistent agent permissions

Client authorization needs to be recorded before review

Reports must be separated by client scope and delivery owner

Precautions

Use reviewed bundle handoff for client ownership clarity

Create client-ready report packets per repository

Preserve campaign and delivery attribution through cart review

Team

Investor diligence packet

A growing team wants proof that AI-agent repository access is controlled before investor or customer diligence.

Risk score

76/100

Severity

Medium

Best fit

Pro License

EUR 349

Continue

Signals found

Several agent-readable files mention production access paths

Workflow automation changes lack explicit review gates

No public verification path exists after the internal review

Precautions

Generate executive report output from the Pro path

Review workflow and production-adjacent access before broader agent use

Use verification after payment, authorization, and operator approval

Starter

Single small repo check

A solo builder wants a first-pass AI-agent exposure snapshot before deciding whether a larger report is needed.

Risk score

61/100

Severity

Medium

Best fit

Starter License

EUR 49

Continue

Signals found

One repository has a limited but unclear agent access surface

Dangerous file summary is enough for a first decision

No recurring monitoring is justified before the baseline is known

Precautions

Run the entry scan on the authorized repository

Review dangerous-file and redacted secret-risk summary

Upgrade only if prompt-injection or dashboard evidence is needed

From demo to delivery

A real scan starts only after payment and authorization.

The scenario gallery helps buyers choose a package. The delivery vault still controls activation, ownership confirmation, scan intake, and private report access.

Choose package

Use scenario fit or the license finder.

Activate delivery

Use receipt, license, and buyer email.

Submit scope

Only authorized repositories are reviewed.

Ready to inspect your scope

Use the license finder or buy Pro for the full report workflow.

Find License Buy Pro