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 industries

Dedicated tenant, CACAO-only auth, read audit, key custody, and crypto-shred architecture, with a 99.999% SLA by contract.

Plans

Three plans, separated by who carries the risk. On P2P the operator carries no responsibility at all — run your own peer, or use the shared endpoint as-is. On Secure Managed Gftd Japan K.K. operates the service and is accountable for it, with a 99.9% monthly SLA and service credits. On Enterprise that accountability is contractual and goes further: a 99.999% SLA, SOC 2-class compliance response, and dedicated infrastructure.

P2P

You carry operational risk

Run your own peer, or use the shared endpoint as-is. No operator responsibility.

  • Availability: No availability commitment
  • Support: Public docs and repository issues
  • Included: 100 MB, 3 pins on the shared endpoint; unmetered on your own peer
Start free

Secure Managed

Gftd Japan K.K. is responsible

Gftd Japan K.K. operates it and is accountable for it. 99.9% SLA with service credits.

  • Availability: 99.9% monthly SLA
  • Support: Email support · 1 business day · Business hours, JST
  • Included: 500 GiB, 10,000 pins included; usage expansion beyond that
Subscribe

Enterprise

Gftd Japan K.K. is responsible under contract

99.999% SLA, SOC 2-class compliance response, dedicated infrastructure. By contract.

  • Availability: 99.999% monthly SLA (by contract)
  • Support: Named technical account manager, dedicated escalation channel · 15 minutes for P1, 2 hours for P2 · 24x7
  • Included: Contracted capacity on dedicated infrastructure
Contact sales

Who is responsible

PlanAccountable partyAvailabilityHow to start
P2PYou carry operational riskNo availability commitmentSelf-serve, free
Secure ManagedGftd Japan K.K. is responsible99.9% monthly SLASelf-serve subscription
EnterpriseGftd Japan K.K. is responsible under contract99.999% monthly SLA (by contract)Contract — hello@gftd.co.jp

P2P. The operator accepts no responsibility on this plan. The service is provided "as is" and "as available" with no availability commitment, no service credits, no incident-response obligation, no recovery objective, and no support obligation. You run your own peer, or you accept the shared endpoint's best-effort behaviour and design your application to tolerate it.

Secure Managed. Gftd Japan K.K. carries operational responsibility on this plan: it operates, monitors, patches, and recovers the service; it commits to a 99.9% monthly availability SLA backed by service credits; it acknowledges customer-reported incidents within one business day; and it holds itself to the published data-handling and security boundary. Availability is measured by the daily SLO gate, whose receipts are committed to the repository.

Enterprise. Gftd Japan K.K. carries operational responsibility on the terms of a signed enterprise contract, which can exceed the published ones: a 99.999% monthly availability SLA with a service-credit schedule, 24x7 named support with a 15-minute P1 acknowledgement, dedicated tenant and infrastructure, a DPA and (where applicable) a BAA, data-residency commitments, customer-held key custody, read audit, and agreed retention and deletion policy. These commitments attach to the dedicated deployment the contract provisions; they are not offered on the shared production endpoint.

The binding version of these statements is the Terms of Service (§6 plans, §7 service levels, §8 limitation of liability); the engineering detail is in docs/PLANS.md.

Enterprise commitments

99.999% availability SLA

A 26-second monthly error budget, with service credits: below 99.999% → 10% of the monthly fee; below 99.99% → 25% of the monthly fee; below 99.9% → 50% of the monthly fee; below 99.0% → 100% of the monthly fee, plus termination for cause without penalty.

Signed per contract, on the dedicated deployment that contract provisions — it is not offered on the shared endpoint. The readiness gates the deployment must clear are listed in docs/PLANS.md.

Compliance response

Available today: Data Processing Addendum (DPA), Business Associate Agreement (BAA), Security questionnaire and audit response.

In preparation: SOC 2 Type II, ISO/IEC 27001, ISMAP (Japan government cloud registration). No report or certificate has been issued yet — we will not claim otherwise before it has.

Provisioned per contract

Data residency (in-jurisdiction cold pins); Read audit (universal read receipts); Customer-held key custody (HYOK/KMS).

Support

Named technical account manager, dedicated escalation channel · 15 minutes for P1, 2 hours for P2 · 24x7

Contact sales

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