Who runs RyoProxy
Six recurring shapes of deployment. They differ in what they sell, but they all own the routers and need the same control plane underneath.
- [segments]
- 6
- [deployment]
- self-hosted · Docker Compose
Proxy sellers running their own hardware
You own routers and PPPoE lines and sell access to them. The platform turns each WAN into addressable HTTP and SOCKS endpoints, rotates credentials in bulk, and gives every customer a scoped key they can rotate themselves.
outcome: Provisioning a new customer stops being a manual RouterOS session.
key capabilities
- › Per-WAN proxy provisioning
- › Bulk credential rotation
- › Per-interface API keys
- › Scoped per-customer access
Small ISPs and multi-line operators
Dozens or hundreds of PPPoE lines behind one router need balancing, watchdogs and redial policy. PCC or plain ECMP, a 2-minute WAN watchdog and per-line rotation schedules are configuration, not scripts you maintain.
outcome: A dead line redials itself before anyone opens a ticket.
key capabilities
- › Multi-WAN PCC / ECMP
- › PPPoE bulk provisioning
- › WAN watchdog
- › Traffic accounting
Network teams with a MikroTik fleet
Declarative config across 22 RouterOS categories, drift reported per item, guided bootstrap for new routers, and an audit log with CSV export covering who changed what.
outcome: Fleet-wide consistency you can prove, not assume.
key capabilities
- › Declarative config + drift
- › Guided router bootstrap
- › Audit log with CSV export
- › Role-gated access
Automation and bot developers
Rotation, status and IP lookup are plain GET endpoints. One key can cover a whole router, or exactly one line and nothing else.
outcome: A shell script or worker rotates an IP with one URL — no session, no SDK.
key capabilities
- › Keyless rotation endpoints
- › Per-interface scoped keys
- › Run-now rotation
- › Copy-paste API examples
Teams that live on IP quality
Continuous reputation checks score every line, blacklist lookups run through a residential pool, and a blocked line rotates automatically with a cooldown instead of burning attempts.
outcome: Bad IPs are replaced before a customer reports them.
key capabilities
- › Residential scoring 0–100
- › Blacklist lookup
- › Auto-rotate on block
- › 90-day IP history
Remote access and site-to-site
WireGuard clients with QR codes, Apple profiles, expiry dates, LAN policy and a routing mark that pins a client to a chosen WAN — plus imported site-to-site tunnels.
outcome: VPN access becomes a two-minute task with a clear revocation path.
key capabilities
- › WireGuard clients + QR
- › Per-client WAN pinning
- › Site-to-site tunnels
- › Expiry and LAN policy
If your deployment does not look like any of these, describe it — the platform is modular and most fleets fit somewhere.
[ describe your setup ]