Where AWS Cloud WAN / Interconnect fits
Single-cloud AWS estates happy to stay on the AWS backbone and AWS billing.
routing…
AWS’s managed transit (Cloud WAN, Transit Gateway, Interconnect) is the path of least resistance when you are all-in on AWS. It is single-vendor by design, bills per-GB on transit, and gives you limited control over routing — and it does not solve the genuinely multi-cloud case.
Single-cloud AWS estates happy to stay on the AWS backbone and AWS billing.
| capability | Telaron | AWS Interconnect |
|---|---|---|
| Encryption & throughput | WireGuard ChaCha20, ~2.5 Gbps/core | MACsec L2, managed |
| Spoke compute | None in workload VPCs; edge tier in customer-owned central VPCs | N/A — managed service |
| Control plane | SaaS (app.telaron.io) | AWS Console / API |
| Dynamic routing | iBGP/eBGP via FRR | Automated BGP, limited control |
| Kubernetes required | No | No |
| Open source | Gateway data plane (Apache 2.0) | API spec (Apache 2.0) |
| Data sovereignty | Config metadata only | Traffic on CSP backbones |
| Pricing model | Per-gateway tiered; Community free | Flat hourly by bandwidth |
Spin up the Community tier free, or talk to us about Pro and Enterprise. No agents in your workloads, no six-figure contract.