Who runs RyoProxy on MikroTik
Proxy sellers running their own hardware
key capabilities
Provisioning a new customer stops being a manual RouterOS session.
You own routers and PPPoE lines and sell access to them. The platform turns each WAN into addressable HTTP and SOCKS5 endpoints, rotates credentials in bulk, and gives every customer a scoped key they can rotate themselves.
Small ISPs and multi-line operators
key capabilities
A dead line redials itself before anyone opens a ticket.
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.
Network teams with a MikroTik fleet
key capabilities
Fleet-wide consistency you can prove, not assume.
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.
Automation and bot developers
key capabilities
A shell script or worker rotates an IP with one URL — no session, no SDK.
Rotation, status and IP lookup are plain GET endpoints. One key can cover a whole router, or exactly one line and nothing else.
Teams that live on IP quality
key capabilities
Bad IPs are replaced before a customer reports them.
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.
Remote access and site-to-site
key capabilities
VPN access becomes a two-minute task with a clear revocation path.
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.