Start free with kotobase
A tenant-scoped Knowledge Graph BaaS. Create your graph tenant on P2P at no cost, then move to Secure Managed when you need Gftd Japan K.K. to be accountable for uptime — or to Enterprise for a 99.999% SLA and SOC 2-class compliance response.
How signup works. kotobase authenticates every tenant with your existing gftd identity — a authn.gftd.ai session or a self-signed CACAO. Click Start free to sign in / create your identity, then pick a plan to open a Stripe checkout scoped to your tenant DID.
1. Create your identity
Uses your existing gftd account (or creates one) at authn.gftd.ai. No new password for kotobase.
2. Choose a plan
P2P needs no card and carries no operator responsibility. Secure Managed opens a tenant-scoped Stripe checkout and makes Gftd Japan K.K. accountable under a 99.9% SLA. Enterprise is a contract — 99.999% SLA, dedicated infrastructure, compliance response.
P2P — You carry operational risk. 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. is responsible. 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. is responsible under contract. 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.
Prefer the API? See the full docs or Using kotobase as a pin service.