Skip to content

System Requirements

Review these requirements before provisioning a Gateway or preparing a Node.

Account access

An ADMIN user is required to create and configure Gateways, Nodes, Proxies, and Proxy Credentials.

A VIEWER has read-only access and cannot complete the initial setup workflow.

Gateway requirements

A MyOwnProxy Gateway requires:

  • Ubuntu 24.04 LTS.
  • At least 4 GB of RAM.
  • Administrative operating-system access through sudo.
  • Stable Internet connectivity.
  • A static public IPv4 address.
  • The installation command and configuration values provided by MyOwnProxy when the Gateway is created.

The Gateway must be able to retrieve MyOwnProxy software during installation and maintain connectivity with the MyOwnProxy control plane during normal operation.

Follow the Gateway installation flow provided by MyOwnProxy. Do not reuse enrollment material for another Gateway or include it in logs, tickets, or documentation.

MyOwnProxy manages the MyOwnProxy application software installed on the Gateway.

You remain responsible for:

  • The Gateway host or virtual machine.
  • The Ubuntu operating-system lifecycle.
  • Operating-system security updates.
  • Host-level security and connectivity outside MyOwnProxy.

CPU and disk requirements may depend on the expected deployment size. Confirm larger or unusual deployments with MyOwnProxy Support.

Node requirements

MyOwnProxy Nodes currently support:

  • Raspberry Pi 4 Model B.
  • Raspberry Pi 5.

Each Node requires:

  • At least 2 GB of RAM. Higher-memory Raspberry Pi variants are supported, but additional memory is generally not required for normal MyOwnProxy operation.
  • A 32 GB or larger High Endurance microSD card.
  • The official Raspberry Pi power supply appropriate for the Raspberry Pi model.
  • An Ethernet cable.
  • A stable Ethernet connection to the router, switch, or network where the Node is deployed.
  • Internet connectivity.
  • The Node image and configuration values provided by MyOwnProxy.

A passive case with good heat dissipation is recommended. A Flirc-style case is a suitable option because it provides passive cooling without requiring a fan.

Prepare the Node

After creating the Node in MyOwnProxy:

  1. Flash the provided Node image to the microSD card.
  2. Open the customer-editable partition on the card.
  3. Add the configuration values provided by MyOwnProxy to the required configuration file.
  4. Insert the card into the Raspberry Pi.
  5. Connect Ethernet and power.
  6. Start the Node.

The Node completes its MyOwnProxy setup and enrolls automatically.

Normal onboarding does not require SSH access or manual commands on the Node.

See Preparing and Adding a Node for the complete customer procedure.

Network requirements

Gateways and Nodes require stable Internet connectivity.

Nodes must use a wired Ethernet connection for normal MyOwnProxy operation.

The bandwidth required by a Node depends on the amount and type of proxy traffic that it serves. MyOwnProxy does not currently publish a fixed minimum bandwidth requirement.

If you are planning a high-traffic deployment, confirm the expected network capacity with MyOwnProxy Support.

Application requirements

Applications connecting through MyOwnProxy must support:

  • SOCKS5.
  • Username-and-password proxy authentication.

Pool access is the normal MyOwnProxy operating model.

Direct access through a specific Node is also available when a particular exit Node is required.

Readiness checklist

Before starting the Quick Start, confirm that:

  • You have an ADMIN user.
  • Your Gateway runs Ubuntu 24.04 LTS with at least 4 GB of RAM.
  • You have a supported Raspberry Pi 4 Model B or Raspberry Pi 5.
  • The Node has at least 2 GB of RAM.
  • You have a 32 GB or larger High Endurance microSD card.
  • You have the appropriate official Raspberry Pi power supply.
  • The Node can be connected by Ethernet.
  • Gateway and Node Internet connectivity is available.
  • You have the installation material provided by MyOwnProxy.
  • Your application supports authenticated SOCKS5 connections.

See Supported Environments and Platform Limits for stable product constraints and boundaries that are not published as universal requirements.