Home
Contact salesLog in
Release notes

Network Bindings Now Available for Telnyx Edge Compute Functions

15, Oct 2026

Network Bindings Now Available for Telnyx Edge Compute Functions

Telnyx Edge Compute Functions can now call services on your private Telnyx WireGuard network. A network binding connects an Edge Compute Function to an existing Telnyx WireGuard Interface. The function can then use env.<NAME>.fetch() to send HTTP requests through the tunnel.

What's new

  • Network binding: Declare a [network.<name>] binding in func.toml or telnyx.toml, using the WireGuard Interface UUID, not the parent Network UUID.
  • Function as a peer: Deployment automatically registers the function as a WireGuard peer named func-<function-id>.
  • Requests over the tunnel: env.<NAME>.fetch() accepts a URL string, URL, or Request, and sends HTTP requests through the configured network binding.
  • Requirements: telnyx-edge v0.5.10 or later, @telnyx/edge-runtime v0.16.0 or later, a Network with a WireGuard Interface in provisioned status, and a host connected as a WireGuard peer, running the target HTTP service.

Why it matters

Network bindings let Edge Compute Functions call private HTTP services over an existing Telnyx WireGuard tunnel, without exposing those services to the public internet.

Example use cases

  • Internal APIs: Call an HTTP service on your own host from a function, without exposing a public endpoint.
  • Private backend services: Access internal HTTP APIs reachable through a configured WireGuard peer.

Getting started

  1. Follow the WireGuard Interfaces Quick Start to create a Network, create a WireGuard Interface, wait for provisioned status, register the target host as a peer, and bring the tunnel up.
  2. Declare the binding in func.toml or telnyx.toml and regenerate declarations with telnyx-edge types:
[network.PRIVATE_NET]
id = "<wireguard-interface-uuid>"
  1. Call the service with the host's WireGuard address. The address and port in the example are illustrative. Use the actual address and port of your private HTTP service:
import { env } from "@telnyx/edge-runtime";

const response = await env.PRIVATE_NET.fetch("http://172.27.0.2:8787/health");
  1. Deploy with telnyx-edge ship, invoke the function, and confirm the private HTTP service responds successfully.

The network binding docs cover the manifest fields, the fetch options, and the full verification flow.