the agentic framework that never forgets

kulla is truth.
chat is the working surface.

A new discipline for agents that persist. kulla provides memory, behavior modification, and configuration, for all agents in all environments.

models intelligence The reasoning engine. Interchangeable.
rag knowledge The information store: what the agent can look up.
kulla continuity What the agent remembers, decides, and is allowed to do, over time.
Enterprise agents need all three.
01 · the claims

The load-bearing claims.

Everything follows from one change: move the agent's memory out of the chat window and into a record it owns. Four properties fall out of that discipline.

If you're a Chief AI Officer, VP of AI, or Head of Applied AI accountable for the autonomous-agent projects coming online, you've hit this wall. If you're a Chief Data Officer or CISO responsible for the audit trail and permission gateway around those agents, you know today's tools don't cover the gap. kulla is built for both.

01 · CONTINUITY

Agents that remember forever.

On any context wipe, model upgrade, or Monday-to-Thursday gap, the agent re-reads its record and resumes exactly where it left off, with no re-onboarding tax. Projects, clients, decisions, and rationale hold across the whole engagement, even as people rotate off.

02 · COST

A smaller AI bill.

Selective context retrieval means agents pull only the sections they need, so they never blow the cache — sustaining a 99.995% median cache-hit rate on real workloads. Shared context is cached once and read many, and a mid-tier model on kulla often matches a frontier model running stateless. Net: roughly 75% lower inference cost at enterprise scale (modeled).

03 · PORTABILITY

No vendor lock-in.

The encrypted memory lives on infrastructure you own, never a vendor's servers, never their training set. Move Anthropic → OpenAI → Google on a Tuesday and every decision travels with you. The model is negotiable; the discipline is the identity.

04 · TRUST

Auditable & secure by construction.

Every decision and action is written as it happens: attributable, timestamped, and (in enterprise) hash-chained. Every agent action is gated by an operator-set level: deny · ask · notify · auto. Prompt injection is closed at the framework layer, not patched at the model.

02 · the products

Enterprise governs. The engine is included.

kulla is the framework. kulla Studio is the app that runs it. kulla Enterprise governs a federation of agent workspaces, and kulla Local, the engine it governs, ships inside it. Buy Enterprise and you get both. Local also stands alone for a single operator.

kulla Enterprise Enterprise Ready
The multi-department studio.

Everything Local has, plus a governance layer that makes agentic AI safe to deploy across an organization at scale.

  • Multi-department governance: every department runs its own agents under a shared constitution; cross-department work is brokered, not free-form.
  • Fair resource broker: an enforced starvation bound; heavy workloads can't crowd out light ones.
  • Countersignature validation: decisions that span teams require both sides to sign the ledger.
  • Tamper-evident audit trail: a hash-chained ledger, exportable and independently verifiable.
  • Deny-by-default control gateway: every agent action gated through four permission levels; nothing runs you didn't allow.
  • Governance knowledge graph: organizational context, project state, and client engagements persist across the practice.
Buy Enterprise and the Local engine is included: the same discipline and the same record, with access control and a verifiable audit trail on top.
Enterprise Ready: customer-hosted deployment · DPA available · security artifacts on request
best fit enterprises deploying agentic AI across departments · consulting firms running client engagements at scale · regulated industries
kulla Local
The single-operator studio.

The full framework, on one machine, through a GUI. Your memory in your encrypted database, your model keys, your rules.

  • Runs entirely on your machine: no cloud, no relay, no vendor telemetry.
  • Bring your own model keys: Anthropic, OpenAI, Google, or a local endpoint. Swap providers on a Tuesday.
  • Extremely long-lived agents: survive context wipes, session ends, and model upgrades. Pause Monday, resume Thursday.
  • The full protocol library: decision-before-code, plan-before-multi-day work, enforced by the app, not by folklore.
  • Connector-native: first-party connectors for secrets, databases, and metrics, installed from the app itself.
best fit individual engineers · small dev teams · consultancies on billable work
why it holds

The moat is the discipline.

Better models ship every month. kulla is the discipline that turns them into colleagues who hold across weeks, not tools that reset every session.

01
Portable by construction
The framework runs against any provider; the memory lives on your infrastructure. Swap Anthropic → OpenAI → Google without re-onboarding a single agent.
02
Declared, not retrieved
RAG returns what an embedding resembles. kulla returns what you declared: a structure you design and control, not a similarity score.
03
Auditable to the line
Every decision written as it happens, tagged with what was asserted, how it was checked, and what was observed. Handed over, not reconstructed.
04
Compounds over time
The longer you run it, the more the record holds. More decisions → better inheritance → smaller models doing more of the work.

kulla is not a memory layer, an agent framework, or an observability tool alone. Memory-only tools store what an agent has learned. Agent frameworks help you build agents. Observability tools watch what happens. kulla is the memory-and-behavior layer that ties all three together: persistent context, enforced behavioral discipline, and decision continuity across sessions and across agents, deployed on your infrastructure so your data never leaves it.

03 · the economics

Measured savings. By the work.

The saving isn't one number. Every workload below was run locally through the full Cheapifier pipeline with the real model, and the reduction depends on the kind of work and on how much of it qualifies. We publish both — measured, not projected.

Token reduction by work type 93 local cases · real model · measured
Tool-intensive automation 89%
Software engineering 84%
Customer support 80%
Research and content 71%
Regulated knowledge work 62%
Balanced knowledge work 58%

Tool-intensive automation reaches 89%; broad, mixed knowledge work lands near 58%. Each figure is that scenario's actual sequential token total through the pipeline, reproduced exactly by the calculator.

The mechanism
83%
Tool-surface routing

Only the tools a task needs are exposed. Up to ~83% measured when a broad catalog would otherwise be sent eagerly — the dominant structural saving.

51%
Model & effort routing

Each task runs on the smallest capable model. ~51% measured cost cut versus always choosing the strongest, with every capability, risk, and context-window floor satisfied.

47%
Duplicate-call suppression

Identical reads are served from cache; mutating calls always execute. ~47% measured on a repeat-heavy fixture.

37%
Protected budgets

The working context is fit to a priority budget before dispatch. ~37% measured under history pressure, 100% of required items retained, overflow fails closed.

≈7%
Guarded compression

Meaning-preserving compression on what remains — 100% of protected probes retained. Modest by design (~7% end-to-end), applied last, never before the structural reductions.

How much qualifies — by AI maturity
15% Pilot
35% Emerging
60% Operational
80% Advanced
100% AI-native

The Cheapifier only acts on the share of work that qualifies. That share rises with AI maturity — from a pilot touching a fraction of workflows to an AI-native organization where nearly everything runs through it. Your savings scale with both the work mix and this coverage.

Observed, not guaranteed. 3,447 of 3,447 automated checks and 867 of 867 semantic probes passed across 93 local cases; a separate independent-agent audit re-extracted meaning from every modified context and lost none. The model, tokenizer, and report hashes are pinned. Want a number for your own seats, work mix, and provider? Build an evidence-bounded operating case →

04 · the framework

The discipline, built in.

Six disciplines kulla Studio enforces by construction, automatic in the software, not folklore your engineers pass around.

the ledger

Written as it happens

Every decision, action, and claim is captured the moment it occurs: nothing summarized, actually recorded. Export it to a regulator, query it live, or hand it to a client.

the agents

Long-lived by default

Agents persist across sessions, model upgrades, and reboots. Pause one Monday, resume it Thursday: same identity, same context, same next step.

the protocols

Enforced by the app

Decision-before-code. Plan before multi-day work. Every claim carries what was checked and what was found. The app blocks non-compliant moves: a constraint, not a convention.

the evidence

Unforgeable by construction

Every record carries what was asserted, how it was checked, and what was observed. It's impossible to record a verification that never ran: no agent can claim a check it didn't perform.

the connectors

Plug in from the app

First-party connectors for secrets managers, databases, and metrics, installed from the app itself. Extend the workbench without leaving the workflow.

the admin console

Federation control plane

kulla Enterprise adds an admin surface on top: a shared constitution, a fair resource broker, cross-department countersignature policies, and hash-chained audit export.

05 · the company

The company behind kulla.

MOMUS DEV builds kulla and stands behind it, from a single laptop to the enterprise. Founded and led by Travis Winegar, with founding partner William Chapin (COO track). kulla started from a simple frustration: agents that were brilliant for an hour but useless in three. The fix was giving the model an external memory worth keeping.

We believe all software should be secure, safe, and auditable, and that AI, of all software, is where those three stop being nice-to-haves. Durable AI is an operating commitment, not a download.

Company
MOMUS DEV, LLC
Founders
Winegar · Chapin
Based in
Missouri, USA
IP
Owned outright

All kulla intellectual property, including framework, source code, documentation, and brand assets, is owned outright by MOMUS DEV, LLC, with clean provenance and no third-party encumbrances.

The people behind the company:

06 · faq

Questions, answered.

Straight answers to what buyers and engineers ask first.

What is kulla?

kulla is the agent memory and behavioral framework for enterprise AI. It moves an agent's working memory out of the chat window into a record it owns, so agents keep their context, judgment, and decisions across sessions, model upgrades, and restarts.

How is kulla different from a memory layer or an agent framework?

Memory-only tools store what an agent has learned. Agent frameworks help you build agents. Observability tools watch what happens. kulla is the memory-and-behavior layer that ties all three together: persistent context, enforced behavioral discipline, and decision continuity across sessions and across agents.

Where does my data live? Is kulla customer-hosted?

Yes. Your encrypted agent memory lives on infrastructure you own. It never lands on a vendor's servers and never enters anyone's training set.

Does kulla lock me into one AI provider?

No. The memory lives in your files, not the provider's. You can move between Anthropic, OpenAI, Google, or a local endpoint without re-onboarding a single agent — the decisions travel with you.

How does kulla lower AI inference cost?

Selective context retrieval means agents pull only the sections they need, so they don't blow the cache — sustaining a 99.995% median cache-hit rate on real workloads. Combined with model routing, that lands roughly 75% lower inference cost at enterprise scale (modeled).

Is kulla secure and auditable?

Every decision and action is written as it happens. kulla Enterprise adds a tamper-evident, hash-chained audit ledger and a deny-by-default permission gateway where every agent action is gated as deny, ask, notify, or auto. Prompt injection is closed at the framework layer, not patched at the model.

What's the difference between kulla Local and kulla Enterprise?

kulla Local is the single-operator studio: the full framework on one machine with your own model keys. kulla Enterprise adds multi-department governance, a fair resource broker, countersignature validation, and a tamper-evident audit trail across the organization — and it includes the Local engine.

Who makes kulla?

kulla is built and owned outright by MOMUS DEV, LLC, a software company in Missouri, USA founded by Travis Winegar, with clean IP provenance and no third-party encumbrances.

See the whole picture.

Every claim on this page is backed by measurement or by the framework itself. Tell us what your agents are trying to do, and we'll walk you through what changes when they stop forgetting: what it costs, what it saves, and what it takes to stand up.


We answer directly, usually within a business day.
Direct: sales@momusdev.com