# Secure internal communication between services

Source: [Vercel](https://vercel.com/changelog/secure-internal-communication-between-services)  
Feed7 permalink: https://feed7.dev/p/secure-internal-communication-between-services-1usj7m4  
Published: Unknown  
Trust: Official Source (official_source)

## Why Included

Vercel Service Bindings let one service in a deployment call another via an injected env var URL, with internal routing, auth, and TLS handled — e.g. a Next.js frontend reaching a FastAPI backend privately.

## Source Summary

**The gist** Vercel shipped **Service Bindings**: a service declares a binding to another service in the same deployment, Vercel injects an **environment variable** holding an internal URL, and a plain HTTPS fetch works — **routing, auth, and TLS** are handled internally, off the public route table.

## Practical Implication

**Why it matters** Multi-service apps on one deployment get practical: a **Next.js frontend** can call a **FastAPI backend** without exposing it publicly or managing certificates, and each call shows in **observability** with the target service and duration.

## Agent-Ready Context

**The gist** Vercel shipped **Service Bindings**: a service declares a binding to another service in the same deployment, Vercel injects an **environment variable** holding an internal URL, and a plain HTTPS fetch works — **routing, auth, and TLS** are handled internally, off the public route table.

**Why it matters** Multi-service apps on one deployment get practical: a **Next.js frontend** can call a **FastAPI backend** without exposing it publicly or managing certificates, and each call shows in **observability** with the target service and duration.

**Watch out** Billing is its own lane — bound calls count as **Service Requests** and **Fast Origin Transfer**, not CDN Requests — so check current rates before routing chatty internal traffic; a service stays unreachable unless exposed via a **rewrite or a binding**.

## Context Map

- Layer: infra
- Domains: None
- Topics: None

## Uncertainty

- Billing is its own lane — bound calls count as **Service Requests** and **Fast Origin Transfer**, not CDN Requests — so check current rates before routing chatty internal traffic; a service stays unreachable unless exposed via a **rewrite or a binding**.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.