With Fixie static IP, your Sevalla applications can send any (HTTP, HTTPS, Database, TCP, and more) outbound requests from a fixed set of static IP addresses. Fixie for Sevalla is language- and framework-agnostic.

Sevalla's own documentation is upfront that IP-based allowlisting is a weak fit for its platform: apps running on Sevalla's Google Cloud data centers get outbound traffic from Google's published IP ranges, which refresh regularly rather than staying fixed. Fixie sits in front of all of that: your app connects to one Fixie proxy, and the two IPs it hands back stay the same regardless of which data center or cloud Sevalla runs your app on.

Fixie can be used with any backend language, including JavaScript, Ruby, Python, Java, Go, Elixir, and PHP. Sevalla builds all of these with Nixpacks, its default build system; its older Buildpacks option covers every language on this list except Elixir, so pick Nixpacks if your app needs it.

Unlike Heroku and Vercel where there are native integrations available, Sevalla support needs to be added manually at this time.

Getting Started

To get started, create a Fixie account, and create a new Proxy Application.

After the proxy is created, go to Proxy's Details page where you'll see a couple of important values:

• Proxy URL: Your Fixie HTTP/S or SOCKS proxy URL that includes your username, password and proxy server load-balancer to use.
• Outbound IPs: Your pair of Fixie IP-addresses. These will never change, so feel free to allow-list them with firewalls or services.

Configure Your Application

Next, update your application to use your Fixie proxy server. Sevalla builds applications in many popular languages, and we have documentation for most of them:

• JavaScript/TypeScript
• Ruby
• Python
• Java
• Go
• Elixir
• PHP

You also need to make sure Fixie credentials are accessible by your Sevalla application. We recommend against hardcoding the values in the source code and instead adding your Proxy URL through your application's environment variables panel, available under your app's settings in the Sevalla dashboard. We recommend the following naming conventions for Environment Variables so it's easier to follow along with our documentation:

• FIXIE_URL for your Fixie HTTP/S proxy
• FIXIE_SOCKS_HOST for your Fixie SOCKS proxy

If several of your Sevalla applications call the same allowlisted service, Sevalla also supports global environment variables that apply across all of your applications, so you don't need to re-enter the Fixie proxy URL for each one individually. Feel free to create different Fixie proxies for different environments (for example, development and production) to keep credentials and logs separate.

If you'd rather manage variables from the terminal, the Sevalla CLI supports setting them directly:

sevalla apps env-vars create <YOUR_APP_ID> --key FIXIE_URL --value "<YOUR_PROXY_URL>"

Local setup

To use Fixie locally, replicate the FIXIE_URL and/or FIXIE_SOCKS_HOST environment variables in your local environment. For example, you can add it to .env file locally.

Keep sensitive configuration values, like credentials, out of source control. Exclude the .env file in Git with: echo '.env' >> .gitignore.

Changing plans

Use the Fixie dashboard to change your plan. To change the plan, click Change Plan button and select an appropriate plan.

NOTE: Changing the plan won't affect your outbound IP address

Deleting a proxy

To remove the proxies, go to the Fixie dashboard and select Delete for the desired proxy.

Related static IP guides

For making API requests with a static IP from a Node app on Sevalla, see Node.js on Sevalla.

See the full list of static IP guides for every supported language, platform, and destination.