JamJet Cloud

Your agents
have a team now.

Two lines drop in next to your existing agent. No rewrite, no sidecar.

agent.py
import jamjet.cloud as jamjet

jamjet.configure(api_key="jj_xxxx", project="my-agent")
# every OpenAI / Anthropic call is now on the tape

The call shows up in the dashboard in seconds. Free for you, forever.

app.jamjet.dev · home
JamJet Cloud dashboard home: a production-readiness ring at 90, an attention queue of held approval requests, and a row of recent allow and hold decisions.

You approved a held merge on the Gate yourself. This is where your team does it.

Act I · Observe

The team sees.

Traces, signals, and costs from every run land in one place your whole team can open. Token usage by the minute, the model and tool calls behind each trace, and the spend trend rolling up across agents and environments.

app.jamjet.dev · signals
JamJet Cloud signals view: a live token-usage area chart with input and output bands, totals for input, output, and cache tokens, and a live events feed below.

The morning the token bill jumps, this chart is how you find out, and the budget cap is how it never ships an invoice.

Seeing your own runs is free, forever.

Act II · Enforce

The team decides.

Held actions land in a queue your teammates work, each with an SLA timer counting down. Approve or reject in one click, with a reason that lands in the audit log. Budgets sit alongside, ready to halt a run before it spends past the cap.

app.jamjet.dev · approvals
JamJet Cloud approvals queue: three held actions, a bulk email, a payment refund, and a github merge, each with an SLA-in-59-minutes chip, the requesting agent and reason, and Approve and Reject buttons.

A queue is only a queue when it is shared. The held merge you approved on the Gate becomes a line your reviewers see, with a timer and a name attached.

A shared queue is where the team turn starts. That is the Team plan.

Act III · Prove

The team proves.

Every decision is retained and sealed into a receipt. Export a window as a signed PDF, check production readiness, and hand compliance evidence instead of a story.

Compliance asks for March. You export a sealed PDF, not a Slack archaeology dig.

Retention and export are what an audit actually asks for. That is Business.

The split

Everything local stays free.

The runtime, the policy engine, Engram, and the Gate are Apache 2.0 forever. Cloud is the team surface on top. That split is the business model, in the open.

Capability
OSS runtime
JamJet Cloud
Local execution & durability
Yes
Yes
Policy engine
Yes
Yes
Audit log (local)
Yes
Yes
Engram memory
Self-hosted
Hosted
Trace dashboard
Local web companion
Team-wide
Approval queue across reviewers
API only
Hosted UI + SLA
Retention & audit export
Manual
Built-in
SSO / RBAC / projects
Team / Enterprise
Cross-agent trace propagation
Manual
W3C traceparent
Pricing

You pay for the team surface.

Solo is free, forever. The paid tiers are where more than one person is involved: higher trace volumes and longer retention.

Free
$0 forever

For you. Connect an agent, watch your runs, solo everything.

  • 5K traces / month
  • Traces, signals, and costs
  • Policies and audit log
  • 7-day retention
  • Hosted Engram memory
Connect an agent free
Starter
$29/mo

For the first run that outgrows solo.

  • 50K traces / month
  • 30-day retention
  • Everything in Free
Start on Starter
the audit turn
Business
$499/mo

When someone outside the team asks for proof.

  • 1M traces / month
  • 180-day retention
  • Audit export
  • SSO when available
Go Business

Regulated team, self-hosted control plane, or a volume that breaks these brackets? Talk to us.

Send your first trace.
Bring the team to it later.

Two lines next to your agent and the dashboard fills in. Free for you, forever. The paid line shows up the day someone else needs to see, decide, or prove.