constraint · pci-boundaryscope · orgtrust 0.91used 31×
Card data never transits the analytics VPC. Route exports through the tokenised gateway — see incident 2209.
run 2209 · incident reviewapproved · platform leadorg scope · audited
Enterprise · governed private memory
Enterprises are deploying agents across engineering, support, finance, data and operations. Memco captures what those agents learn, curates what matters, and gives future agents the shortcut your organisation already paid to discover — inside boundaries you govern.
deployment saas · vpc · on-prem · uk/eu residency · audit trail
01The missing layer
Wikis, tickets, dashboards and data lakes record what happened. None of them capture what an agent programme learns while working: permissions quirks, workflow exceptions, approval paths, the fix that finally worked. That layer either compounds — or every team, vendor and agent rediscovers it alone.
Knowledge bases and wikis — written for humans, stale by design.
Tickets, threads, retros — where lessons go to be buried.
Data platforms — facts about the business, not judgement about the work.
Captured lessons from real agent runs, with provenance.
Curation that deduplicates, scores and decays without a review queue.
Governed reuse: the next relevant agent starts ahead, inside your boundary.
02One governed workflow
Memco sits beneath your agent stack. Not another chatbot, IDE or platform — the compounding layer underneath them.
eng · support · finance · ops
Agents work
the tools teams already use
fixes · corrections · exceptions
Memco captures
with full provenance
dedupe · score · decay · scope
Memory is curated
no taxonomies — signal from use
permissioned · audited
Governed memory
03The hard boundary
Scopes are isolated at the storage layer. Nothing your agents learn contributes to any pool outside your organisation — there is no blended commons, and Memco does not read your tenant.
Private memory pools
Per-team, per-repo, per-org or per-deployment. Sharing across boundaries is opt-in and explicit.
RBAC & permissioned sharing
Roles and permissions down to a memory entry. Promote, scope or revoke knowledge as a control-plane action.
Provenance
Every memory traces back to the run, agent, repo and human correction that produced it.
Decay
Stale conventions, outdated fixes and obsolete decisions lose weight before they mislead future agents.
Audit trail
Every read, write, promotion and revocation is logged and exportable for compliance.
Retirement
Memory can be edited, deduplicated and retired — deletion is a control, not a support ticket.
tenant-isolated · never trains models
04Provenance & audit
Every entry knows where it came from. Every action on it is logged.
Card data never transits the analytics VPC. Route exports through the tokenised gateway — see incident 2209.
run 2209 · incident reviewapproved · platform leadorg scope · audited
12:04:11 read constraint/pci-boundary agent · finance-07 12:04:12 serve rank 1 · trust .91 14:22:40 promote team → org user · j.okafor 14:22:40 log provenance chain attached
05Deployment & residency
Confirmed options only — and the same MCP/CLI interface in every one of them.
Managed tenant
Dedicated instance in Memco’s cloud, isolated data and compute, per-tenant keys. Hours to deploy.
Your VPC
The Spark instance runs inside your cloud boundary. UK/EU residency options.
On-prem
Entirely behind your firewall. Org memory never leaves customer-controlled infrastructure.
Compliance posture stated exactly as it stands in July 2026 — no badge until the certificate exists.
06Pathfinder
Start with one team, one workflow and one metric. The activation event we design for: a lesson contributed on one task and reused on a second — by a different person, in a different tool.
100+ engineers, regulated, or procurement-heavy programmes.
VPC / on-prem requirements, residency constraints, audit obligations.
Under 100 engineers and self-serve? Start with a team trial instead.
07Security & data flow
the loop
benchmarks · product · research
A short dispatch on shared memory for AI agents — the numbers behind the product, what we're shipping, and the research we're reading. No filler.