Plans and billing
Compare the current code-backed plan entitlements and one-time scan tier.
Plans control project count, scheduling, GEO prompt capacity, model surfaces, reporting features, API access, webhooks, and recurring model-run allocation. They also interact with per-scan engine caps, so a monthly entitlement does not imply that every scan can consume the entire monthly amount at once.
Billing operations are handled through Stripe for subscriptions and one-time purchases. Product messaging should distinguish current application constants from a durable commercial promise, especially for taxes, currency, grandfathering, failed payments, cancellation timing, and feature behavior after a downgrade.
Before changing a subscription, review current project count, active prompts, schedules, API keys, webhooks, report branding, and expected scan usage. A downgrade can leave existing data readable while restricting new creation or automation. The product should communicate those consequences before checkout or cancellation so customers understand which workflows will stop and which historical evidence remains available.
| Capability | Free | Starter | Pro |
|---|---|---|---|
| Projects | 1 | 3 | 10 |
| Scheduled daily scans | No | Yes | Yes |
| Monthly model-run credits | 0 | 10,000 | 30,000 |
| Active GEO prompts per project | 0 | 40 | 80 |
| Selected AI surfaces per project | 0 | 4 | 4 |
| White-label reports | No | No | Yes |
| REST API and new API keys | No | No | Yes |
| Webhooks | No | Yes | Yes |
| Current monthly price in code | €0 | €19 | €49 |
Billing behavior
Sight uses Stripe for subscriptions and one-time purchases. The product supports checkout, plan changes, recovery, receipts, cancellation, and payment-failure handling.
Subscription changes should explain effective timing, prorations, retained data, and features that stop creating new work. Billing state can lag after failed payment or recovery, so operational workflows should rely on the product’s resolved entitlement state rather than a locally cached plan label.
Pricing is a product decision
The values above are the current application constants. Confirm public pricing, tax language, currency behavior, and grandfathering policy before publishing these numbers commercially.
Coordinate application constants with the public pricing page, billing configuration, taxes, contracts, and customer communications. A code value alone is not a complete commercial policy.