saas · config metadata only

Orchestration that never sees your packets.

The SaaS control plane (app.dev.telaron.io) handles configuration metadata and telemetry only — it physically cannot see customer packet content. It distributes intent to the edge tier, with per-tenant isolation enforced at the database. GitOps reconciliation is coming.

surface: app.dev.telaron.io
sees: Config metadata + telemetry
iac: Terraform · REST · Pulumicoming
isolation: PostgreSQL RLS

Config-driven, everywhere

A first-class Terraform provider and a full REST API for everything in between, with a Pulumi SDK (Go, TypeScript, Python) coming. No ClickOps traps, no console-only settings.

GitOps reconciliationcoming

Planned: the platform generates your policy as code and you apply it from your own repository, so the running fabric matches committed intent rather than the last manual tweak.

Data sovereignty by architecture

The control plane carries metadata and telemetry, never packet content. It is a property of how the system is built, not a clause in a policy document — and it is documentable for compliance.

Tenant isolation at the row

PostgreSQL row-level security isolates every tenant, enforced by a role that owns nothing. Access to your cloud federates via workload identity, with no service-account key stored anywhere.

the rest of the platform

Data planeeBPF-native packet processing in the kernel.GatewayThe edge that carries the fabric — in your VPCs, not your apps.

Start connecting your clouds today.

One secure fabric across every cloud — identity-aware policy, encrypted end to end, and no agents in your workloads. Start on the free Community tier; no sales call to get going.

Request access Book a demo

routing…