Managed static egress · Dedicated IPv4
Get your IP. Connect your app. Keep building. Connect with the Penduses SDK.
We manage your egress and keep your IP fixed across deployments.
For the API, webhook or business system that will only accept requests from an approved IP. Start with a compatible server-side HTTP(S) client.
Give this address to the partner whose API you need to reach.
Redeploying your app does not change the IP allocated to your Penduses service.
Your partner allows connections from your IP.
You choose which destinations your service can reach by adding them to your Penduses allowlist. Requests to unlisted destinations are refused.
Check your outbound IP, then make a real request to your partner’s API.
await egress.verifyIp(echoUrl)
The IP check is the first step. Confirm that the real API call succeeds and that your partner sees the assigned address.
The board, addresses and responses are illustrative examples, not live test results.
This Node.js example shows the connection path. Send an API call through egress.fetch; ordinary fetch calls keep their existing route.
import { createEgress } from '@penduses/egress';
const egress = createEgress({
endpoints: [{
host: process.env.PENDUSES_HOST,
httpPort: Number(process.env.PENDUSES_HTTP_PORT),
username: process.env.PENDUSES_USER,
password: process.env.PENDUSES_PASSWORD,
tls: true,
}],
expectedIp: process.env.PENDUSES_EXPECTED_IP,
});// Use an HTTPS IP-echo endpoint you trust.
// Add its destination to your allowlist first.
const { observedIp, ok } = await egress.verifyIp(
process.env.PENDUSES_ECHO_URL
);
console.log({ observedIp, ok });// TARGET_URL must also be on your allowlist.
const response = await egress.fetch(
process.env.TARGET_URL
);
console.log(response.status);Set the endpoint hostname, port, credentials and expected IP supplied for your service. Keep credentials on the server. The endpoint hostname must match its TLS certificate.
Add an HTTPS IP-echo endpoint you trust to your destination allowlist, then call egress.verifyIp to check the outbound address.
Add your API destination to the allowlist and call it with egress.fetch. Your partner’s API authentication still applies.
Vercel / Next.js is our starting point. On another platform? Tell us your runtime and target so we can check the actual connection before you choose a plan.
Your outbound address is allocated to your service and is not shared with other customer services. App redeploys do not change that allocation. Pro has two addresses; your partner must allow both.
We operate the egress infrastructure. The SDK verifies the service’s TLS certificate before sending credentials. Keep those credentials on your server; your partner’s own API authentication still applies.
Choose which destination IPs and ports the service can reach. Calls through Penduses to other destinations are refused. Requests you do not route through Penduses keep their existing path.
If the SDK cannot connect through its configured egress endpoints, it returns an error. Pro can try a second endpoint for eligible connection failures before a request is sent. Requests that may already have been sent are not replayed.
Tell us about your integration. We will confirm compatibility, region, monthly price, included usage and limit behavior in your pilot quote before you commit.
For an API integration that needs one dedicated source IP.
For integrations that need a second connection path and can allow two IPs.
The recurring price of the plan you purchase stays fixed until you cancel. Upgrade later and the current price of the higher plan applies.
Price protection covers your purchased plan, not every future plan or usage charge. Your quote will specify included usage, any additional charges and cancellation terms. Pilot service: best effort, no SLA.
Still unsure? Email us your setup.
No. Keep your existing deployment and route the selected server-side HTTP(S) requests through Penduses. Our Next.js example uses the Node.js runtime. Other platforms and clients need a compatibility check; this is not a switch for all project traffic.
Only requests explicitly routed through Penduses. Other traffic keeps its existing route. If your application uses separate service identities for different tenants, use a separate client for each identity.
Redeploying your app does not change its Penduses allocation. Ending the service releases the address. Discuss migrations or service changes with us so you can account for any required allowlist updates.
The fetch example covers HTTP(S), not database or SFTP clients. Send us your runtime, client and destination for a separate review. WireGuard on a server you control is a different setup; it does not mean WireGuard runs inside a Vercel Function.
With one endpoint, the SDK returns an error. With Pro, eligible connection failures can trigger an attempt through the second endpoint before the request is sent.
Existing connections are not moved. Requests that may have been sent are not replayed. Authentication, certificate and destination-policy errors must be resolved. The SDK does not fall back to a direct connection.
Start with an allowed HTTPS IP-echo endpoint and compare the observed address with your expected IP. Then make a real request using your actual API client and confirm the result with your partner. A successful IP check alone does not prove every library uses the same route.
Choose from the available regions with your application and destination in mind. Routing through Penduses adds a network hop, so measure actual request times during the pilot.
Your pilot quote will state the monthly price, included transfer, connection limits and what happens when you reach them. Send a rough usage estimate, or tell us if you do not know it yet. Your hosting provider may still charge for outbound traffic.
Its built-in option may be enough. Penduses is worth checking when your partner requires an IP dedicated to your service, you want to route only selected API calls, or you do not want to operate your own egress infrastructure. Compare the full setup and usage costs; a lower total bill depends on your workload.
Tell us which apps, environments and customers you need to connect. Shared usage counts toward the service’s limits. Different customer identities may need separate IPs and credentials; we will confirm the arrangement before quoting.
The destination allowlist uses IP addresses and ports. A hostname or CDN can resolve to different addresses, so its required destinations need to stay on the list. We will review this during setup; it is separate from keeping your own source IP fixed.
No. Static Egress handles outbound connections. For routed inbound and outbound IPv4 on a host you control, ask about Tunnel IP.
Routed public IPv4 over WireGuard for a host you control. Discuss /32, /29 or /28 options for inbound and outbound connectivity.
Ask about Tunnel IPIPv4 blocks for hosting companies and network operators. Contact us about routing, address management and commercial terms.
Discuss a blockTell us where your app runs, which API you need to reach and whether the partner requires a dedicated IP. A rough usage estimate helps; “not sure yet” is fine.
We will check the setup and send a pilot proposal with scope, price and next steps. We operate the address space and servers behind Penduses.
Opens your email app with a short setup checklist. No signup or payment.
hello@penduses.com