kubbiai

When to use kubbi

kubbi pays off in cross-trust-boundary handoffs and sensitive payload traffic. It isn't the right tool for all-internal pipelines, low-volume non-sensitive data, or permanent storage.

When kubbi is the right fit

Cross-organizational agent traffic. Your MCP server returns a claim URL. Another vendor's agent claims the payload. Neither of you exposes a bucket. The trust boundary between organizations is exactly where claim-check defaults pay off.

Cross-trust-boundary handoffs within one organization. An on-premise extraction step hands data to a cloud analytics agent. A CI pipeline hands artifacts to an air-gapped build runner. The two sides shouldn't share storage credentials.

Sensitive payloads on existing async channels. You're using a queue, a webhook, or an A2A bus, and the payload contains credentials, PII, or tool outputs you don't want sitting inline in logs.

Multi-file bundles tied to a single claim. Config, data, instructions, and attachments that should be delivered together with one URL.

Teams that don't want to build claim-check plumbing. Server-side burn enforcement, expiry, multi-file bundling, audit, and a manifest preview API are real work to roll yourself.

When kubbi isn't the right fit

All-internal AWS with S3 + IAM dialed in. If your producer and consumer share a trust boundary and you have presigned URLs and per-object expiry working, the marginal value of kubbi is small. Use S3.

Low-volume, non-sensitive payloads. If your data is fine sitting inline in the queue or webhook, the overhead of two systems isn't worth it.

Permanent storage. kubbi is for handoffs. Payloads are temporary by design. Use a real object store for archival or long-term reference.

Synchronous request/response. If the producer can wait for the consumer to fetch the payload directly, you may not need a side-channel at all.

Decision rule of thumb

Pair kubbi with whatever async channel you already have when both conditions hold:

  1. The trust boundary between producer and consumer is real.
  2. The payload is something you don't want sitting inline in the primary channel.

For the technical comparison to alternatives, see kubbi vs. the alternatives.