What Proxy Bastion is

The problem

The moment you send someone host:port:user:pass, you have lost control of it. You cannot tell who is using which credential, you cannot cut off one person without rotating the password for everyone else, and you have no way to cap how much traffic any single person can run through your account.

The relay model

Proxy Bastion does not sell proxies. It sits in front of the http and https proxies you already pay for. You register those proxies, group them into failover pools, and issue each person a separate relay link instead of your real proxy credentials.

A relay link looks like relay://<linkId>:<secret>@<relay host>. That link is the entire credential a renter receives. They never see the upstream address, the upstream username, or the upstream password.

What you get from the indirection

Because each person has their own link instead of your shared credentials, you can:

• Set an expiry date on a link.
• Set a traffic cap on a link.
• Revoke a single link without touching anyone else’s access or rotating your upstream password.
• Group several upstream proxies into a failover pool so a link keeps working if one pool member goes down.

What Proxy Bastion is not

Proxy Bastion is not a proxy provider. It does not add proxies of its own or improve the ones you already have. It is a control layer: a control plane where you register proxies and manage links, and a separate data plane that forwards the traffic for each active link. If your upstream proxies are unreliable or slow, relaying them through Proxy Bastion does not change that.