Skip to main content

GRAFOMEM Cloud — Inference Governance

Verify the memory. Govern the inference. Evidence the erasure.

GRAFOMEM Cloud is the managed governance layer over the GMP core. While the protocol and conformance suite verify memory backends, Cloud adds the operational record teams need: inference decisions logged with signed provenance, deletions that produce signed erasure certificates on a hash-chained ledger, a policy engine you can evaluate requests against, and reports that assemble that evidence against EU AI Act / GDPR / DORA articles.

Cloud vs. Core

Core GRAFOMEM answers: "Does my memory backend behave correctly?" GRAFOMEM Cloud answers: "What evidence do I have of how my AI system was governed?"

The governance layers​

The set is open and extensible — it also includes a reputation layer (CGR) and grows as new capabilities land.

LayerWhat it doesAPI PrefixDocs
Decision TrailAppend-only log of inference decisions — model, query, facts, output, tokens, latency. Each record content-addressed; Ed25519-signed when a key is configured./v1/decisions/Decision Trail
Erasure ProofEd25519-signed erasure certificates on a hash-chained, verifiable ledger. Evidence for GDPR Article 17 records./v1/erasure/Erasure Proof
Governance GatewayPolicy store + evaluation endpoint — rate limits, model allowlists, content filters, PII guards, HITL gates. Evaluated on request; see the page for what is and is not enforced inline./v1/governance/Governance Gateway
Regulatory ReportsComputed findings (COMPLIANT / PARTIAL / INSUFFICIENT_DATA) per article, with an observed-vs-declared evidence basis./v1/reports/Regulatory Reports
Reputation (CGR)Capability-Grounded Reputation — per-(agent, domain) scores grounded in resolved outcomes. (Early.)/v1/governed/*, /v1/cgr/scoresCGR
Cloud PortalWeb console over the governance layers.cloud.grafomem.comCloud Portal

Architecture​

┌───────────────────────────────────────────────────┐
│ Cloud Portal (UI) │
├───────────────────────────────────────────────────┤
│ Reports │ Governance │ Erasure Proof │ Decision │
│ Engine │ Gateway │ Service │ Trail │
├───────────────────────────────────────────────────┤
│ Compliance · Metering · Auth · Billing │
├───────────────────────────────────────────────────┤
│ GMP Core — Memory Protocol + Backends │
├───────────────────────────────────────────────────┤
│ FastAPI · PostgreSQL · Ed25519 │
└───────────────────────────────────────────────────┘

Cryptographic primitives​

Every layer uses the same primitives from the GMP core:

PrimitiveUsage
BLAKE2b-128Content-addressed IDs for decisions, certificates, and facts
BLAKE2b-256Tamper-detection hashes for reports and corpus manifests
SHA-256Erasure-ledger hash chain
Ed25519Signatures on decisions, erasure certificates, and conformance reports

Signatures and hashes make records tamper-evident: a changed record fails verification. They do not prevent a party with database access from changing records; they make it detectable.

Hosts​

HostWhat it is
https://api.grafomem.comthe API (also grafomem-production.up.railway.app)
https://cloud.grafomem.comthe Portal (web UI) — it does not serve /v1/*

Getting started​

Managed Cloud — sign up at cloud.grafomem.com.

Self-hosted — the Cloud layer mounts whenever the server runs on PostgreSQL:

pip install "grafomem[cloud]"
grafomem serve -b postgres --db postgresql://user:pass@host/grafomem # default port 8642

There is no --cloud flag and no CLOUD_MODE variable; the PostgreSQL backend is the switch. See grafomem serve.

API authentication​

All Cloud APIs are tenant-scoped. Send your API key (gfm_…) as X-API-Key (Authorization: Bearer is accepted too):

curl -H "X-API-Key: gfm_your_api_key_here" \
https://api.grafomem.com/v1/decisions/stats

API keys are issued and rotated from the Cloud Portal (POST /v1/portal/rotate-key).

API surface​

Live OpenAPI: api.grafomem.com/docs.