TRUSTED STATE · CONTENT-ADDRESSED GRAPH
Kotobase is a content-addressed graph database for AI state and knowledge. Keep relationships, provenance, and identifiable history together, with tenant-scoped access and managed hosting.
Graph Database · Datalog · SPARQL · Cypher-style · GraphRAG
Free to evaluate. Managed production starts at $25/month; no card required for Free. Live checkout currency is disclosed before payment.
Copy-safe commands from the live agent-quickstart. Inspect each step; this is not a hidden pipe-to-shell.
Health
curl -fsS https://kotobase.net/healthDownload installer
curl -fsS https://kotobase.net/install.sh -o /tmp/kotobase-install.shInspect, then run
sh /tmp/kotobase-install.shPut the CLI on PATH
export PATH="$HOME/.local/bin:$PATH"CLI health
kotobase healthDocker
docker run …HOLD: no public kotobase image or tag is published yet. This is a placeholder, not a runnable pull.
Kotoba Labs is building a safe and ultra-fast stack for AI-generated software. Start with the layer your application needs.
The language: inspectable programs, explicit capabilities, and reproducible benchmarks.Explore Kotoba
The graph database: explicit relationships, content identity, and traceable context.Start Free
Identity and deploy control for the execution environment. Discovery is live; hosted apply is not yet offered.Explore Kotoba Cloud
8 September 2026 · NRT edge · 100 requests per series · 5 excluded warmups · concurrency 1 · 1 test entity
p50 · milliseconds
100/100 successful requests
p50 · milliseconds
100/100 successful requests
p50 · milliseconds
100/100 successful requests
| Operation | p50 | p95 | p99 | Max |
|---|---|---|---|---|
| Biscuit issuance | 32.23 | 110.02 | 123.46 | 144.59 |
| Biscuit verification | 18.26 | 80.78 | 105.49 | 105.64 |
| Authenticated warm query | 741.67 | 961.66 | 1073.58 | 3667.31 |
Single-client production HTTPS latency, including network and authorization. A small two-pattern Datalog point selection; not a throughput, large-graph, controlled cold-cache, or competitor ranking claim.
Every measured query returned the inserted marker. All 300 measured requests succeeded.
Method and raw resultsList prices come from kotobase.plans and the vendor footnotes already on this page. Measured cells cite the 2026-09-08 NRT p50 cards above, or stay empty when we have no measurement.
| Offering | List price | Measured | Notes |
|---|---|---|---|
| Kotobase Free | $0 (kotobase.plans public-price) | 2026-09-08 NRT p50: biscuit issuance 32.23 ms · biscuit verification 18.26 ms · authenticated warm query 741.67 ms | Hosted secure storage. No availability SLA. |
| Kotobase Starter | $25 / month (supabase.com/pricing analogue, 2026-08-14; kotobase.plans) | 2026-09-08 NRT p50: biscuit issuance 32.23 ms · biscuit verification 18.26 ms · authenticated warm query 741.67 ms | Individual / engineer rung. Live checkout is ¥3,750. |
| Kotobase Professional | $132 / month (kotobase.plans; live Stripe ¥19,800) | 2026-09-08 NRT p50: biscuit issuance 32.23 ms · biscuit verification 18.26 ms · authenticated warm query 741.67 ms | Aura Professional 2 GB band analogue. Shared production endpoint. |
| Kotobase Business Critical | $292 / month (kotobase.plans aura-analogue 2 GB band) | Sales-led. 99.95% / 24x7 are contractual, not on the shared endpoint. | |
| Neo4j AuraDB Free | $0 (kotobase.plans aura-analogue; Aura Free, read 2026-07-30) | 200,000 nodes / 400,000 relationships. No invented latency. | |
| Neo4j AuraDB Professional | $65.70/month (1 GB); $131.40/month (2 GB). neo4j.com/pricing, checked 2026-08-27. | RAM-hourly. Empty measured cell: no Aura latency is published here. | |
| Neo4j AuraDB Business Critical | $146/GB·month, 2 GB min ≈ $292 (kotobase.plans aura-analogue) | 99.95% / 24x7 on Aura's published band. No invented latency. | |
| Supabase Pro | $25/month (supabase.com/pricing, 2026-08-14; kotobase.plans Starter analogue) | Not a graph database. Cited only as the Starter price analogue. |
Aura public prices from neo4j.com/pricing, checked 2026-08-27. Kotobase USD list uses the footnote FX in kotobase.plans (¥150/$, ADR-2606130100). Empty measured cells are unknown, not zero.
Agents forget between sessions. Retrieval returns disconnected chunks. Operating graph infrastructure steals time from the application you are building.
Keep useful entities, claims, and relationships available across sessions.
Represent how people, events, documents, and decisions relate — not only which text looks similar.
Use hosted secure storage, then a managed SLA when a production team needs one.
Give agents memory that survives the session instead of isolating knowledge in chat history.
Store and query entities, claims, and relationships instead of only disconnected chunks.
Expose the same tenant-scoped graph through APIs and MCP.
Preserve graph state and provenance through content-addressed commits.
Traditional RAG is useful for finding related passages. Graph-backed AI adds explicit entities, claims, and relationships so an agent can follow connected context.
Kotobase complements retrieval; it does not claim that every workload should replace vector search.
Applications and agents access the graph within the same tenant identity boundary.
Signed immutable commit CIDs make the selected graph state explicit and reproducible.
Clients can query, cache, compute, and contribute verified CID-addressed results.
Give agents a graph tool surface without building one-off retrieval glue for every application.
https://kotobase.net/mcp
Tools are generated from the same published lexicons used by the application API.
Represent the people, products, organizations, documents, and events your application reasons about.
Keep assertions and their graph context available across sessions and applications.
Use Datalog, SPARQL, or Cypher-style query surfaces for the shape of query you need.
Bind work to content-addressed graph commits instead of an implicit mutable database state.
Kotobase is an option to evaluate when you want a knowledge graph for agents and applications, MCP access, managed hosting, or content-addressed provenance.
| Evaluation factor | Kotobase |
|---|---|
| Start | Free hosted secure storage; no credit card required |
| Managed production entry | $25/month. AuraDB Professional starts at $65.70/month (official public price checked 2026-08-27). |
| Agent access | MCP |
| Knowledge graph | Yes |
| Managed option | Yes — Starter, Professional, Business Critical, Enterprise |
| Query | Datalog, SPARQL, and Cypher-style |
| Provenance | Content-addressed commit CIDs |
| Dedicated option | Yes — Enterprise contract |
Source: Neo4j AuraDB pricing. Prices exclude taxes and usage outside each plan's included limits.
Production scope as of 2026-08-15. Supported syntax, measured evidence, and open gaps are separated so a subset result is not presented as general graph-database performance.
| Area | Current production specification |
|---|---|
| Storage and truth | Signed immutable CID commit DAG; R2-backed immutable blocks and conditional graph heads. Durable Objects, D1, PostgreSQL, and an S3 mutable database are not correctness dependencies. |
| Cypher-style read subset | Labels, parameters, property projection, DISTINCT, ORDER BY/SKIP/LIMIT, NOT/AND/OR predicates, one materializing WITH stage followed by MATCH, simple CASE plus CASE WHEN variable IS NULL, and directed/undirected variable-length paths in primary and OPTIONAL MATCH. OPTIONAL traversal runs under the left join and null-fills misses. A 2026-08-15 production probe combined these new operators and returned the expected row through kotobase.net on graph Worker 838a5a03-f307-46f2-99b8-4717a0573096. This remains a bounded subset, not full openCypher or a performance claim. |
| Planner and joins | Path-free basic graph patterns are handed to the peer statistics planner as one BGP: it measures visibility-scoped clause cardinalities or consumes fresh scoped materialized statistics, cost-orders clauses, and passes estimates to join strategy. Hash natural joins and binding push-down are used around OPTIONAL/WITH stages. Variable-length path interleaving still uses bounded heuristics; this is not a general cost model for every Cypher operator. |
| Cypher writes | Authenticated CREATE of standalone nodes with a required non-empty id uses the same graph-policy check, immutable transaction/commit blocks, conditional R2 head CAS, nonce replay protection, and conflict retry path as datom transact. The 2026-08-15 production probe created created/1 with HTTP 200 and read the graph back. Relationship CREATE, CREATE after MATCH, MERGE, SET, REMOVE, and DELETE are rejected. |
| SQL JOIN read subset | Bounded SELECT over datoms and request-scoped external tables. INNER/LEFT/RIGHT/FULL/CROSS and non-equality joins, derived tables to depth 2, GROUP BY, and COUNT/SUM/AVG/MIN/MAX are supported across at most four sources. Datom scans/results stop at 1,000 and intermediate joins at 10,000. External tables are finite scalar rows supplied in the request, not arbitrary network/database connectors. A 2026-08-14 production probe passed FULL external JOIN, grouped derived-table, and LEFT non-equality JOIN shapes; this is functional evidence, not a performance claim. HAVING, CTE/UNION, windows, DML, comments, and multi-statements remain unsupported. |
| Cold reads | CID verification, Cache API/R2 block fetch, query-ordered pack Range support, and bounded client caches. The published 12.5M-datom qualification policy requires three independent empty-client-cache samples and cold network ceilings of 5 s for point lookup and 12 s for two-hop traversal; its receipt measured cold p99 2.231 s and 6.264 s. This is a reproducible engineering envelope for those two shapes, not a contractual SLA or an arbitrary-query guarantee. |
| Same-graph writes | Optimistic conditional-head CAS, full-jitter exponential backoff, 12 attempts by default (operator-bounded 1–16), then HTTP 409 with Retry-After and retry metadata. Writes are not lock-free successes under arbitrary contention; no acknowledged write may be reported before its CAS wins. |
| Scale evidence | Historical LDBC SF-0.1 receipt: 3,013,602 datoms and five of seven Interactive Short queries. IS2's WITH shape and IS7's OPTIONAL path/CASE IS NULL shape now pass end-to-end tests, but the historical latency receipt has not been relabelled or rerun. SF-1 converts to 25,522,216 datoms; no completed 100M-datom production qualification exists. |
| Comparison claim | No general Neo4j, Neptune, GraphDB, or Datomic performance superiority claim. There is no audited LDBC Neo4j result to compare against; published local paired results apply only to their exact bounded workloads. |
Use the API or point an MCP-capable agent at https://kotobase.net/mcp.
Write entities, claims, and relationships, then query the same tenant-scoped graph from agents and applications.
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=kotobaseAuthenticate with Passkey or SIWE, then authorize API operations with a short-lived tenant- and graph-scoped Biscuit. CACAO and opaque Bearer remain migration-only compatibility paths. Public exact-CID reads are live at /ipld/:cid; canonical queries select an explicit signed commit CID rather than a mutable database head. Built on kotoba.
Start with Free hosted secure storage. Choose Starter or Professional when you want Kotoba Labs Inc operating the graph. Business Critical and Enterprise are contract rungs for HA and dedicated deployments.
$0
Developers evaluating Kotobase and small graphs that need a secure hosted place to live.
You carry operational risk
Hosted secure storage for your graph. Encrypted in transit and at rest. No credit card. No availability SLA.
The operator hosts the graph as encrypted multi-tenant storage and does not ask you to run a peer. Availability is still best-effort: 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. That allocation is why this rung is free.
$25 / month
Individual developers and small engineering teams who need hosted encrypted storage without a $65+ company graph bill.
Kotoba Labs Inc is responsible
Hosted secure storage at the Supabase Pro price. For individuals and engineers, not a company Aura 1 GB bill.
Kotoba Labs Inc hosts and operates the graph on this plan. The public price is $25/month — the band an individual engineer already pays for Supabase Pro. Checkout is self-serve; the charge is ¥3,750 per month. The Aura Professional 1 GB company band ($65) is a separate sales quote.
$132 / month
Production applications that need the Aura Professional 2 GB band, flat, with a 99.9% SLA.
Kotoba Labs Inc is responsible
Aura Professional 2 GB band, flat. Kotoba Labs Inc operates it. 99.9% SLA with service credits.
Kotoba Labs Inc 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.
$292 / month
Production graphs that need Aura Business Critical's HA and 24x7 band, not only a 99.9% shared endpoint.
Kotoba Labs Inc is responsible under contract
Aura Business Critical 2 GB band as a flat monthly BaaS. 99.95% and 24x7 by contract.
Kotoba Labs Inc quotes this rung against Aura Business Critical's 2 GB floor. 99.95% availability and 24x7 support attach only to a contracted deployment that clears the multi-region write and on-call gates. They are not offered on the shared production endpoint.
Custom contract
Financial, medical, government, and enterprise data teams under audit or regulatory obligation.
Kotoba Labs Inc is responsible under contract
99.999% SLA, SOC 2-class compliance response, dedicated infrastructure. By contract.
Kotoba Labs Inc 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, counsel-approved privacy terms where available, 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.
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.
Available only by signed contract on a dedicated deployment that clears the readiness gates in docs/PLANS.md; it is not offered on the shared endpoint.
Available today: Data Processing Addendum (DPA), Security questionnaire and audit response.
Legal review required: Business Associate Agreement (BAA). It is not available for execution until qualified counsel approves it.
In preparation: SOC 2 Type II, ISO/IEC 27001, ISMAP (Japan government cloud registration). No report or certificate has been issued yet.
Data residency (in-jurisdiction cold pins); Read audit (universal read receipts); Customer-held key custody (HYOK/KMS).
Named technical account manager, dedicated escalation channel · 15 minutes for P1, 2 hours for P2 · 24x7
Keep Obsidian as your local-first writing space and Markdown as the source of truth. Sync notes, frontmatter, and [[wikilinks]], then query the vault as a graph.
Pinned commit blocks can be archived as CAR files to an S3-compatible immutable object store. Providers improve availability but do not choose graph truth.
No. Applications and agents can query the same tenant-scoped knowledge graph through APIs and MCP.
Not necessarily. Vector search finds similar content; a knowledge graph preserves explicit entities, claims, and relationships. They can be used together.
Kotobase offers a Cypher-style query surface, but this page does not claim wire compatibility. Validate your schema and queries before migrating.
Yes. Free hosted secure storage has no payment checkout. Starter and Professional are live self-serve subscriptions. Business Critical and Enterprise are quoted by sales.
Start with a connected knowledge graph for agents and applications.