Kraterion
v 0.1 · testnet

A runtime for agents
you can debug.

Built on object storage you own. Every run is recorded as a replayable, tamper-evident trail — so you can reproduce it, audit it, and prove what happened.

Replay & auditVerifiable runsS3 storage
Stored onWalrus
Secured bySeal
Owned onSui
01 · Storagesupport-docs · 4 files · 1.7 MB
  • pricing-faq.md
    12 KBIndexed
  • product-overview.pdf
    482 KBIndexed
  • release-notes-2026-05.md
    8 KBIndexed
  • onboarding-guide.pdf
    1.2 MBSealed
indexed · hybrid retrieval
02 · Knowledge48 chunks · 1024 dims
BM25 + dense vectorstop-k = 8 · hybrid
queried · /v1/agents/support
03 · Runagent · support184 ms
Q

What is our refund policy?

A

Refunds are processed within 7 business days from the original payment method.

pricing-faq.md · §3score · 0.92verified
run · 3f4d…aerecorded · replayable
00The problem

What breaks when you ship an agent.

Agents are non-deterministic. When one goes wrong in production, you need to see what it did, reproduce the run, and prove it — and most tools can't give you that.

01Today

Agents are black boxes.

Your agent retrieves files, calls tools, and writes to memory. When the answer is wrong, you can't see which step caused it. Debugging is guesswork.

02Today

Runs don't reproduce.

The same input gives a different output every time. Once a run ends, the trace is gone — you can't replay the bug, and you can't prove how a past decision was made.

03Today

Your logs aren't yours.

Tracing tools keep their records in their database — mutable, sampled, and on their retention clock. You can't verify them independently, and you can't take them with you.

Bridge

Run your agent.
Keep the receipts.

01The foundation

Storage you own.
The runtime sits on top.

Every file, knowledge base, run record, and memory lives in storage you own — S3-compatible, so boto3, aws-cli, and rclone work unchanged. Bring your data in, and the runtime records itself right beside it.

Request lifecycle · S3 PUT objectSigV4 · HTTPS · multipart
01YOUR SIDE02KRATERION GATEWAY03STORAGE SPINES3 clientSigV4boto3 · aws-cli · rclone · JS SDKendpoint_url = "s3.kraterion.com"s3.put_object(Bucket="assets-prod",Key="photo.jpg",Body=fp,)GatewayS3-compatible · NestJS + FastifySigV4 authMultipartStreams11 ops · 0 rewrites · TLS 1.3ENCRYPTIONSealed on your device.Envelope encryption · keys split across independent serversSTORAGECiphertext only, at rest.Erasure-coded across nodes · plain HTTPS readIDENTITY & AUDITYou own the object.Revocation stops decryption · digests are verifiablePUT objectSigV4 · TLS 1.3
STORAGE

Files stay yours.

Cancel anytime — your bytes don't move. Any S3 client can pull them.

ENCRYPTION

Keys stay yours.

Revoke and decryption stops. Enforced by structure, not policy.

IDENTITY & AUDIT

Every artifact has a receipt.

Tamper-evident manifest digests you can verify against the chain.

S3 compatibility

It speaks S3 — really.

  • Point your boto3 client at us.
  • rclone, aws-cli, and the AWS SDKs all work today.
  • Presigned URLs, public-read buckets, always-on AES256 at rest.

Tap a tab to switch SDK.

import boto3

s3 = boto3.client(
    "s3",
    endpoint_url="https://s3.kraterion.com",
    aws_access_key_id="...",
    aws_secret_access_key="...",
)
s3.upload_file("photo.jpg", "my-bucket", "photo.jpg")
02Knowledge

Retrieval you can check.

Flip one toggle and your files become a knowledge base. Hybrid retrieval — BM25 plus dense vectors, top-k 8. Every answer carries a citation you can verify against the exact source it came from.

01Bucket
4 files · 1.7 MB
Bucket
Your S3 keys.
  • pricing-faq.md12 KB
  • product-overview.pdf482 KB
  • release-notes-2026-05.md8 KB
  • onboarding-guide.pdf1.2 MB
02Indexed knowledge
48 chunks · 1024 dims
Indexed knowledge
BM25 + dense vectors.
  • top-k8 · hybrid
  • encodertext-embedding-3-small
03Answer + citation
0.92 · verified
Answer + citation
Reranked, citation-bound.
answer

Refunds are processed within 7 business days from the original payment method.

pricing-faq.md · §30.92
stage 01 / 03
03The runtime

Wrap your agent.
Replay any run.

Wrap a LangGraph or Vercel AI SDK agent with one import — or point your OpenAI client at us. From then on, every retrieval, tool call, and memory write is recorded automatically, with nothing else to wire up.

from langgraph.graph import StateGraph
from kraterion.langgraph import WalrusCheckpointSaver

# Point your existing graph's checkpointer at Kraterion.
# Every run records itself — replayable, auditable, yours.
graph = builder.compile(
    checkpointer=WalrusCheckpointSaver(project="support"),
)

result = graph.invoke({"question": "What is our refund policy?"})
# run recorded · receipt 3f4d…ae · replay with: kraterion replay 3f4d…ae
Agent · supportkr_share_test_3f4d…
scoped · support-docs
USER

What is our refund policy?

TOOL CALLS · 3 of 6 available
  • recallquery: "user prefs"2 notes29 ms
  • searchquery: "refund policy"4 hits62 ms
  • readkey: "pricing-faq.md"12 KB38 ms
ASSISTANT

Refunds are processed within 7 business days from the original payment method.

pricing-faq.md · §3score · 0.92verified
run · 3f4d…aereplayable
Total latency213 ms
Tools called3 of 6
Recordrecorded
03bNative MCP

Also reachable
from your AI assistant.

Plug Kraterion into Claude Desktop, Cursor, or any MCP-compatible client. Your knowledge, your tools, and persistent memory — over a different protocol, with the same scoped credentials.

claude_desktop_config.jsonPaste this in
{
  "mcpServers": {
    "kraterion": {
      "url": "https://mcp.kraterion.com/mcp",
      "auth": {
        "type": "oauth",
        "dcr": true
      }
    }
  }
}
OAuth 2.1 · Dynamic Client Registrationauto-register
Works withmcp.kraterion.com
  • Claude DesktopFirst-party MCP host
  • CursorEditor MCP support
  • ZedEditor MCP support
  • ContinueIDE assistant
  • Any MCP clientImplements the spec
Tools7 · same
Scopeper-agent
AuthOAuth 2.1
04Why this matters

Your data.
Your logs.
Your exit.

Observability tools hold your traces in their database — mutable, sampled, on their retention clock. Kraterion keeps every file and every run record in storage you own. Encrypted by default, verifiable by anyone, and yours to take with you.

Typical S301 · before

They hold the keys.

provider.s3·/iam/access-keys
Access keys · provider-managed3 active
  • AKIA7C4D8E1C…3Fread-onlyactive
  • AKIA92AC6712…A1read-writeactive
  • AKIA1A8B4C5D…99adminactive
Revoke via support ticketdisabled

Manual process · SLA 2-5 business days

  • Keys live inside the provider boundary.
  • Revoke is a support ticket, not a property.
  • Exit means copying everything out — at $0.09/GB egress.
Kraterion02 · after

You hold the keys.

app.kraterion.com·/keys
Your keys · scoped per agentyou hold
  • kr_test_3f4d8e1c…a2read-onlyactive · revoke
  • kr_test_92ac6712b1…7cread-writeactive · revoke
  • kr_share_test_1a8b4c…99agentactive · revoke
Revoke per agent · enforcedone click

Keys stop being issued immediately — by structure, not policy.

  • Keys live with you. Plaintext never crosses the wire.
  • Revoke is a policy property — enforced, not promised.
  • Exit through any S3 client — at ~9× lower egress than AWS.

What that gets you

You own your data and your logs.

Pull raw bytes and full run records over plain HTTPS, from any region. No proprietary export, no vendor-held traces.

Sealed before it leaves you.

Encryption is the default, not a setting. The platform stores only ciphertext — files, run records, and memory alike.

Tamper-evident by structure.

Every run is recorded so it can't be altered after the fact. You don't take our word for it — you verify it independently.

Revocable access — enforced, not promised.

Remove access and reads stop — files and memory together. Not a policy. A property.

06Compliance

Built for the rules AI is facing.

AI regulation keeps asking the same things — show what your AI did, keep the record, control the data. The way Kraterion is built answers all three.

EU AI Act · ISO 42001

Durable audit logs

Every run is a tamper-evident record you keep as long as you need.

GDPR

Data control & erasure

Encrypted by default and revocable — lock data out or erase by destroying the key.

NIST AI RMF

Traceability

Replay any run and trace every output back to its sources.

07Quickstart

Five lines to a replayable agent.

Wrap an agent you already have. Run it, and Kraterion records the run. Replay it from its receipt — same inputs, same retrieval.

terminal
$  
08Pricing

Pay for what you use.

Storage, retrieval, and run records on the same meter — generous free band on each, flat per-unit rate above it, no minimums or tier cliffs. Bring your own model keys; we don't mark up tokens.

Estimate · per project, per monthlive · USD
Project shape
Knowledge layerIndex files for hybrid search + agent retrieval
  • Storage$2.9750 GB
  • Reads$1.605M ops
  • Writes$0.0510k ops
  • Egress$1.50200 GB
  • Knowledge index$0.9010 GB-day
  • Agent messagesfree$020k msg
Estimated monthly billBased on industry averages for this project shape.Private beta— rates informational, not final
$7.02
See full pricing
Now on testnet

Ship agents you can
debug, reproduce, and trust.

No card. Free band on every meter. Wrap an agent you already have.

v 0.1 · testnetAll systems normal