Fixed outbound IP

Send your backend's calls from fixed IP addresses, for banks, payment processors and partner APIs that only accept allowlisted IPs.

Some services only accept requests from IP addresses you registered with them in advance: banks and payment processors, government and partner APIs, vendors that restrict an API key to a list of IPs. A Floot backend is serverless, so its outbound address changes all the time. Fixed outbound IP gives your app a short, fixed list of IPv4 addresses to send those calls from.

When you need it

A service asks for your server IP, a static IP, or an IP allowlist (also called a whitelist) before it will give you access
Calls from your backend are refused with an IP error such as 403 IP not allowed or not whitelisted, while the same key works from somewhere else
You want to restrict one of your own API keys to known IPs, for example an IP-restricted Stripe restricted key on your own Stripe account

Turn it on

1
Open the setting
Open your project on floot.com, click the project name dropdown in the top-left, then Project Settings. Expand Advanced Settings, find Fixed outbound IP and click Turn on. Only the project owner can change it, and it needs a paid plan. Your assistant can't turn it on for you because it is billed, but it can send you a link that opens the setting.
2
Give the addresses to the service
Once it is on, the setting lists the addresses with a Copy button. Add all of them to the service's allowlist. Some are held in reserve, so the list doesn't have to change as Floot grows.
3
Ask your assistant to use it
Say which calls should go through it, and your assistant wires them up:
```
Send our calls to the bank's API through the fixed outbound IP.
```

How it works

Only the calls you choose: Your app decides, call by call, what leaves from the fixed addresses. Everything else your backend does (database, AI, email, other APIs) is unchanged.
Preview and published app: It works the same in both, so you can test against the service before you publish.
Encrypted end to end: The connection between your app and the service stays encrypted the whole way. Floot passes the traffic along and can't read it.
HTTPS only: It carries HTTPS calls to public addresses on port 443, which is what API allowlists are for. It can't be used for other protocols, such as a direct database connection.
Backend only: The calls are made from your app's endpoints, scheduled jobs and background tasks. Requests made by a visitor's browser come from the visitor's own IP.

The addresses are shared

Every Floot app that turns this on sends from the same addresses. An allowlist is one layer of protection: the service still identifies your app by its own API key or credentials, so keep those secret as usual. Dedicated addresses for a single app aren't available yet. Contact us if a service requires them.

Pricing

Fixed outbound IP is available on paid plans and costs $10 a month per project, billed from your hosting credits at $0.33 for each day it is on. That includes 5 GB of traffic through the fixed addresses per month; beyond that it is $0.15 per GB. It appears as its own line on your hosting usage page.

Turn it off at any time and billing stops after that day. Routing only the calls that need it keeps you well inside the included traffic.

When it pauses

Calls through the fixed addresses are refused, and the feature isn't billed, while:

The setting is off. Services that allowlist the addresses stop working for your app until you turn it back on.
The owner's plan is no longer a paid plan. It resumes when the plan is renewed.
The hosting balance is overdue. It resumes once the balance is paid.

The setting shows Paused with the reason in the last two cases. Changes take effect within about a minute. The rest of your app keeps running either way; only the calls routed through the fixed addresses fail.