All posts
Joe Connolly private networking, microservices, security

Private networking between your apps

Your apps can now call each other at http://name.internal, straight across velixir's network. No public URL for internal APIs, on every plan.

Private networking between your apps

Split an app into a frontend and an API and, until today, the frontend called the API the way a stranger would: out to the public internet, through the edge, and back in again. That's slower than it needs to be, and every service you split off is one more public URL to protect.

Now every app on your team has a private address:


http://<app-slug>.internal

Calls go straight across velixir's network, app to app. It always points at the live release, so deploys, rollbacks and slot swaps don't change it. Your databases and caches were already on the same network; now your apps are too.

Who can reach my app's private address?

  • Your team's apps, on port 80 or the app's own port.
  • Not other teams. Every app's network policy admits its own team, the edge, and itself, and nothing else.
  • Not copies. A fork or Rewind preview runs with the original app's variables, so it's left off the private network on purpose: a copy can never call your live app.

How do I turn it on?

There's nothing to switch on. Find an app's private address on its Processes tab.

Private networking is on every plan, at no extra cost. The private networking docs cover the details.


Got an app to ship? velixir hosts it in any language, on servers in the EU.

Start free - your first month's on us