v1.11.0
current releaseLatest public release on GitHub, shipped 2026-07-22. Public-readiness closeout: PR #617 (+10329/-9188 linii) + 39 wcześniejszych PR-ów, w tym operator-mode wisdom 5-layer, telegram vision+exec tier-3, SEGV fix, deps advisories clear, Node ≥22 baseline.Born from Oswobodzeni, built for operators
mE/\/\phi$
Memphis, sovereign AI runtime
Memphis is a sovereign AI runtime for operators who want their own memory, their own tools,
and their own chain of decisions. It combines chain-backed memory, vault-sealed secrets,
observability, and operator control into a system you can install, inspect, and evolve on your own machine.
What this page is for. English-language brand + pillars view for reviewers, journalists and
external devs. If you want the install path and Polish copy, the canonical home is memphis-v5.pl.
If you want the engineering state (release, sprint, next), see the roadmap.
v1.11.0
Kartograf track
local-first
chain-backed
poland
Rust + TS
real coreNot a thin wrapper over one model API.SHA-256
chain-backed memoryContinuity you can inspect and trust.AES + Argon2id
sealed vaultSecrets protected at rest with real crypto.Health / Logs
observabilityStructured signals for real operation.Why Memphis exists
sovereignty, translated into runtime control
Memphis was born from Oswobodzeni, but its public promise must be operational.
Sovereignty here means control over infrastructure, data, secrets, boundaries, and the operator loop.
In a world of rented AI, Memphis is the stack you can actually own and run on your own hardware.
Your machine, your memory, your vault, your operator loop.
System pillars
four things the site must prove fast
Four things the Memphis front must prove fast — memory, vault, observability, operator control.
Not just sound good. Show the system under the hood.
memory
append-only continuity
Memory is a system layer, not a prompt add-on. Every entry is SHA-256 linked and auditable.
vault
sealed secret discipline
Keys and tokens live in vault. Not scattered across scripts and env files.
obs
health and logs
Memphis communicates state through health, metrics and structured logs — not silence.
operator
tool use with control
Runtime works for the operator, not instead of the operator.
Runtime surfaces
multiple ways in, one system underneath
Memphis should be readable for both developers and operators. The public page must clearly show
that Memphis is a full runtime with multiple work surfaces — not just a repo with a readme.
TUI cockpit
Native terminal cockpit for working with memory, vault, sessions and system state.
HTTP + MCP
Integrations via API and agent transports — without locking into one work channel.
Remote surfaces
Telegram and other surfaces as system inputs, not replacements for the runtime itself.
Install
fastest path from interest to operator
This is where the page turns interest into action. Not by flooding with text — just a clean path:
install, init, service, tui. This is the entry point into a real operator workflow, not a marketing dead end.
curl -fsSL https://raw.githubusercontent.com/Memphis-Chains/memphis/main/scripts/install.sh | bash
memphis init
memphis service install && memphis service restart
memphis tui