Example HostingTomaTíoby Example Hosting

Why TomaTío

Regulation lets you get your data out. The Portable Context Protocol makes sure it arrives somewhere useful.

With its structure, rules and history intact, and only the parts you choose. No AI provider has a reason to build that for its competitors, so it has to be an open standard. That, delivered by the hosts people already use, is TomaTío.

Three things together

Each exists somewhere. The combination is the project.

Portable

Context that moves whole

The Portable Context Protocol (PCP), an open standard, carries a team's whole working context between tools and hosts, a piece at a time if you want.

  • Memories, approved knowledge, procedures and house rules
  • Scopes, shared documents and handoffs, with their history
  • Erasure receipts that travel with the archive

Distributed

Where people already are

A WordPress plugin, so it runs on the software behind over 40% of the web, and reaches teams through the hosting companies they already pay.

  • Hosts can offer it free with their plans
  • Runs next to your sites, on your host's servers
  • An upgrade path hosts already know, like shared hosting to VPS

Open

Owned by its community

Nobody can close it later, and a host that builds on it adds to it rather than competing with it.

  • The plugin is GPL; the PCP specification is open
  • Hosting companies are invited to contribute
  • Your context stays on servers you or your host control

Portability, compared

What “you can take your data with you” means today, and what PCP adds.

AI provider exportRegulationGDPR Art. 20, Data Act, DMAPCP
What movesA dump: chat transcripts, a flat list of “memories”Data you provided, in a machine-readable formatThe working context: memories, approved knowledge, procedures and house rules, scopes, documents and handoffs, with their history
StructureEach provider's own shapeNot specifiedOne open schema with a manifest, hashes and counts, checked by a conformance suite
GranularityAll or nothingAll or nothing in practiceBy scope: one project, one team, work apart from personal
ImportNone: nothing on the other side reads itNot requiredDefined: restore into an empty brain, or import as proposals a person reviews, never a blind merge
Trust and historyLostNot coveredWho wrote what and what was approved travels with it, along with the audit log
DeletionSeparate, unverifiableA right, without proofErasure receipts and tombstones, carried in every archive
InteroperabilityNoneEncouraged, rarely achievedThe point of the protocol: an open specification and a conformance suite, so any tool can implement it

Bill of Rights

What every TomaTío brain promises the people who use it.

  1. Your memory is yours.You can see all of it, at any time.
  2. Take it with you.Export it any time with PCP and move it to any host or tool.
  3. Delete it.Erase what you choose, with a receipt.
  4. No lock-in.An open protocol and an open format, not a proprietary store.
  5. You decide what your team knows.AIs can remember and suggest; only a person approves what becomes shared knowledge.
  6. Free software.The code is GPL: anyone can run, study, change and share it.

Ships with the invite-only beta, when PCP export opens to everyone. See the launch roadmap.

Why it matters

Two risks grow as AI agents do more of a team's work.

No single vendor should hold the context

Whoever holds the working memory of people and organisations (what they know, how they work, what they decided) holds a moat. Switching gets harder, alternatives starve, and customers lose their leverage.

An open, structured, importable format that any tool can implement works directly against that concentration.

People stay in charge of their agents

Each agent sees only its scopes. Every action is attributed to the agent and the person behind it, a person approves what becomes shared knowledge, and everything is in an audit log.

As agents act for teams, that is how teams keep control, and PCP makes that control portable too.

See it working

A live brain, connected to Claude, on WordPress 7.1.3.