Predictable security support, without pretending scope is infinite.
The retainer is built for teams that want a continuous loop from finding to fix to verification, while keeping capacity and milestone progress explicit.
Bounded monthly access with explicit response expectations
Security Units make tradeoffs visible instead of hidden
Milestones are earned over time, including deeper platform testing
Model
Monthly capacity
Support and milestone work draw from the same bounded pool
Delivery style
Async-first
Meetings are optional and consume capacity when used
Best for
Continuous risk reduction
Useful when shipping keeps moving and one-off reviews are not enough
This is not unlimited support and it is not incident response coverage.
How the model works
The retainer stays business-safe by making pace and scope visible, not by hiding work inside vague “support” language.
Security Units
Capacity currency
Support, verification, calls, and milestones all consume the agreed monthly units
Milestone progression
Earned over time
Deeper work happens when enough units are intentionally allocated to it
Scope boundary
Product security only
Not an org-wide audit and not unlimited implementation help
What the retainer is good at
Best for teams that want security to stay close to shipping reality rather than show up only as periodic audits.
Ongoing
Remediation support
Clarify findings, sequence fixes, and keep the action plan current while the team ships.
Verification
Verification and retest support
Use monthly capacity to verify fixes and reduce the lag between “we changed it” and “we know it worked.”
Progression
Earned milestone work
Reserve units toward larger milestones such as a Health Check refresh or a one-platform deep mobile pentest.
How the monthly rhythm stays bounded
Scope and onboarding
Define the product surface, key flows, response expectations, and what counts as out-of-scope.
Monthly allocation
Explicitly split capacity between support work and milestone progress so tradeoffs stay visible.
Delivery and updates
Work happens async-first, with short written updates and optional timeboxed calls when the tradeoff is worth it.
Earned milestones
Once enough units are allocated and prerequisites are ready, deeper milestone work gets scheduled into an agreed delivery window.
What the retainer is not
It is not a promise of unlimited access, unlimited meetings, or unlimited implementation work. Capacity is explicit so the service remains predictable and credible.
Common questions about the retainer
Does this replace a pentest?
Not automatically. The retainer is the path for continuous support and risk reduction. A deep pentest is still a distinct milestone with explicit scope and timing.
Why use units instead of vague support language?
Because it makes tradeoffs visible. Founders and CTOs can see how much capacity is going to verification, advice, or milestone work instead of discovering the limit after the fact.
Can we start here without a Health Check?
Yes, but many teams still start with a Health Check first because it clarifies the backlog and helps the first months of the retainer focus on the right work.
Is there a lighter option?
A lighter monitoring tier is available to clients after a Health Check or pentest.
Related offer paths
Security Health Check
A strong first step when you want to establish the initial risk picture before committing to monthly support.
A fast, productized security review for early-stage teams that need a bounded answer on what matters most next.
View Health CheckDeep Mobile Pentest
Useful when one platform needs a more evidence-heavy review after the retainer has clarified what deserves the depth.
Evidence-first mobile application pentest for teams that need deeper validation on realistic attacker paths, one platform at a time.
View Mobile PentestAsk whether the retainer shape fits your team.
Share your product surface, current milestone, and where you want ongoing help to reduce risk or speed up verification.
Availability and monthly capacity are confirmed after review.
Review the Health Check first