COMING SOON Tack Cloud is in active development. tack-guard ships first; Cloud upgrades it with one line. Follow along.

TACK CLOUD

The memory your guard loses on every restart.

Tack Cloud is the paid tier of Tack — runtime risk scoring for AI agent tool calls. tack-guard scores every tool call locally, in under 1ms; Tack Cloud gives it a baseline that survives restarts and correlates behavior across sessions and across agents, catching the attacks a single, in-memory session structurally cannot see.

Last updated June 17, 2026

ONE LINE

Same guard. One new line.

You do not re-architect anything. Keep your existing tack-guard setup and add guard.connect(). The scoring still runs locally; events sync to Tack Cloud after the verdict, so baselines now persist and correlate. The API is already final, so this is a no-redesign upgrade.

  • Scoring stays local, under 1ms
  • Events sync async, after the verdict
  • Graceful degradation if Cloud is down
agent.ts
import { createGuard } from '@tacksec/guard'

const guard = createGuard()
guard.connect('tk_live_xxx')   // the only new line

// Everything else is identical. Scoring still runs
// locally, in under 1ms. Baselines now survive restarts
// and correlate across sessions and across agents.
const result = guard.evaluate({
  action: 'write',
  target: 'user_db.credentials',
})

WHAT CLOUD ADDS

The detections a local guard cannot do.

tack-guard is single-session by design: fast, private, zero dependencies. Tack Cloud adds exactly the three things that need memory across processes and across agents.

01

Persistent baselines

Your agent's per-agent baseline is written to Tack Cloud, not held in process memory. Restart, redeploy, or scale to ten replicas and the baseline is still there. No cold start, no relearning window where attacks slip through unscored.

02

Cross-session detection

A patient attack escalates privileges over hours or days, one quiet step per run. A fresh process forgets the earlier steps; Tack Cloud remembers them. Detection windows span 24h, 72h, and 7d, so slow credential-creep is scored against the whole history, not one session.

03 persistent baselines

Cross-agent baselines

An agent's ID is set by the caller, so an attacker can spread malicious steps across many agent IDs to stay under any single session's radar. Tack Cloud makes your account the trust boundary and correlates behavior across every agent ID, so splitting the attack no longer hides it. This is the one detection a local, in-memory guard cannot do.

HOW IT FITS

Cloud never touches the hot path.

The verdict is computed locally and returned before anything is sent anywhere. Tack Cloud receives events after the fact, so it adds memory without adding latency, and an outage cannot block your agent.

Scoring Local, inline, under 1ms Stays local. Cloud is never in the hot path.
State In memory, lost on restart Persisted server-side, reloaded on connect()
Detection window Single session Cross-session and cross-agent (24h / 72h / 7d)
Data Nothing leaves the process Events sent async, after the verdict (fire-and-forget)
If Cloud is down n/a Guard falls back to single-session. The agent never blocks.

ON THE ROADMAP

Visibility comes after persistence.

Persistent, cross-agent baselines ship first because they are the part nothing else can give you. A dashboard, alerts, and an LLM analyst follow, driven by what early users actually ask for.

  • Dashboard & timeline

    Later

    See every agent, its threat score over time, and the events behind a quarantine.

  • Alerts

    Later

    Push a detection to email, a webhook, or Slack the moment an agent drifts.

  • Analyst

    Later

    LLM-assisted forensics that explains a correlated incident in plain language, not just a score.

PRICING

Free guard, forever. Paid memory on top.

tack-guard stays free and MIT licensed, with zero runtime dependencies, for as long as it exists. Tack Cloud is a simple paid tier layered on top for teams that need baselines to persist and correlate. Final pricing lands at launch.

Follow for launch Read the guard docs Tack Cloud lands after tack-guard.

FAQ

Tack Cloud, answered.

What is Tack Cloud?
Tack Cloud is the paid tier of Tack — runtime risk scoring for AI agent tool calls. The free tack-guard SDK scores every tool call locally; Tack Cloud adds a hosted memory that persists each agent's baseline and correlates behavior across sessions and across agents.
What does Tack Cloud add to tack-guard?
Persistence and correlation. tack-guard is single-session and in-memory: restart the process and the baseline is gone. Tack Cloud keeps baselines across restarts, scores slow attacks over 24h to 7d, and ties activity together across agent IDs so an attacker cannot split the work to stay under the radar.
Does Tack Cloud slow down my agent?
No. The scoring stays local and synchronous, under 1ms, exactly as in the free guard. Events are sent to Tack Cloud asynchronously after the verdict is returned, so the cloud round trip is never on the agent's critical path.
What happens if Tack Cloud is unavailable?
The guard keeps working. If the cloud is unreachable it degrades gracefully to single-session, in-memory scoring, which is the free behavior. A cloud outage can never block a customer's agent.
Is my data sent to the cloud?
Only if you call guard.connect(). The free guard sends nothing and runs fully offline. With Cloud connected, tool-call events (action, target, agent ID, timestamp) are sent after the verdict so baselines can persist. Scoring still happens locally.
How will it upgrade from the free guard?
One line. You add guard.connect('tk_live_xxx') to an existing tack-guard setup and everything else stays identical. The API surface is already final, so the upgrade is a no-redesign change.
When is Tack Cloud available, and what will it cost?
It is in development. tack-guard ships free first; Tack Cloud follows. tack-guard stays free and MIT licensed forever; Tack Cloud will be a simple paid tier on top, with final pricing announced at launch. Follow along on LinkedIn for the date.