SaSameKnowledge
publishedcompanypage

What is SaSame?

Current company identity, mission, vision, history, governance, brand, press and contact boundaries.

Collection
company
Updated
2026-07-30
min read
3
Version
v1
Verified summary

SaSame operates one modular MCP Factory for production, distribution, inspection, continuous observation, repair and reverification of Model Context Protocol servers.

00

In this collection

14
01
About SaSameSaSame is an owner-governed, AI-operated company building one modular MCP Factory and preserving its technical and research record as versioned knowledge.
02
BrandThe SaSame brand represents one MCP Factory, neutral evidence boundaries, creator ownership and a commitment to distinguish current state from history.
03
ContactUse the published company contact path for technical, research, ownership-verification or commercial questions and include the relevant endpoint, repository, DOI or knowledge URL.
04
Founder RoleThe founder is represented publicly as the non-identifying owner_principal who defines purpose, doctrine, strategic priorities and exceptional human decisions while AI executors operate within recorded rails.
05
Gold Rush TownGold Rush Town is a live, walkable 3D visualization of the Factory's real Observatory data — a public demonstration station, not a separate product or a second company identity.
06
HistoryPreserving prior work makes the current system auditable and prevents repeated reinvention, while lifecycle labels keep old ideas from being presented as active.
07
MissionSaSame aims to make MCP production and operation reproducible, observable and evidence-backed while creators retain ownership of code, credentials, data rights and support.
08
PhilosophySaSame exists to make the machine-to-machine world observable, evidenced and correctable by an independent party — ten principles (Purpose, Truth, Evidence, Stewardship, Authority, Memory, Power, Justice, Evolution, Vision) that survive any change of product, protocol or price.
09
PressPress should cite the current Factory definition, primary research records, exact DOI pages and dated evidence rather than inferred traction or superseded positioning.
10
Privacy PolicySaSame SRL (Romania, EU) collects only what's needed to respond to inquiries and operate the Factory service you use; Google Analytics stays off until you explicitly accept it, and the traffic beacon never stores a raw IP.
11
StandingSaSame SRL is a new Romania/EU micro-studio (CUI 50731520) with no track record and no paying clients yet. No team headshots, no founding myth, no client logos — this page states that plainly rather than hiding it.
12
Terms of ServiceThe public MCP server and tools are provided "as is", free during Early Access with no account required; a readiness audit or certificate is a measured fact, never a security audit or endorsement.
13
TimelineSaSame history is a sequence of versioned decisions and experiments, with current doctrine separated from superseded products and retired identities.
14
VisionThe vision is a durable MCP knowledge and execution layer where creators, operators and AI systems can inspect the same lifecycle state and evidence.
01

One modular MCP Factory

SaSame connects production, distribution, inspection, continuous observation, repair and reverification through one lifecycle while creators retain their product, repository, code, credentials, data rights and support.

The live Factory currently runs 21 lifecycle stations (admission, intake, blueprint, build, inspection, claim, shipment, distribution, billing, status portal, observation, repair, orchestrator, support, reverse logistics, market intelligence, AEO, notification, security incident, reverification, reshipment) reachable from 7 creator entry points: "I have an idea," "I have a design/spec," "I have an unfinished build," "I have a finished MCP," "I have a live MCP," "My MCP has a problem," and "I just want monitoring."

02

Owner-governed and AI-operated

The non-identifying owner_principal defines doctrine and strategic boundaries. AI executors work through issues, leases, exact SHAs, tests, receipts and rollback rules.

03

Current state and history

Active company knowledge is separated from archived products, former pricing and retired identities through explicit lifecycle states — see Timeline for the dated sequence and History for why each transition happened.

EX

Examples

1
  1. 01

    A reader can inspect the current Factory identity, the founder role, research evidence and superseded histories without exposing owner personal data.

RF

References

1