History
Why does SaSame preserve unsuccessful or superseded work?
Preserving prior work makes the current system auditable and prevents repeated reinvention, while lifecycle labels keep old ideas from being presented as active.
Search the graph
Find current SaSame knowledge.
Current company, Factory, documentation, research, evidence, product and API records are searched by default. Historical records are available only when you explicitly include them.
Refine
Clear filtersCollections
Include historical recordsHistorical records are visible and explicitly labelled as not current.
Return to current recordsResults
All · #archive · history included15 knowledge records
Mission Archive
What does the SaSame Mission Archive preserve?
Historical products, architectures, pricing and research are preserved for provenance in a separate, explicitly non-current collection.
Advertising Service Vertical
Is SaSame still selling a standalone Ads service?
No. The former Ads vertical is retired and is not part of the current MCP Factory commercial ladder.
AI Automation Studio Portfolio
What happened to the former SaSame AI automation studio portfolio?
The portfolio documented an earlier AI automation and integration studio model. That model is superseded by the one MCP Factory, while the public code examples remain preserved as historical case studies.
AI Consulting Service
Is the former general AI consulting service still offered?
No. General AI consulting is superseded by the bounded MCP Factory lifecycle and is not a current standalone SaSame service.
Client Portal Application
Is SaSame still operating a separate client portal application?
No. The former client-portal application was fully retired 2026-08-02; identity, organization membership and billing now run through Account Control.
Dental Service Vertical
Is SaSame still offering a standalone Dental service?
No. The former Dental vertical is retired as a standalone offer; historical assets are preserved privately and do not represent a current product or outreach programme.
Deprecated APIs
How should deprecated SaSame APIs be handled?
Deprecated APIs remain documented for migration with replacement endpoints, sunset state and compatibility limits.
Firme Marketplace
What happened to the Firme marketplace and Romanian business directory?
Firme was a short-lived Romanian directory and request-for-quote marketplace experiment. It is retired as a product; the static research assets are preserved for audit, while no current customer marketplace or account service is offered.
Legacy Blog Host
What happened to the former standalone SaSame blog host?
The standalone blog host is superseded by the canonical Knowledge Blog collection, with historical material retained only when it remains accurate and properly labelled.
Legacy Public Pages
Where did the former SaSame company, solution and campaign pages go?
Former company, solution, campaign, comparison, division and landing-page groups are superseded by the canonical Knowledge collections and preserved only as bounded history.
Marketing Service Vertical
Is SaSame still operating a standalone Marketing service?
No. The former Marketing vertical is retired and does not represent a current product, division or autonomous campaign surface.
Nihongo Service
What happened to the former Nihongo service?
The former Nihongo human service is closed. Its public host retains a truthful closure notice and the retired backend remains stopped.
Passport-First Model
What was the Passport-first model?
Passport-first positioned identity and verification artifacts as the primary product; it is superseded by the one-Factory lifecycle.
Sales Service Vertical
Is SaSame still operating a standalone Sales service?
No. The former Sales vertical is retired; sales operations now support the one MCP Factory rather than forming a separate customer product.