Investors

The system of record
for AI egress.

The opportunity

A blind spot that grew
as fast as AI coding did.

Developers adopted Claude Code, Cursor, and Copilot faster than security teams could get any view of what leaves with them. EDR, CASB, and DLP were built for a world before AI coding assistants — none of them read the prompt inside the TLS tunnel a coding agent opens to its model vendor. Tether does, on the tools that route through it, from inside the customer's own cloud.

Why now

Adoption outran visibility.

AI coding tools are already in production inside most engineering orgs. The controls that watch every other egress lane were never built to see this one.

Auditors have started asking.

SOC 2, HIPAA, and AI-governance reviews increasingly ask what controls AI-tool egress. Today the honest answer for most companies is "we have no record."

The old DLP doesn't fire.

A customer record paraphrased into a prompt never trips a regex pattern. The exfiltration surface moved, and pattern-matching stayed where it was.

The gap

Why the existing stack
can't close it.

  • EDR sees the process and the connection, not the prompt inside the tunnel.
  • CASB sees an approved SaaS host — a call to the model API looks like any other allowed destination.
  • DLP classifies files and known patterns, not paraphrased content generated on the fly.
  • Vendor logs live at the AI vendor, not in the customer's SIEM or on their audit timeline.

The full category-by-category map is on the How it works page.

The wedge

Start where the prompt
is still readable.

The developer's machine is the one place you can see a prompt before it disappears into an encrypted tunnel. Tether lands there first — and becomes the system of record for what leaves a company through AI tools.

Where the durability is

Trust you can check, not trust you're asked for.

Every decision is an Ed25519-signed bundle a customer's auditor verifies offline, with no access to us and no root certificate on any laptop. Fail-closed by design. That's the property regulated diligence looks for — and it's hard to retrofit.

Deployed inside the customer's cloud.

Tether runs in the customer's own GCP or AWS via Terraform. No Tether-side data lake, no data-processing liability, and a much shorter path through procurement. terraform destroy unwinds it cleanly.

Enforcement that's safe to turn on.

A three-tier judge — Tier 0 always blocks named patterns, Tier 1 is opt-in and fails closed, Tier 2 is advisory — lets teams enforce without breaking their developers. The moat is execution and integration depth, not a patent.

Expansion

From dev tools to
all AI egress.

Today: see and govern what developers send to AI coding tools (Claude Code, Cursor, Copilot). Next: broader AI egress beyond the IDE, prompt analytics, and compliance mapping to SOC 2, HIPAA, and PCI. Roadmap items are described as future work, not shipped capability.

Where we are

Early, and building
with design partners.

We're an early-stage company running design-partner pilots — free for up to 25 developers, two weeks, in the customer's own cloud. The Design Partner Program gives the first five paid partners per vertical 50% off for twelve months in exchange for a public case study and reference calls.

If you invest in security or developer infrastructure and want to talk, reach us at hello@tetherconnect.app, or see the pilot →