- Layer 1, live
- Local-first
- Open source
Memory that survives every model switch.
kontxt is 4StaX Layer 1, a memory layer that stays consistent across AI products without relying on a single vendor's memory cloud.
4StaX ships memory first, then vault, marketplace, and programs. kontxt is the shipping on-ramp.
Where 4StaX is headed
- 01Memorykontxt ships today.
- 02VaultData with real governance.
- 03MarketplaceOptional value with clear consent.
- 04Programs and APIsTraining, quality, hosted access over time.
Why this exists
Continuity is the baseline for trust.
When every session starts cold, work slows down and context gets repeated. kontxt closes that gap with a portable memory layer that can follow work across tools.
Memory belongs to the operator, not the interface.
The stakes
Every new chat should not start from scratch.
- Fragmented context
- Different assistants do not share context. Background and preferences get repeated until it becomes busywork.
- Control stays with people
- Most platforms optimize for retention and data exhaust. 4StaX is built so people keep agency as the stack grows, not as an afterthought.
- Memory is the wedge
- If memory works across tools, everything else can attach to the same spine. Vault, marketplace, and programs do not need to reinvent identity every release.
How it should feel
Three beats of the experience.
A product-level overview of the experience and what this layer unlocks.
Write once, reuse everywhere
kontxt captures what matters in a vault under operator control. The same memories surface in Cursor, Claude Desktop, or any MCP host, without reintroducing everything in every product.
Continuity that compounds
A durable thread of context persists across tools. This is not vendor lock-in for “training.” It is Layer 1 of a larger personal data OS. Vault, marketplace, and programs attach to the same spine over time.
Respectful defaults
Local-first means memory can live on a machine first. What graduates to the cloud stays a choice, not a hidden default in someone else’s roadmap.
Who it is for
Built for people who live in more than one AI surface.
Built for power users, teams, and builders who need continuity across assistants, models, and workflows.
- People who use more than one AI product in a week and are tired of re-explaining themselves.
- Teams and builders who need persistence across models without locking into a single vendor’s memory cloud.
- Anyone who wants open, inspectable memory, not a black box that only works inside one app.
Framing
Without a portable memory layer vs. with kontxt.
Typical silos
- Every new chat forgets what the last one knew.
- Context lives in silos tied to each product’s business model.
- Switching tools means re-building trust and background from zero.
Portable memory
- One memory layer you can point multiple assistants at.
- A path toward vault, governance, and optional value, with clear consent.
- Open package and docs. Evaluate the system before committing.
Vision
Available today, with a clear path forward.
Start with kontxt today. Vault, marketplace, and other products will build on the same foundation as they launch.
- Shipping
Memory stack
kontxt keeps context consistent across assistants. Local-first, open, and user-owned.
- Roadmap
Data stack
A vault with real permissions and revocation, so sensitive work gets governance instead of guesswork.
- Roadmap
Intelligence stack
Continuity that compounds over time, not just the last prompt.
- Roadmap
Value stack
Opt-in data and training programs with clear consent and economics.
Questions people ask first
Is kontxt another chat app?
No. kontxt is infrastructure (MCP + CLI) that sits beside the apps teams already use. The Developer hub maps products, the kontxt developer page covers integration detail, and docs.4stax.com holds full reference.
Do I have to send everything to the cloud?
No. The design starts local-first. Cloud and hosted surfaces are optional on the roadmap.
How does this relate to the rest of 4StaX?
kontxt is Layer 1, memory. Vault, marketplace, and programs share the same long-term arc. kontxt can be adopted without committing to the full platform vision.
Where do install, MCP, and APIs live?
The kontxt developer page provides the integration overview. Full flags and host snippets live on the documentation site as it expands.
Developer resources
kontxt integrates through the npm package, MCP hosts, and the CLI. The developer hub covers products and libraries, and the docs include full reference.