Enterprise

Govern memory like any other production system.

Boundaries, auditability, and policy your security and legal teams can support, built on the same core product. We work with a small group of design partners to shape enterprise features and priorities.

Design partners · limited cohortOrg roadmap · in co-design

Program

Where things stand

Current status for the product, the open-source path, and upcoming enterprise capabilities.

Design partner cohort
Open for qualified teams
Layer 1 · kontxt
@4stax/kontxt on npm · GitHub · v0.1. Local vault at ~/.kontxt/ with MCP and CLI.
Enterprise org features
In development with early partners
Hosted org / API surface
Planned. Join the waitlist for early access.

Why this exists

Why chat exports break governance

Screenshots and transcripts are hard to govern. They don’t carry consistent lineage, access controls, or policy context. We’re building memory and vault events that integrate with SSO and your review process.

Most teams start with a narrow use case and expand over time. If you need a full compliance package on day one, we’ll tell you early.

The bar

What procurement is really asking for

Security and legal need proof: what crossed a boundary, under which policy, and who approved it, not chat exports alone.

  1. 01Lineage & proof

    Tie retrieval to policy version and identity, not a folder of screenshots after the fact.

  2. 02Signals for security

    Exports and signals your team can route into SIEM, review, and existing governance habits.

  3. 03Phased rollout

    Start with a thin slice your legal and IT teams can defend, then widen when they are ready.

Roadmap themes

Focus areas

These are the areas we’re building with early enterprise teams.

Enterprise vault

Separation, keys, and policy for multi-tenant memory, co-designed with partners rather than lifted from a datasheet.

  • Namespaces and CMK patterns validated on your workflows before we promise a vendor checklist.
  • Templates that keep legal and engineering aligned on internal vs. partner-facing memory.
Full page

Compliance tooling

Audit trails and retention for teams under real review pressure, built with procurement rather than for a slide.

  • Retrieval history you can defend before we borrow words like “immutable.”
  • Legal hold and retention that survive vendor and model changes.
Full page

Team memory

Shared spaces with roles and revocation that match how people join, move, or leave.

  • Read/write and approvals mapped to identity and HR reality.
  • Fast revocation when roles change, with timelines from pilots rather than marketing.
Full page

Analytics & delivery

Usage, quality, and delivery signals you can pipe into warehouses and BI, not another siloed dashboard.

  • Exports prioritized from how partner teams actually run analytics today.
  • Reviewer and program throughput tied to consent, not vanity metrics.
Full page

How we work

Working with us

  • Built with operators

    We build with a small partner cohort and ship in clear stages.

  • One product, enterprise-ready

    Enterprise features extend the same core product instead of a separate "enterprise edition."

  • Straight answers

    We share what exists today and what is planned, with clear timelines when available.

Engagement

How a partnership starts

A simple process to decide whether a pilot makes sense.

  1. Conversation

    We review your identity setup, data residency needs, procurement process, and success criteria.

  2. Scoped pilot

    If it’s a fit, we run a focused pilot so policy and user experience are validated together.

  3. Co-build

    We plan the rollout and hardening work with you, including multi-tenant boundaries and audit requirements.

Navigate

What you can do next

Email us for enterprise conversations. Everything else is available on the site.

Design partners

Apply with a short brief: stack, region, and what governed memory needs to prove in your environment. We read every note on enterprise@4stax.com.

Elsewhere on the site

Talk to us

For procurement, security review, or pilot scoping, we reply within a few business days.

Questions? enterprise@4stax.com