Cowrie Research

terminal-3-company-primary-sources-2026-08-12

4 min read

Terminal 3 company primary sources — 2026-08-12

Classification takeaway

Terminal 3 now clears the bar for a separate companies/ note because the useful control question is not only what is T3N? It is which named operator packages T3 Network, T3 Identity, T3 Verify, the ADK, identity accounts, relying-organization access, and the legal/privacy shell into one governed service boundary? The strongest answer in current primary materials is Terminal 3 HK Limited.

Primary sources reviewed

  1. Official homepage — https://terminal3.io/

    • Best concise statement of the current company framing.
    • Leads with secure workloads, credentials, and computation for AI agents, and presents Agent Command, T3 Network, and human-identity tooling as one bundled trust platform.

  2. About page — https://terminal3.io/about

    • Best source for explicit entity framing.
    • Calls Terminal 3 a deep-tech company and says it powers identity and trust infrastructure across enterprises, governments, and Web3 platforms.

  3. Platform overview docs — https://docs.terminal3.io/intro/platform.md

    • Best source for product-family packaging.
    • Says T3 Network sits underneath Terminal 3’s products, including T3 Identity, T3 Verify, the ADK, and Agent Command.

  4. T3N overview docs — https://docs.terminal3.io/t3n/overview/what-is-t3n.md

    • Best source for the technical network framing.
    • Describes T3N as a confidential-computing network with node operators, compliance authorities, and credential issuers/verifiers, but still reached through one company-run developer/docs shell.

  5. Docs index (llms.txt) — https://docs.terminal3.io/llms.txt

    • Best source for the breadth of the operator-managed adoption surface.
    • Shows one company-run documentation corpus spanning T3N, ADK quickstarts, public and organization-owned agent registration, API-key flows, support channels, and OpenAPI specs.

  6. Privacy policy — https://terminal3.io/privacy-policy

    • Strongest source for the legal entity and data-boundary framing.
    • Identifies Terminal 3 HK Limited as the entity handling data across websites, web/mobile apps, SDKs, APIs, and related services.

  7. Terms of service — https://terminal3.io/terms-of-service

    • Best source for service-boundary and operator-discretion framing.
    • Says the binding agreement is with Terminal 3 HK Limited and covers websites, applications, SDKs, APIs, and related services, while reserving the right to change, suspend, or discontinue services.

Selected excerpts

Homepage

Unleash the full power of AI agents through secure workloads, credentials, and computation

Terminal 3 secures your most sensitive data and systems ... Agent Command is a single trust plane for your entire AI agent workforce

About

Terminal 3 is a deep-tech company solving the world's most pressing data privacy and security problems.

Terminal 3 powers identity and trust infrastructure across enterprises, governments, and Web3 platforms worldwide.

Platform overview

Built on top of T3N are Terminal 3's products ... T3 Identity, T3 Verify, T3 Agent Developer Kit (ADK), T3 Agent Command (coming soon)

T3N overview

T3 Network (T3N) is a confidential computing network ... no single party (including node operators) can read or alter it.

The participants in the T3N ecosystem include ... node operators ... compliance authorities ... VC issuers ... VC verifiers.

Privacy policy

This Privacy Policy ... describes how Terminal 3 HK Limited ... collects, uses, discloses, and protects personal data across our websites, applications (web and mobile), software development kits, application programming interfaces, and related services

Terms

These Terms of Service ... are a legally binding agreement ... with Terminal 3 HK Limited

We may change, modify, suspend, or discontinue all or part of the Services at any time.

Why it belongs in the active corpus

  • Useful company-boundary example for confidential-computing and verifiable-credential stacks that market protocol properties while still concentrating developer access, account models, product packaging, and legal control inside one company shell.
  • Helps separate lower-layer mechanism questions from operator questions: DID/VC standards and TEE architecture are not the same thing as the company deciding how the live stack is packaged, exposed, and governed.
  • Good taxonomy cleanup because the old projects/terminal-3 note was really an entity note with multiple products underneath it rather than a clean deployed protocol surface.

Graph View