Repository change drift
New files, workflows, scripts, and config paths that expand what AI tools can read or modify.
Recurring monitoring layer
Add monitoring after the first CapitalGuard license proves what matters.
The first purchase stays simple: Starter, Growth, or Pro. Monitoring is the recurring layer for teams whose repositories, AI tools, access rules, and customer diligence needs keep changing after the baseline scan.
Monitoring packages
Monthly or annual scope, quoted after review.
These are recurring monitoring paths on top of a completed license. The public checkout remains focused on Starter, Growth, and Pro so buyers do not subscribe before the baseline is known.
Monitoring License
Monitoring€499per month or €4,990/year
Continuous monitoring
- Monthly AI-agent risk report
- Slack/email alerts
- New-risk detection
- Policy updates
- Quarterly executive report
Monitoring Annual License
Best annual€4,990per year
Continuous monitoring
- Continuous AI-agent exposure monitoring
- Monthly risk reports
- Slack/email alerts
- Policy updates
- Quarterly executive report
What gets watched
Monitoring is for teams whose agent-risk surface keeps moving.
Agent permission changes
New tool access, automation bridges, integration scopes, and human-approval gaps.
Prompt-injection surface
Docs, issues, prompts, logs, and runbooks that could carry hidden instructions into agent workflows.
Policy drift
Protected paths, approval rules, and redaction settings that need updates as the repo changes.
Best order of operations
License first. Monitoring second.
Recurring monitoring is most useful after the buyer knows which repositories, files, agents, policies, and alert paths deserve ongoing attention.
1
Buy Starter, Growth, or Pro and complete the first authorized scan.
2
Review the baseline report, policy files, and remaining exposure surface.
3
Submit repo count, change frequency, AI tooling, and alert requirements.
4
CapitalGuard quotes monthly or annual monitoring after scope review.
Boundaries
Recurring alerts need honest scope.
Monitoring is added after a fixed license baseline, not before the buyer understands the exposure surface.
Monitoring detects new exposure and policy drift; it is not incident response or remediation engineering.
Only repositories owned by the customer or covered by written authorization are eligible.
Alerts and reports are designed to support precautions, not guarantee complete protection.
Ready path