Static outbound/egress IP for external database allowlisting

[brunohaasds]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the FastAPI Cloud documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI Cloud" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to FastAPI Cloud but to FastAPI.

Example Code

The issue is not the FastAPI application itself. The issue is that the external database firewall requires us to allowlist the public outbound IP used by the FastAPI Cloud deployment.

So we need to know whether FastAPI Cloud can provide a stable outbound/egress IP, or fixed IP range, for database connections.

Description

Hi! Does FastAPI Cloud provide a static outbound/egress IP address for deployed apps?

We need our FastAPI app to connect to an external SQL database that only allows connections from whitelisted IP addresses.

Can we get a stable public outbound IP, or a fixed IP range, used by the app when connecting to external databases over TCP?

Also, is this IP stable across deploys, restarts, scaling events, and multiple replicas?

This is important because the database firewall requires IP allowlisting.

Operating System

Linux

Operating System Details

No response

FastAPI Version

0.115.6

Pydantic Version

2.13.4

FastAPI CLI Version

2.7.1

Python Version

3.12

Additional Context

No response

[YuriiMotov]

Hello!

At the moment, FastAPI Cloud does not provide static outbound (egress) IP addresses for deployed applications.

If your goal is to secure access to your database, we generally recommend relying on TLS and strong authentication rather than IP allowlisting alone. Since multiple applications on the platform share the same outbound IP pool, using a static shared IP would not provide a significant security benefit.

If the IP allowlisting requirement is primarily due to a limitation of your database or hosting provider, you may be able to allow a broader IP range (such as the AWS egress IP pool), or, if appropriate for your environment, allow connections from 0.0.0.0/0 while relying on TLS and authentication for security.

You may also want to consider moving your database to one of the providers we integrate with, as this can simplify connectivity and deployment. You can find the list of supported integrations here: https://fastapicloud.com/docs/integrations/

If this feature is essential for your use case, please consider submitting a feature request.
This helps us understand how many users would benefit from it.