TonD is closer to Boundary than to Teleport: both provide controlled, protocol-agnostic network access to private targets through a control plane and relay or worker data plane. The difference is mainly maturity and architecture.
| Area | TonD | HashiCorp Boundary |
|---|---|---|
| Primary purpose | Direct or relayed TCP access to remote endpoints | Identity-aware secure remote access broker |
| Data path | P2P first; central or customer SSH relay fallback | Worker-proxied sessions, including ingress/egress and multi-hop workers |
| Control plane | Python WebSocket server with in-memory registry | HA stateless controllers backed by PostgreSQL |
| Target registration | Remote client advertises allowed protocols and ports | Managed targets, host catalogs, target configuration, and worker tags |
| Identity | Organization/device registration and Ed25519 proof | Users, groups, OIDC and other auth methods, roles, and grants |
| Authorization | Organization boundary plus remote-advertised protocol/port | Fine-grained RBAC policies over scopes, targets, sessions, and workers |
| Credentials | User's normal protocol credentials remain separate | Can broker/inject credentials, often integrated with Vault |
| Reliability | Single server registry; customer relay fallback | HA controllers, persistent database, worker health, and routing |
| Recording/audit | Audit design exists; no durable implementation yet | Durable audit events and optional SSH session recording |
| Connectivity advantage | Can avoid relays entirely with encrypted P2P | Predictable, managed routing across complex networks |
Key distinction: TonD is an encrypted connectivity layer: it creates a local port that normal SSH, RDP, or HTTP clients use. Boundary is an access-management product: it decides who may access which target, selects a worker route, can manage credentials, and records the authorized session.
TonD's customer SSH node is conceptually nearest to a Boundary worker, but it is a fallback relay only. A Boundary worker is the normal data-plane component and supports deliberate placement, tags, multi-hop routing, health management, and scalable scheduling.
To move TonD toward Boundary, prioritize persistent organization, target, and session state; user/role RBAC; OIDC; target inventory; durable audit events; relay health/capacity scheduling; and eventually Vault-backed credential brokering.