Skip to content
winfunc
Pricing

Start with one audit. Scale to every pull request.

Buy a single scan, top up credits as you go, or keep a monthly allowance for continuous review. Enterprise adds your own hosting, tenancy, and model keys.

Compare plans
  • No subscription to start
  • Credits estimated before every scan
  • SOC 2 Type II audited

Plans

A release or an audit

One-time

One surface or deep scan, delivered as findings your team can review. No subscription.

from$500

per surface scan

Deep scan priced by scope

  • Pay once, no subscription
  • Surface scan from $500
  • Deep scan priced by scope
  • Findings workspace and report
  • Prioritized findings with supporting context
  • Suggested remediation for review

Occasional usage

Pay as you go

Buy credits when you need them and run the full credit-based workflow without a commitment.

Credits

bought as needed

Estimated before every scan

Includes

  • Incremental, scheduled, and PR review
  • Reproduction evidence where feasible
  • Suggested patch pull requests
  • AI triage assistant
  • Winfunc MCP
  • Team access
  • Slack alerts
  • Reports and analytics

Continuous review

Recommended

Recurring

A monthly credit allowance for teams that review every change and ship fixes on a cadence.

Monthly

credit allowance

Discounted annual billing

Everything in Pay as you go, plus

  • Allowance that renews each month
  • Annual billing at a discount
  • Reconciled usage visible per scan

Regulated teams

Enterprise

Committed usage with the deployment, identity, and support terms your review requires.

Custom

committed usage

Terms set in your agreement

Everything in Recurring, plus

  • Committed-usage pricing
  • Customer-controlled hosting
  • Isolated tenants
  • Bring your own model keys
  • Organization-wide policies
  • Named support and response terms
How credits work

You see the cost before the scan runs.

Pay as you go and Recurring plans draw from a credit balance. Every scan is estimated up front, held while the agents work, and settled to what it actually used.

One-time scans are quoted before work begins, so there is nothing to reserve or reconcile.

Credit lifecycle ยท per scan

  1. 01Estimate

    Sized from changed files, lines of code, and comparable past scans.

  2. 02Reserve

    The estimate is held against your balance for the run.

  3. 03Reconcile

    The charge settles to final usage when the scan completes.

EstimatedReservedFinal usage
Compare plans

The details security buyers ask about.

Every plan runs on the same agents. What changes is how you pay, how often you scan, and where it runs.

Swipe the table sideways to compare all four plans.

Plan comparison across pricing, scanning, workflow, and deployment
CapabilityOne-timePay as you goRecommendedRecurringEnterprise
Pricing and commitment
Purchase modelOne-time quoteBuy creditsMonthly or annualCustom
Surface scan pricingFrom $500Uses creditsUses allowanceCustom
Deep scan pricingPriced by scopeUses creditsUses allowanceCustom
Reusable credit balanceNot includedIncludedIncludedCustom allocation
Credit estimate before each scanNot includedIncludedIncludedIncluded
Recurring commitmentNot includedNot includedMonthly or annualCommitted usage
Annual billing discountNot includedNot includedIncludedCustom
Scanning and remediation
Surface scanIncludedIncludedIncludedIncluded
Deep scanIncludedIncludedIncludedIncluded
Application-aware code reviewIncludedIncludedIncludedIncluded
Business-logic and authorization investigationIncludedIncludedIncludedIncluded
Dependency scanning (SCA)IncludedIncludedIncludedIncluded
Incremental repository scansNot includedIncludedIncludedIncluded
Scheduled scansNot includedIncludedIncludedIncluded
Pull request reviewNot includedIncludedIncludedIncluded
Reproduction evidence where feasibleNot includedIncludedIncludedIncluded
Suggested patch pull requestsNot includedIncludedIncludedIncluded
Workflow
Findings workspaceIncludedIncludedIncludedIncluded
Reports and analyticsSingle reportIncludedIncludedIncluded
AI triage assistantNot includedIncludedIncludedIncluded
Winfunc MCPNot includedIncludedIncludedIncluded
GitHub App integrationIncludedIncludedIncludedIncluded
Slack alertsNot includedIncludedIncludedIncluded
Team accessNot includedIncludedIncludedIncluded
SupportScan deliveryStandardStandardNamed contact
Data and deployment
Data retention scheduleConfirm scopeConfirm scopeConfirm scopeBy agreement
Model-provider data termsConfirm scopeConfirm scopeConfirm scopeBy agreement
Customer-controlled hostingNot includedNot includedNot includedIncluded
Isolated tenantsNot includedNot includedNot includedIncluded
Bring your own model keysNot includedNot includedNot includedIncluded
Organization-wide policiesNot includedNot includedNot includedIncluded
Contracted response termsNot includedNot includedNot includedIncluded
Enterprise

The controls your security review will ask for.

Review access, retention, model-provider data terms, and administrative events. Enterprise hosting, identity, isolation, and named-support options are scoped by agreement. Use the procurement pack and current Trust Center materials for your evaluation.

Trust Center

Identity and access

  • Repository-scoped access

    Authorize selected repositories and review user and administrator permissions before expanding scope.

  • Federated identity optionsEnterprise

    Confirm the identity provider, protocol, and configured deployment in the enterprise agreement.

  • User lifecycle reviewEnterprise

    Agree provisioning, deprovisioning, session invalidation, and access-review responsibilities.

  • Revocable MCP keys

    Read-only MCP keys are stored as SHA-256 digests and support revocation. Review other credential types separately.

Data protection

  • Retention by data category

    Working copies, caches, findings, resume state, operational records, backups, and provider data need an agreed lifecycle.

  • Model-provider terms

    Agree the provider/account, processing region, training-use restrictions, and retention before granting access.

  • Credential protection

    Onboarding test credentials support authenticated encryption when storage is configured. Confirm other storage and transport protections.

  • Event and trace boundaries

    API event metadata excludes bodies and credential headers; agent/session traces are separate retained artifacts to review.

Deployment and models

  • Customer-controlled hostingEnterprise

    Hosting and infrastructure, access, upgrade, and support responsibilities are scoped by agreement.

  • Isolated environmentsEnterprise

    Review the proposed network, storage, identity, model, and administrator boundaries.

  • Bring your own model credentialsEnterprise

    Confirm providers and account controls. Customer-owned keys alone do not establish private inference or zero retention.

  • Open-weight model evaluation

    Public research used open models. Confirm the proposed endpoints, infrastructure, and supported workflow for your deployment.

Oversight

  • Administrative event review

    Confirm event coverage, access, retention, filtering, saturation behavior, and export for the deployment.

  • Customer change approval

    Agree read and pull-request permissions separately. Keep patch review, verification, and release approval with your team.

  • Policy and scope controls

    Agree review policies, permitted actions, test environments, exceptions, and reporting for the purchased workflow.

  • Named supportEnterprise

    Support, escalation, response targets, and incident-notice terms are confirmed in the contract.

AICPA SOC 2 Type II

SOC 2 Type II audited

Trust Center

Terms to agree for your deployment

  • Code, finding, and patch ownership
  • Incident notice and escalation obligations
  • Retention, deletion triggers, and backup expiry
  • Confidentiality and data-processing terms
  • Approved regulated-data scope, including any BAA
  • Provider and subprocessor security obligations
Pricing FAQ

Clear terms before the call.

01What happens in a demo?

We review your codebase, security goals, and expected scan volume, then show how winfunc fits your workflow. From there we recommend a one-time scan, pay-as-you-go credits, recurring coverage, or an Enterprise agreement.

02What is included with a One-time scan?

A surface scan from $500 or a deep scan priced by scope, plus the findings workspace and report. It does not include a reusable credit balance, Winfunc MCP, suggested patch pull requests, the AI triage assistant, or ongoing incremental, scheduled, and pull request review.

03How is Pay as you go different from Recurring?

Both use the same credit-based workflow and include the same capabilities. Pay as you go lets you buy credits when you need them. Recurring renews an agreed allowance every month, with a discount for annual billing.

04How are scan credits calculated?

Before a scan starts, winfunc estimates its credit cost from the changed files, the lines of code, and comparable previous scans. Those credits are reserved for the run, then reconciled to the final usage when the scan completes.

05Can Recurring be billed annually?

Yes. Recurring is billed monthly by default, and an annual commitment receives a discount. The exact allowance and discount are confirmed on the pricing call.

06What does Enterprise add?

Enterprise includes everything in Recurring plus committed-usage pricing, customer-controlled hosting, isolated tenants, bring-your-own model keys, organization-wide policies, and a named support contact with contracted response terms.

07Is my code used to train models?

Agree training-use restrictions and retention for the selected model provider and account before granting code access. Source working copies, caches, retained findings, resume state, and backups have different lifecycles. The procurement pack lists the data categories and deployment-specific terms to review.

08Are threat modeling, cloud security, and AI-assisted triage included?

They are available today, alongside SAST, SCA, IaC scanning, and red, purple, and blue team engagements. We scope them with you on the pricing call together with the rest of your coverage.

Find the right fit

Map a plan to your codebase.

Tell us about your repositories and review cadence. We'll recommend a one-time scan, credits, recurring coverage, or Enterprise, and walk through how credits are estimated.

See public findings