kotobase

Knowledge Graph BaaS for engineers and enterprises. Build tenant-scoped graph apps on kotoba with Datomic/Datalog, SPARQL/Cypher-style query, MCP tools, durable graph hosting, and content-addressed provenance over IPFS.

Start freeRead API docsStart with curl

GraphDB without operating graph infrastructure. Ingest facts and relationships, query the graph, pin every commit as a CID, and hand the same API surface to applications, data teams, and AI agents.

Start with a graph or a CID

ipfs pin remote service add kotobase https://kotobase.net <JWT>
ipfs pin remote add  --service=kotobase --name=my-doc <cid>
ipfs pin remote ls   --service=kotobase
ipfs pin remote rm   --service=kotobase --cid=<cid>

Authenticate with a gftd-AUTHN JWT (Bearer) or self-signed CACAO. A public retrieve-by-CID gateway is in progress (see the pinning docs) and not live yet.

Product surface

Graph database API

Datomic/Datalog reads, Datom writes, and SPARQL/Cypher-style graph query through tenant-bound XRPC.

Knowledge-graph ingest

Write entities, claims, and relations into tenant graphs, then pin the resulting commit CID.

MCP for AI agents

https://mcp.gftd.ai/mcp — tools generated from the same lexicons for agent workflows.

IPFS pinning & gateway

POST/GET/DELETE https://kotobase.net/pins. Public CID retrieval gateway in progress, not yet live.

Why teams use it

For engineers

Prototype graph-backed apps without running Neo4j, RDF stores, IPFS nodes, or graph provenance infrastructure.

For enterprises

Keep graph state reproducible: every graph commit is content-addressed, retrievable, and auditable by CID.

For AI systems

Expose the same tenant KG to applications and agents through XRPC and MCP instead of one-off retrieval glue.

For regulated plans

Dedicated tenant design, CACAO-only auth, read-audit, key custody, and crypto-shred architecture are tracked in ADRs.

Plans

Free

100 MB, 3 pins. Developer trial for API and graph workflow validation.

Standard

50 GiB, 1,000 pins. Self-serve graph workspace for solo projects and small apps.

Pro

500 GiB, 10,000 pins. Production teams, larger graphs, and operational support.

Regulated

Dedicated graph infrastructure, audit, key custody, and compliance review by contract.

Durability

Every pinned commit's blocks are packed into one CAR and archived off-site to Backblaze B2 (CAR-on-B2): a content-addressed second copy that scales (object count ∝ commits, not blocks). Cold reads are served from B2 via a single ranged GET. The local durable tier is the kubo (IPFS) blockstore on the pod's PVC.

Docs