Skip to main content

Kam State · for Amazon Bedrock AgentCore

Build more. Manage less state.

Shared State, exact History, version checks, and recovery, without building them yourself.

Explore the productDiscuss an evaluation

Prelaunch. No hosted service yet.

The call dropped. The record didn’t.

Give the next agent a saved version, not a chat to piece together.

  1. Phone call

    “Yep. I updated it.”

  2. Hang-up

    “Click.”

  3. Confused worker

    “Updated WHAT?!”

  4. Kam record

The connection carries the chat. The record carries the handoff.

Saved reports, not proof of completed actions. Earlier versions need retention and access.

Loading the example.

Industry perspectives

Why AI needs more than a model.

Industry reading—not endorsements of Kam AI.

See where Kam fits

What Kam does today

  • Exact

    Read the requested version, or a clear no.

  • Kept

    Fixes add versions. Nothing is overwritten.

  • Checked

    Access checked on each read. Browser input grants no access.

  • Capped

    Each read has a fixed work limit.

Built into the code. Speed is measured after live testing.

One agent turn
Explore product layers

Before Kam, and after

See the causes and costs

Shared results go missing or drift.

Root problem: cause → costWith Kam: the whole class removed

Copies drift.

Each agent keeps a copy.Agents get different versions.

  • Stale reads
  • Silent overwrites
  • Double counting

Ask for an exact version. Fixes add versions. Retries count once.

Inputs go missing.

Inputs change or vanish.No record of the read.

  • Mystery inputs
  • Lost evidence
  • Unrecorded sources

Recorded sources are kept. Your app names its inputs; Kam keeps them while retained.

Work gets redone.

Changes are hard to trace.Work repeats after a crash.

  • Full rebuilds
  • Repeat calls
  • Restarted jobs

Only affected State updates. Kam resumes its own work. Agent task recovery is planned.

Three ways to share results between agents

Compare approaches

  1. 1

    Re-read every source, every turn

    Easy to start.

    • Exact version on request: no
    • A fix keeps the old version: no
    • A retry counts once: no
    • Only affected results update: no
    • Access checked on every read: you build it
    • Built for AgentCore: no

  2. 2

    Your database plus custom code

    You build it.

    • Exact version on request: you build it
    • A fix keeps the old version: you build it
    • A retry counts once: you build it
    • Only affected results update: you build it
    • Access checked on every read: you build it
    • Built for AgentCore: you build it

  3. 3

    Kam

    In code. Not hosted.

    • Exact version on request: built in
    • A fix keeps the old version: built in
    • A retry counts once: built in
    • Only affected results update: built in
    • Access checked on every read: built in
    • Built for AgentCore: built in

means you build and maintain it yourself. Categories, not named products.

Start from your role
Implemented in source

AgentCore developer

Stop rebuilding State plumbing around your agents.

Explore history →Implemented in source

Multi-agent team

One versioned record any agent can read, with access checked.

Explore access →Implemented in source

AI infrastructure engineer

An old worker can’t overwrite a newer result.

Explore recovery →Planned · not available

Enterprise architect

Know exactly what changed, and what each step read.

Explore context →Planned · not available

Long-running workflow builder

Keep the work when a worker stops.

Explore memory →Planned · not available

AI platform team

Reuse finished work instead of computing it again.

Explore efficiency →
Start with Core. Grow into managed workflows.

  1. 01

    Kam Core

    Implemented in source · prelaunch

    Explore this layer

    Record, retry safely, correct, and read exact History and bounded State. SDK distribution and hosted access are not generally available.

  2. 02

    Managed State & Context

    In development · not hosted

    Explore this layer

    Prepare versioned evidence for the next agent, track dependencies, and reconcile stale results with explicit authority.

  3. 03

    Managed Workflows

    Product direction · not available

    Explore this layer

    Configure approved parent-child jobs, execution windows, adapters, and recovery rules. Kam determines eligible work from accepted State; execution can remain on AWS or customer infrastructure.

Follow a result from start to correction.

Try a software release or a fictional NFL game. Inspect versions and dependencies yourself.

Explore the NFL exampleExplore a release

For AgentCore builders

Use exact State and History without building version tracking.

See the code

Prelaunch

Implemented in source. Hosted access is unavailable. AWS Marketplace is planned.

Review the evidence
Built to add on to AWS

Amazon Bedrock AgentCore

AWS runs the agent. Kam adds State and History.

Your databases

Keep your databases.

One project. A clear test.

Try Kam on one real project.

Tell us what your agents do and what keeps going wrong. We set what success looks like first.

Discuss an evaluationSee evaluation scopeNot launched yet. No production promise.