Supported Environments and Platform Limits
Use the supported environment below for normal MyOwnProxy deployments. See System Requirements for the full preparation and readiness checklist.
Supported environment
| Component | Current supported baseline |
|---|---|
| Gateway | Ubuntu 24.04 LTS, at least 4 GB RAM, administrative operating-system access through sudo, a static public IPv4 address, and stable Internet connectivity. |
| Node | Raspberry Pi 4 Model B or Raspberry Pi 5, at least 2 GB RAM, a 32 GB or larger High Endurance microSD card, the official power supply for the model, wired Ethernet, and stable Internet connectivity. |
| Application | SOCKS5 support with username-and-password proxy authentication. |
A passive heat-dissipating Node case is recommended. CPU, Gateway disk, fixed minimum bandwidth, cloud-provider, browser, and processor-architecture requirements are not published as stable customer requirements. Confirm unusual or high-traffic deployments with MyOwnProxy Support.
The Gateway must be able to obtain MyOwnProxy software during installation and maintain control-plane connectivity during normal operation. Nodes require wired Ethernet for normal operation. Use the installation and connection values displayed by MyOwnProxy; do not derive firewall, port, hostname, or other network requirements from resource identifiers.
Stable product constraints
| Area | Current boundary |
|---|---|
| Node assignment | An operational Node is assigned to one Gateway at a time. |
| Proxy and Pool membership | A Proxy is associated with one Gateway. Pool Nodes must belong to the same Customer and be assigned to that Gateway. |
| Customer-created Proxy | It starts with an empty Pool and cannot serve Pool traffic until an eligible Node is added. |
| System-managed Pool | Each Gateway has one pool-all Pool. MyOwnProxy automatically keeps it populated with the Nodes assigned to that Gateway. Its membership cannot be edited manually, and it cannot be renamed or deleted. Customer-created Pools require explicit membership management. |
| Routing TTL | A customer-defined whole-second value must be from 60 through 3,600 seconds. TTL expiration causes reevaluation, not a required Node change. |
| Temporary Proxy Credential | Gateway-scoped, short-lived, Pool-only, and not customer-rotatable or customer-revocable before its displayed expiration. |
| Persistent Proxy Credential | Customer-scoped, usable for Pool and direct Node access, rotatable while Active, and permanently revocable. |
| Direct Node access | Requires a persistent Proxy Credential and depends on the selected Node and its assigned Gateway remaining available. |
| Temporary SSH access | ADMIN only. Supported certificate durations are 15 or 30 minutes, and the portal does not provide early revocation. |
MyOwnProxy does not publish a numeric Customer maximum for Gateways, Nodes, Proxies, Pools, or Proxy Credentials as a stable product contract. Confirm an unusually large deployment or a workload with significant bandwidth or connection demands with MyOwnProxy Support.
Boundaries not defined here
This documentation does not establish a universal inbound-firewall, NAT, IPv4-only, IPv6-only, redundancy, or capacity profile for every deployment. Follow the current MyOwnProxy installation workflow and confirm restricted or unusual network environments with MyOwnProxy Support before relying on them in production.