What is the current acquisition path for SaSame?
Current acquisition mode (Capability Control Beta), existing-subscriber continuity, plan reference for the record, and commercial integrity boundaries.
- Collection
- pricing
- Updated
- 2026-08-23
- min read
- 7
Capability Control Beta is the current new-user path: sign in, connect an AI client, choose capabilities, use them — no payment required for new users during beta. New paid Factory membership checkout is disabled; Free Listing remains available. Existing subscribers retain all entitlements, renewals and webhooks. CP4 keeps North-Star accounting strict: only independent LIVE payment plus exact verified fulfillment can count; checkout starts, tests, crawler signals and synthetic replays never count.
Start and install
2In this collection
6Current acquisition: Capability Control Beta
New-user acquisition is Capability Control Beta. Sign in to Account Control, connect an authenticated MCP client, choose the capabilities you want active, and use them. No payment method is required for new users during the beta period.
New paid Factory membership checkout is disabled for new users during beta. The factory_membership_checkout tool and the Account Control billing panel both return a structured NEW_MEMBERSHIP_CHECKOUT_DISABLED refusal — not a network error — so agents and UIs can branch on it deterministically.
Free Listing (€0) remains available as always: go to Start and register an already-live MCP — no checkout, ever.
Existing-subscriber continuity
All existing subscriber entitlements, Stripe webhooks, renewal paths and plan capabilities are fully preserved and unaffected by Capability Control Beta. The factory_membership_status tool, the billing status panel and the subscription event store all remain operational. Only new paid membership checkout is paused.
Plan reference (historical — not current purchase path)
These plans exist in the canonical commercial SSoT and remain the technical foundation. They are not a current purchase path for new users during beta.
| Plan | Price | Checkout status during beta | Includes |
|---|---|---|---|
| Free Listing | €0 | Available — no checkout | Unlimited registration/claim of already-live MCPs, best-effort observation |
| Factory | €9/month | Disabled for new users | BYO-LLM Guided Build, guaranteed monitoring, plan-defined slots |
| Factory Pro | €29/month | Disabled for new users | Higher processing level, credentialed audits, history, notifications, exports, API |
| Factory Team | €79/month | Disabled for new users | Team capability profile, organization roles |
| Assisted Review | €99 one-time | Not yet on sale (separate from beta) | Exception review outside standard recipes (not development-for-hire) |
MCP registration is unlimited on every plan, including Free Listing. Plan limits apply only to processing capacity (guided builds, monitoring, audit profiles, API volume) — never to how many MCPs a creator may register or claim.
Full capability matrix
| Capability | Free Listing | Factory (€9/mo) | Factory Pro (€29/mo) | Factory Team (€79/mo) |
|---|---|---|---|---|
| Concurrent guided builds | 0 | 1 | 3 | 10 |
| Managed monitoring slots | 0 | 3 | 15 | 50 |
| Managed monitoring interval | — | weekly | daily | every 6 hours |
| Credentialed audit profiles | 0 | 1 | 5 | 20 |
| Notifications | none | basic | detailed | team |
| History retention | 0 days | 90 days | 365 days | 365 days |
| Repair blueprint depth | none | basic | detailed | detailed |
| Credentialed real-argument calls | no | yes | yes | yes |
| Data export | no | no | yes | yes |
| Factory API access | no | no | no | yes |
| Multi-user / organization roles | no | no | no | yes |
| Inspection queue priority | best-effort | normal | priority re-inspection | priority inspection + repair |
| Published MCPs only (no drafts) | yes | no | no | no |
Slot counts are monotonic — each tier includes everything the tier below it has, plus more. Every limit bounds processing — never how many MCPs you may register or claim.
Unlimited registration
Every plan allows unlimited MCP registration and claiming. Plan limits apply only to processing slots, monitoring level, API volume, priority and other plan-defined service capacity.
CP4 North Star accounting
The CP4 projection records first_organic_paid_revenue as 0/1 in current evidence. Checkout intent, TEST mode, owner/self/synthetic activity, crawler visibility and verified fixture fulfillment are useful operational evidence but never qualifying revenue. #2099 remains open until an independent external actor completes LIVE payment and exact paid fulfillment is externally verified.
Examples
3- 01
Calling a public MCP tool does not create a charge — a payment only begins once you actually start a checkout that is open for real purchases.
- 02
During Capability Control Beta, new users do not need a payment method. factory_membership_checkout returns NEW_MEMBERSHIP_CHECKOUT_DISABLED; existing subscriber renewals are unaffected.
- 03
Starting checkout or completing a synthetic replay does not count as revenue; the count changes only after canonical payment and fulfillment adjudication.