Run Kumiho Server. On your own machine.
Community Edition is a free, single-user build of the Kumiho graph server. It runs entirely on your machine, talks only to a local Neo4j (and an optional local Redis), and needs no account, token, or cloud connection. Install in one command — the rest is a guided wizard.
Two ways to run Kumiho
Community Edition is the free option. Choose a managed cloud plan when more than one person or remote agents need to reach the server.
Kumiho Cloud (Managed plans)
Managed infrastructure we run for you. Nothing to install, multi-user and agent-ready, with AI Cognitive Memory and cross-session recall included.
- We host Neo4j, Redis, and the server
- Creator, Studio, Studio Pro, and Enterprise plans
- Team collaboration and shared access
- Scale without running graph infrastructure yourself
Community Edition (Self-hosted)
A single binary you run yourself. Loopback-only, tokenless, and fully local — your graph never leaves your machine. Unlimited nodes for a single user.
- You run Neo4j (and optionally Redis) locally
- No data caps — your single-user graph is unlimited
- No account, token, or network connection required
- Single-user and local only — not a shared backend
Install in one command
The installer downloads the latest release binary, verifies its SHA-256 checksum (fail-closed), installs it to ~/.kumiho/bin, and hands off to the onboarding wizard.
# One-line install (macOS / Linux)
curl -fsSL https://github.com/KumihoIO/kumiho-server-community/releases/latest/download/install.sh | sh
# then — re-run the wizard any time
kumiho_server onboard# One-line install (Windows · PowerShell)
irm https://github.com/KumihoIO/kumiho-server-community/releases/latest/download/install.ps1 | iex
# then — re-run the wizard any time
kumiho_server onboard- Downloads the latest release binary from GitHub
- Verifies its SHA-256 checksum — fail-closed on mismatch
- Installs to ~/.kumiho/bin
- Launches the built-in onboarding wizard
Setup — kumiho_server onboard
The installer hands off to the built-in onboarding wizard (run it again any time with kumiho_server onboard). It writes a permission-restricted config to ~/.kumiho/server.toml plus a launch script, and can start the server right away.
- Your local username / email — used to attribute created data; defaults to your OS user
- The Neo4j connection — port, database, credentials
- An optional local Redis port — enables event streams
- The server port — defaults to 127.0.0.1:9190
- Optional OpenAI embeddings — for vector / semantic search
- EULA acceptance
Requirements
Docker is a convenient way to run the databases locally.
Neo4j 5.x
A local instance. Not bundled — bring your own.
Redis 7.x
Enables event streams when configured.
OpenAI API key
Enables embeddings / semantic search.
# Local databases via Docker (Kumiho runs on the host, not in these containers)
docker run -d --name kumiho-neo4j -p 7687:7687 -p 7474:7474 \
-e NEO4J_AUTH=neo4j/your-local-password neo4j:5
docker run -d --name kumiho-redis -p 6379:6379 redis:7
# Point onboarding at the published host ports (7687, 6379)What CE is — and isn’t
CE is a single-user, loopback-only build. The edition is locked at compile time — it cannot be reconfigured into a cloud or multi-tenant server.
Loopback-only
Binds only to 127.0.0.1 and refuses non-loopback peers. Local access only.
Single-user concurrency cap
A built-in cap keeps one user smooth while refusing a second simultaneous user. Not a shared backend.
Tokenless & unauthenticated
The loopback / peer checks are isolation, not a security boundary. Never expose CE to a network or place it behind a proxy.
No data caps
There are no node or data limits — your single-user graph is unlimited.
Verify a download manually
Every release ships checksums.txt so you can confirm the binary before running it.
# Every release ships checksums.txt
sha256sum -c checksums.txt # Linux
shasum -a 256 -c checksums.txt # macOSHealth check
Confirm the server is live and running in self-hosted CE mode.
# With the server running
curl http://127.0.0.1:9190/api/_live
# {"status":"ok","version":"x.y.z","deployment_mode":"self_hosted_ce"}
# /api/_health additionally reports Neo4j, Redis, and embedding readinessLicense & scope
Community Edition is distributed in binary form under the Community Edition EULA. It is licensed for single-user, local use — personal, development, internal, or commercial. Running it as a hosted, shared, multi-user, team, or production-backend service — or needing higher concurrency — requires a separate commercial agreement.
Documentation
The full runbook (self-hosted-ce.md) is included in every release archive and covers configuration, Docker, the Python SDK, and the security model.
Related
Pricing & Cloud plans
Managed Creator, Studio, and Studio Pro plans for teams and scale.
AI Cognitive Memory
The graph-native memory layer — persistent, auditable agent memory.
Revka
Open-source multi-agent runtime that can point at a self-hosted Kumiho endpoint.
Kumiho SDKs
Python, C++, and Dart clients for the graph backend and memory layer.
Free. Local. Yours to run.
Install Community Edition for a single-user graph that never leaves your machine — or compare managed cloud plans for multi-user, agent-ready memory.