Static IP

Some systems you need to reach from a Vince Platform workflow — an on-premises SQL Server, an internal API behind a corporate firewall, and so on — only accept connections from a known, fixed set of IP addresses. Workflow steps normally run from a pool of cloud infrastructure, so by default there's no fixed address to allow-list.

Static IP solves this. Outbound requests made through a Connection with Use Static IP enabled always leave through fixed IP addresses, no matter which underlying infrastructure actually processes the step. You allow-list those addresses on your firewall, and Vince Platform can reach your system — without opening it up to the wider internet.

---

Which option do I need?

Ask yourself what your system, or your firewall, should accept. There are three options, and the difference is who else can use the address.

	Default	Shared static IP	Dedicated static IP
What your firewall says	"Connections from anywhere are fine."	"Connections from Vince Platform are fine."	"Connections only from my own Vince tenant are fine."
Where Vince traffic comes from	Different IP addresses every time	Always the same two addresses, used by every tenant that uses Static IP	One address, used only by your tenant
Setting on the Connection	Use Static IP off	Use Static IP on	Use Dedicated IP on. This is the same setting as Use Static IP, shown under this name when Dedicated IP is enabled for your tenant
What to allow-list on your firewall	Nothing	Both shared addresses	Your Dedicated IP
Cost	No extra charge	No extra charge, provided you keep within fair usage limits	Extra charge
How to get it	Nothing to do	Enable Use Static IP on the Connection	Request it from Vince support. Setup typically takes 2–3 days

If your system doesn't restrict access by IP address, for example a public API that anyone with the right credentials can call, you don't need Static IP. Leave Use Static IP off.

Shared or Dedicated?

Start with the shared IPs. You don't need to ask Vince for anything, and they cost nothing extra, provided you keep within fair usage limits. If you're unsure whether your use is within them, contact Vince support. Choose a Dedicated IP if your security policy doesn't accept an address that other Vince customers also use.

The shared addresses are used by every tenant, so your firewall can't tell one Vince customer from another. Only your credentials do that. A Dedicated IP is yours alone, so allowing it means allowing only your own tenant.

note

A Dedicated IP is not set up automatically. Request it from Vince support and allow around 2–3 days before you need it, so you can allow-list it on your firewall in good time.

---

Using the shared static IPs

These are Vince Platform's shared static IP addresses. Allow-list both of them on your firewall — outbound traffic can come from either one:

• 63.186.142.133
• 18.196.254.118

Then open the Connection to your system and enable Use Static IP (see Create a Connection). Requests made through that Connection will then go out via one of the addresses above.

---

Using a Dedicated IP

If your firewall must allow an address that no other Vince customer uses, a Dedicated IP is available for an extra charge.

1. Contact Vince support and ask for a Dedicated IP. Vince sets it up for you, which typically takes 2–3 days.
2. Allow-list the Dedicated IP on your firewall.
3. Open the Connection to your system and enable Use Static IP. A Dedicated IP still needs this setting on the Connection. When Dedicated IP is enabled for your tenant, the option is shown as Use Dedicated IP.

---

Which protocols are supported?

You don't choose a protocol. It follows from what you connect to:

• HTTP(S) — any workflow step that communicates over HTTP(S) through a Connection with Use Static IP enabled goes out through the static IP. This covers steps such as REST API and Code.
• SOCKS5 — used for TCP-based systems such as SQL Server, which don't speak HTTP. This is done in a Code step with authorizedSocks5, see the Code component page.

Both the shared static IPs and a Dedicated IP support both protocols.

---

Further reading

• Create a Connection — where Use Static IP is enabled
• Code component — authorizedAxios and authorizedSocks5, the helpers that route requests through a Connection, static IP included