Provenance intelligence,
priced to scale
Launch and Growth self-serve trials are open now. Product capabilities remain labeled by their actual availability.
Public repository URL scan intake, npm and PyPI manifest extraction with OSV checks, AI-origin scoring over a bounded source sample, policy evaluation against built-in and active custom rules, and completed-scan CycloneDX export are available now.
Launch
For teams starting with public-repository scan intake and OSV-backed dependency checks.
Available now
- Authenticated public-repository scan intake
- Queued job tracking with job ID + status
- Repository metadata history (manifest discovery)
- npm / PyPI dependency lineage with OSV matching
- Private GitHub scanning with a connected token
- AI-origin score (bounded source sample)
- Policy engine (log & warn actions, incl. custom rules)
Support
- Email support
Included as released
- Maven dependency lineage — coming at GA
- SOC 2 compliance reports — coming at GA
- Archive scan intake — coming at GA
Usage limits
- Up to 10 repositories
- Up to 50 scans / month
- Up to 5 users at GA
- Metadata retained for the life of the account
Growth
For scaling organizations planning policy automation and reporting as those phases reach GA.
Everything available now in Launch, plus:
Support
- Priority email support
Included as released
- Policy engine (block & require-review actions) — coming at GA
- EU AI Act & GDPR compliance reports — coming at GA
- Slack, GitLab & Bitbucket integrations, and outbound webhooks — coming at GA
- SBOM generation & validation — coming at GA
Usage limits
- Up to 50 repositories
- Up to 250 scans / month
- Up to 25 users at GA
- Metadata retained for the life of the account
Control
For enterprises planning advanced provenance controls, dedicated support, and custom rollout requirements.
Everything available now in Growth, plus:
Support
- Direct founder access
Requires enterprise review
- SLSA Level 3 provenance attestation — requires enterprise review
- HIPAA compliance reports — requires enterprise review
- SSO / SAML (Okta, Azure AD, Google) — requires enterprise review
- High-availability infrastructure — requires enterprise review
Usage limits
- Unlimited repositories
- Custom scans / month (to be confirmed at GA)
- Custom seat count (to be confirmed at GA)
- Custom retention windows per enterprise agreement
SOC 2 Ready
Built to SOC 2 controls — compliance evidence generation is on the roadmap
Encrypted at rest
By our infrastructure providers
TLS 1.3
In transit
Proof behind the plans
What you receive with ProvenanceOS
The current scan path below maps to code that ships today. No fabricated customer logos or testimonials; roadmap items are labeled.
Illustrative report example
This visual example is not live scan output; its numbers are sample values. Current completed public repository scans provide npm and PyPI dependency extraction, OSV checks, CycloneDX export, AI-origin scoring over a bounded source sample and Policy evaluation (built-in + active custom rules). Not available today: compliance reports.
Available in current scans
- npm and PyPI dependency manifests
- Known-vulnerability checks against OSV
- AI-origin scoring over a bounded source sample
- Policy evaluation (built-in + active custom rules)
- CycloneDX export for completed scans
Shown only as roadmap examples
Not available today: compliance reports.
Illustrative example — sample values, not generated from a real scan
Provenance confidence
87%
AI-Origin Scoring & Stylometrics
Example valuesTop evidence signals
- Dependency manifest resolved (npm)94%
- Known vulnerability match (OSV.dev)91%
- Repository metadata (manifest discovery)88%
- AI-origin stylometric signals (bounded source sample)89%
Dependency lineage
Example values47 dependencies traced across npm + PyPI
3 known vulnerabilities matched (OSV.dev) • 1 high • 2 medium
Policy decision
Pass — 0 policy violations
Flag critical-severity dependencies
Example record ID
EV-2026-07-11-A1B2C3
2026-07-11T14:32:00Z
What you receive in the first 15 minutes
- Authenticated scan intake (repository URL)
- Durable queued job tracking with job ID + status
- Repository metadata extraction (manifest discovery)
- Dependency resolution across npm and PyPI, including packages from an npm lockfile
- Known-vulnerability match against OSV.dev with severity counts
- AI-origin score with confidence and sample coverage (bounded source sample)
- Policy evaluation: per-rule pass / warn / block / could-not-evaluate decisions
- Job status + scan summary, viewable in-app
Architecture & data flow
What ships today: repository scan intake, stored scan metadata, and dependency and vulnerability results. AI-origin scoring runs in the same worker over a bounded source sample.
Sample policy decision
0 policy violations · 0 critical-severity dependencies on the release branch.
Example — the policy engine (log & warn) is available now; this shows the shape of a decision it produces.
Download sample compliance report
A redacted PDF export of the sample report above will be available once the compliance-report artifact ships. Until then, contact us to discuss a preview.
Contact us about a previewFounder credibility
ProvenanceOS is built by Edward Brooks, an AV systems engineer and software builder. Read the founder profile and the legal/operator relationship with Developer312 on the About page.
Plan comparison
Side-by-side usage limits, retention, support, and contractual terms. The qualitative state is accurate today; exact quantitative limits will be confirmed at GA.
Swipe sideways to compare Launch, Growth and Control.
| Capability / limit | Launch | Growth | Control |
|---|---|---|---|
| Repositories | Up to 10 repositories | Up to 50 repositories | Unlimited repositories |
| Scans / month | Up to 50 scans/month | Up to 250 scans/month | Custom (to be confirmed at GA based on engagement) |
| Users / seats | Up to 5 users | Up to 25 users | Custom seat count (to be confirmed at GA) |
| Data retention | Repository metadata retained for the life of the account; derived signals retained with the scan job. | Same as Launch: metadata retained for the life of the account; signals retained with the scan job. | Custom retention windows per the enterprise agreement. |
| Report retention / export | Customer-controlled. You can delete a report at any time; export retains your copy. | Customer-controlled, with priority export. | Custom report retention + export terms per the enterprise agreement. |
| Overage behavior | Overage is not sold on the Launch plan. When the repository or scan limit is reached, new scans are queued until the next cycle or until you upgrade. | Per-scan overage billing on Growth is planned; until it ships, new scans queue until the next cycle or until you upgrade. | Overage is contracted per engagement; no per-scan overage on Control. |
| Trial feature availability | The 14-day trial covers the capabilities marked as available now for this plan. A card is not required to start it. If no payment method is on file when the trial ends, the subscription is cancelled and you are not charged. | The 14-day trial covers the capabilities marked as available now for this plan. A card is not required to start it. If no payment method is on file when the trial ends, the subscription is cancelled and you are not charged. | Not applicable — Control is a sales-led engagement with a scoped proof-of-value period instead of a self-serve trial. |
| Onboarding / implementation fee | No onboarding fee on the Launch plan. | No onboarding fee on Growth; a guided setup call is included. | Implementation fee is scoped per engagement and may be waived for design partners. |
| Cancellation timing | Cancel anytime; changes take effect at the end of the current billing cycle. | Cancel anytime; changes take effect at the end of the current billing cycle. | Annual contract; cancellation terms are scoped per engagement. |
| SLA applicability | No contractual SLA on the Launch plan. The platform is operated to SOC 2 controls; a formal SLA is available on Control. See the Service Level Agreement. | No contractual SLA on Growth. A formal SLA is available on Control. See the Service Level Agreement. | Contractual SLA included on Control. See the Service Level Agreement. |
| Support hours + time zone | Email support, business hours. | Priority email support, business hours. | Direct founder access + dedicated support, extended hours. |
| SSO availability timing | SSO/SAML is planned for a future phase and is not included in the Launch plan at GA. | SSO/SAML is planned for a future phase and is not included in the Growth plan at GA. | SSO/SAML is included on Control when the SSO phase ships. |
| Data residency options | Single-region hosting today; multi-region data residency is not yet available. | Single-region hosting today; multi-region data residency is a roadmap item. | Data residency is scoped per engagement; a single-tenant VPC is a roadmap item. |
| Future features contractually included | Roadmap timing is not guaranteed; future capabilities are included only when documented for the plan at release. | Roadmap timing is not guaranteed; future capabilities are included only when documented for the plan at release. | Roadmap capabilities are contractually included as released under the enterprise agreement. |
| Compliance status | Built to SOC 2 controls — compliance evidence generation is on the roadmap | ||
Need Enterprise?
Custom pricing, annual contracts, dedicated support, and procurement-friendly terms for organizations with advanced security and compliance requirements.
Contact salesExplore featuresBilling and usage FAQ
How do I get access?
Create an account, then start a Launch or Growth 14-day trial from this page. Public repository URL scan intake, npm and PyPI manifest extraction with OSV checks, AI-origin scoring over a bounded source sample, policy evaluation against built-in and active custom rules, and completed-scan CycloneDX export are available now. Automated policy enforcement (block / require-review) and compliance reports remain planned.
When can I sign up for a paid plan?
Launch and Growth are open now through self-serve checkout. New customers receive a 14-day trial, and Control remains a sales-led plan.
What counts as a repository for pricing?
A repository is a single public source repository (for example, github.com/acme/payments-service) that you scan under one ProvenanceOS account. A repository counts against your plan limit once you create a scan job for it; rescanning the same repository does not consume an additional slot.
What are the scan and compute limits?
Scan limits are scoped per plan (Launch: up to 50 scans/month; Growth: up to 250 scans/month; Control: custom). Each scan is one queued analysis job. Overage behavior differs per plan — see the plan comparison table below.
What are the user / seat limits?
Each plan includes a seat count (Launch: up to 5 users; Growth: up to 25 users; Control: custom). Seat counts are finalized at GA; Control seats are scoped per the enterprise agreement.
What is the data retention and report retention policy?
Repository metadata is retained for the life of the account so job history is queryable. Derived signals are retained with the scan job. Reports are customer-controlled — you can delete a report at any time and export retains your copy. See the /security data-processing table for the full retention policy.
What happens if I exceed a usage limit (overage)?
On Launch, overage is not sold — new scans queue until the next cycle or until you upgrade. On Growth, per-scan overage billing is planned; until it ships, new scans queue until the next cycle or until you upgrade, the same as Launch. On Control, overage is contracted per engagement.
What trial features are available, and when do trials expire?
The 14-day trial covers the capabilities marked as available now for the selected plan. A payment card is not required to start it, and you are not charged during the 14 days. If no payment method is on file when the trial ends, the subscription is cancelled and you are not charged. If a payment method is on file, you are charged for the plan and billing period you selected, and the subscription renews until you cancel from Settings → Billing → Manage billing.
Are there onboarding or implementation fees?
No onboarding fee on Launch or Growth; a guided setup call is included on Growth. On Control, the implementation fee is scoped per engagement and may be waived for design partners.
When can I cancel, and how does cancellation timing work?
On Launch and Growth, cancel anytime; changes take effect at the end of the current billing cycle. On Control, cancellation terms are scoped per the annual enterprise agreement.
Is an SLA included?
No contractual SLA on Launch or Growth. A formal SLA is included on Control. The platform is operated to SOC 2 controls regardless of plan.
What are the support hours and time zone?
Launch: email support, business hours. Growth: priority email support, business hours. Control: direct founder access + dedicated support, extended hours.
When will SSO / SAML be available?
SSO / SAML is planned for a future phase and is included on Control when the SSO phase ships. It is not included in Launch or Growth at GA.
What data residency options are available?
Single-region hosting today; multi-region data residency is a roadmap item. Control engagements can scope data residency per contract.
Are future features contractually included?
Roadmap timing is not guaranteed. Future capabilities are included only when documented for your plan at release.
Can I switch plans later?
Yes. You can upgrade or downgrade through the billing flow. Changes take effect according to the current billing cycle.
Do you offer discounts for startups or nonprofits?
Yes. Contact us at support@provenance-os.com for startup and nonprofit pricing.
What's the Enterprise plan?
Enterprise is for organizations with custom procurement, security review, or data residency requirements. Pricing is annual-only and determined per engagement. Contact sales to get started.
Is my code data secure?
Selected supported dependency manifests and a bounded sample of source files (up to 40 files / 512 KB) are processed transiently and never retained; only the sampled files' paths are stored with the result. ProvenanceOS stores scan metadata and results — and, when connected, the organization's GitHub token, encrypted at rest — not a repository mirror. All data is encrypted in transit (TLS 1.3) and encrypted at rest by our infrastructure providers (InsForge and Railway). Built to SOC 2 controls — compliance evidence generation is on the roadmap.
How ProvenanceOS processes your data
ProvenanceOS accepts GitHub, GitLab, and Bitbucket repository URLs. Public repositories scan without a token; private GitHub repositories scan with a connected GitHub token (Integrations → GitHub), stored encrypted and displayed only as its last four characters. For each scan it reads supported npm and PyPI dependency manifests transiently to check packages against OSV, and fetches a bounded sample of source files (up to 40 files / 512 KB, JavaScript, TypeScript, and Python) transiently to compute an AI-origin score. Manifest and source file content is held in memory only for the duration of the scan and is not retained; the paths of the sampled files are stored with the scan result so its coverage can be shown. ProvenanceOS retains scan metadata and the dependency, vulnerability, AI-origin, and policy results. Archive uploads, provider OAuth or sync, policy enforcement, and compliance reports are planned. Completed scans can be exported as CycloneDX JSON. Repository content is not used to train models or stored as a repository mirror.
| Data type | Processed | Retained | Retention | Third-party access |
|---|---|---|---|---|
| Source files | Yes, transiently. To compute the AI-origin score, each scan fetches a bounded sample of the repository's JavaScript, TypeScript, and Python source files (up to 40 files / 512 KB in total, 128 KB per file, within a 20-second budget) from the repository host at its default branch, crawled from the package entry points. Vendored, generated, minified, and lock files are never fetched. File content is held in memory only while the scan runs. Archive and source-file uploads are not available. | Content: no. Sampled file paths: yes. | File content is discarded when the scan completes and is never written to storage, logs, or a repository mirror. The repository-relative paths of the sampled files (not their content), with the file and byte counts and the caps applied, are stored with the scan result so the score's coverage can be shown, and are deleted with the job or on account deletion. | None beyond the repository's provider (GitHub, GitLab, or Bitbucket) that serves the files. Source content is scored in-process; it is not sent to OSV, an AI model provider, or any other third party. |
| Repository metadata | Yes. A GitHub, GitLab, or Bitbucket repository URL and provider are read to create a durable scan job. Public repositories scan directly; private GitHub repositories scan with a connected GitHub token (Integrations → GitHub). | Yes | Retained for the life of the account so job history is queryable. Deleted on account deletion. | Hosted on InsForge (managed Postgres). The repository's provider serves the dependency manifests and the sampled source files for the scan. |
| Derived signals | Yes. Supported npm and PyPI dependency manifests are read transiently, packages are checked against OSV, and dependency and vulnerability results are stored with the scan. The AI-origin score (score, confidence, contributing stylometric signals, and sample coverage) and the policy evaluation computed from the same scan are stored with it. | Yes | Retained with the scan job so results remain queryable. A completed scan can be exported as CycloneDX JSON. Deleted with the job or on account deletion. | Stored in ProvenanceOS infrastructure (InsForge managed Postgres). Only dependency identifiers are sent to OSV. Not shared with other third parties. |
| Reports | No. Compliance reports are planned. CycloneDX is a completed-scan dependency export, not a compliance report. | No | Not applicable. ProvenanceOS does not generate or retain compliance reports today. | None. A CycloneDX export is generated for download only after a completed scan. |
| Credentials/tokens | Optional. The organization can connect a GitHub personal access token (Integrations → GitHub) so scans can read private repositories the token can access. On connect the token is validated against the GitHub API, then stored encrypted at rest (AES-256-GCM, key held server-side) and used only by the scan worker to read repositories for that organization's own scans. | The token: yes — encrypted at rest. It is displayed to users only as its last four characters. No other repository-provider credentials or tokens are collected. | Stored until the organization disconnects the token (Integrations → GitHub → Disconnect), which deletes the stored copy immediately. Deleted on account deletion. | The token is sent only to GitHub itself, as authorization for the scans the organization authorizes. It is not shared with any other third party. GitLab and Bitbucket tokens are not collected. |
Still have questions? Contact our team
Start with the capabilities available today
Create an account and choose a Launch or Growth trial. Roadmap capabilities remain clearly labeled until they ship.
Start 14-day trial