Insights & Memory

Stop re-explaining the same system every sprint

Insights and Memory keeps project decisions, diagrams, and post-mortems where the next thread can find them - without a wiki graveyard.

  • Decisions · schemas · debt
  • Surfaced in future sessions
  • You control what is promoted
project-memory.md - captured context
Work“Ship auth hardening”
CaptureDecision + diagram saved
LinkAttached to services touched
ReuseNext thread picks it up
Insights & Memory

From scattered notes to durable project memory

Promote what matters - architecture calls, incident learnings, and schema intent - so new work starts aligned.

  • Auto-capture useful context as you ship
  • Link memory to services, modules, and incidents
  • Reuse context in future sessions without re-uploading
  • Keep sensitive material behind your access controls
  • Pair with Research and Strategy for higher-stakes decisions
Memory type: Architecture
Source
Freshness
Audience
project-memory.md
Preview
// Promoted insight:
"Record decision: JWT rotation cadence + owner"
Decision: rotate signing keys every 90 days
Owner: platform security
Affected: auth service, mobile clients

Links:
- ADR-014
- Incident retro 2026-03-12

Next review: Q2 security council
1Work
2Capture
3Link
4Promote
5Reuse

What teams get from Insights & Memory

Less archaeology

Future sessions start with the decisions that mattered.

Faster rampLess rehash

Better incident follow-through

Learnings stay attached to the services they touched.

TraceableActionable

Controlled promotion

You decide what becomes durable memory vs ephemeral chat.

GovernedIntentional

Best-fit scenarios

Use Memory when teams churn or systems grow

Microservices, migrations, and compliance-heavy programs benefit most.

Durable Linked Reusable Governed
How it works

Build durable memory in three moves

Treat memory as a product, not a dump.

Ship with notes

Capture decisions while context is hot.

Link to reality

Attach memory to modules, services, and tickets.

Promote deliberately

Keep only what future teams must reuse.

FAQ

Insights & Memory FAQ

Does this upload our whole repo?

No. Follow your data boundary policy; memory should capture decisions and references, not secrets.

Who can see promoted insights?

Use workspace roles and project boundaries consistent with how you already share code.

How do we avoid stale docs?

Assign owners, date decisions, and archive superseded entries on a cadence.

How do we measure value?

Track onboarding time, repeated questions, and incident rediscovery time after rollout.

Pricing

Pricing

Use Insights & Memory within the same Kodus plans and usage model.

Team

For small teams.

$100/mo
  • 70M tokens / month
  • 2,500 iterations / month
  • Full routing + Review + Strategy
  • Bring your own local model
  • Teams (up to 2 members)
  • Priority support
  • Audit log access

Scale

For larger organizations.

$200/mo
  • 300M tokens / month
  • 7,500 iterations / month
  • Unlimited team members
  • All models + custom routing
  • Dedicated support channel
  • Early access to beta features
  • No annual contract
  • Tokens reset monthly
  • Switch plans anytime

Have invite code? Get Access Now