What should users know before using SaSame?

SaSame, operated by SASAME S.R.L., continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history. Pancho is SaSame's internal operating organism. SaSame also generates and simulates hypotheses, launches bounded Missions, routes capabilities through HOCR, records evidence, and turns outcomes into reusable knowledge; the MCP Factory (with permanent independent observation and evidence stations) is internal machinery and an optional product surface behind that one service.

No. Creators retain the product, repository, code, credentials, data/API rights, actual repair and support. Normal Guided Build is BYO-LLM.

No. Public tool calls do not themselves create a charge. Paid access begins only through an explicit LIVE checkout.

Free Listing, Factory, Factory Pro and Factory Team are LIVE. Assisted Review is not currently purchasable.

Its €99 one-time price is approved, but it isn't for sale yet — we haven't finished building and verifying what happens right after someone pays, and we don't sell things we can't yet deliver.

No. Registration and claiming are unlimited. Paid limits apply to processing and service capacity, not portfolio size.

No. It is a bounded record of what was observed, when, how and with which limitations.

It proves control of a stated identity or resource through a defined challenge at a stated time. It is not legal title adjudication or copyright registration.

No. Monitoring provides repeated, time-bounded observations and history according to the applicable plan and method.

Yes. The website, Knowledge API, search and read-only MCP share the same document and relation model.

No. Archive records preserve history with lifecycle labels and cannot override current products, pricing, doctrine or API contracts.

A real person may still be involved behind the scenes in delivering some of this. We don't claim something is fully automatic unless we've actually verified that it runs without a human in the loop.

Concurrent guided-build slots (1 / 3 / 10), managed monitoring slots and cadence (3 weekly / 15 daily / 50 every 6 hours), credentialed audit profiles (1 / 5 / 20), history retention (90 / 365 / 365 days), and — starting at Factory Pro — data export, then at Factory Team, Factory API access and multi-user organization roles. See Pricing for the full matrix.

Only how often, and how much capacity. A paid plan never changes what an inspection or reverification measures — every plan passes the same inspection criteria, and no plan buys a better observation result.

It's encrypted the moment we receive it. Only the automated system that runs your audit can use it, and nobody — including us — can read it back afterward. We only keep a reference pointer and a few non-sensitive details about it, never the credential itself.