Permitted here
A URnetwork provider is an allowed workload on a project server, alongside Mysterium and WireGuard.
URnetwork 2026.7.2 Networking
Free credit available Limited time
Deploy a URnetwork Docker provider Share a server's bandwidth on a host that permitsย it.
URnetwork Docker without the setup. Paste one auth code from your URnetwork account and your provider runs on a Selfhost.dev server we provision, secure and run, where bandwidth sharing is allowed. No open ports, no password, nothing to manage.
No password in the container, no panel to expose. Your URnetwork account is the dashboard.
URnetworkone-click template ready
- providerURnetwork, in Docker
- sign-inone auth code
- portsnone inbound
- identitykept across code changes
- on our serverspermitted
European 4 GB server$0.02/hr
In one line
What is a URnetwork provider?
What it is
URnetwork is a decentralized privacy network. A provider is the node that shares an internet connection as an exit for people using the URnetwork app. This template runs that provider on a server.
Where to start. Open the console with URnetwork selected
Who it is for
URnetwork users who want an always-on provider that does not depend on a laptop or a home router.
When to use it
When you want the node to run all day without opening ports or storing your password. To use URnetwork for your own privacy, you need the app instead.
Containers
URnetwork Docker, set up for you
URnetwork Docker guides start the provider in two steps: an auth command that writes a token to a folder you must keep, then the provider itself. Some community images ask for your account email and password instead. This template takes one auth code at deploy and keeps the node identity for you.
The stack, end to end
Callers
People using the URnetwork app
Edge
Outbound only
Your project server
Container
URnetwork provider
From ur.io/app
Auth code
Kept
Node identity
| Running URnetwork Docker by hand | URnetwork on Selfhost.dev |
|---|---|
An interactive auth step, then a volume you must not lose | One auth code pasted in the console at deploy |
| Or your URnetwork email and password in environment variables | Never your password |
| A bandwidth page on port 8080 in some images | No inbound ports at all |
| A new token and a fresh start if the folder is lost | The node identity kept; replace a rejected code from the console |
| Your own server's terms to check | Permitted on our servers |
Nothing on the server listens for it: the provider dials out. Deploy the stack
Allowed
Can you run URnetwork on a server?
AI answers often warn that bandwidth sharing breaks the terms of many VPS hosts. On Selfhost.dev it does not: running a URnetwork provider is permitted. We asked our infrastructure provider before adding this template and were told there are no restrictions for this use.
No ports to open
The node only connects out, so the server's firewall stays closed to it.
Your account decides the rest
Whether the node carries traffic and what it earns are up to URnetwork, shown in your account.
Server
URnetwork Docker provider requirements
URnetwork Docker provider requirements on this template are short. A 4 GB server, the smallest we offer, on x86 or ARM. An auth code from your URnetwork account at ur.io/app. Nothing else: no ports to forward, no domain and no login to set up.
What it needs
- Server
- 4 GB, the smallest server we offer; x86 or ARM
- Provider image
bringyour/community-provider:2026.7.2-982300760, an exact tag- URnetwork account
- An auth code from ur.io/app, pasted at deploy
- Ports
- None; the provider only connects out
- Login, web interface, domain
- None; you manage it at ur.io
Server size: 4 GB, enough for URnetwork. Deploy on a 4 GB server
Quickstart
How to deploy URnetwork in 3 steps
One auth code, one click, then check your account.
-
Copy an auth code
Sign in at ur.io/app, open Account Settings and generate an auth code valid for at least 60 minutes. Codes from the phone and desktop apps expire after 5 minutes, too soon for a new server.
-
Launch the template
Launch opens the URnetwork template in the console. Paste the auth code, confirm the bandwidth notice and pick a 4 GB server. The template deploys in about ten minutes.
-
Check your account
Open ur.io/app and confirm the new provider appears. That is where you pause it, remove it and see any earnings.
Deploy URnetworkStep 1 starts in the console.
Launch URnetwork Billing
What a URnetwork provider costs here
A URnetwork provider here costs the server and nothing else. We bill it by the hour from prepaid credits; a European 4 GB server is $0.02/hr, about $15 to $16 a month. There are no bandwidth charges on project servers, so the traffic the provider shares adds nothing to the bill.
| Item | Cost |
|---|---|
| The URnetwork template | $0 |
| Bandwidth the provider shares | $0, traffic is included in the server price |
| Optional daily backups | +20% of the server price |
| Server | RAM, cores, disk | Where | Rate | About a month |
|---|---|---|---|---|
cx23 (recommended) | 4 GB, 2 cores, 40 GB | Europe | $0.02/hr | $15.18 |
cax11 (ARM) | 4 GB, 2 cores, 40 GB | Europe | $0.02/hr | $16.35 |
cpx21 | 4 GB, 3 cores, 80 GB | US | $0.12/hr | $87.75 |
cpx22 | 4 GB, 2 cores, 80 GB | Singapore | $0.10/hr | $72.56 |
Monthly figures assume 730 hours.
If your balance reaches zero
With a card on file or a past top-up, the provider keeps running for 5 days after your balance reaches zero. Then it is stopped and kept for 24 hours before it is deleted; a top-up in that time restarts it. After the delete, a copy of the server is kept for 14 days and you can restore the project from the Projects page. We email you when the balance reaches zero and again when it stops. Welcome-credit-only servers are deleted at zero, with a 3-day copy if the project went live.
Price another size or region in the calculator, no signup.
Options
URnetwork provider vs a Mysterium node
A URnetwork provider and a Mysterium node do the same job on a server: they share its bandwidth with a decentralized network. The difference is how you run them. URnetwork is managed from your online account and opens no ports. Mysterium has its own panel on a port only your IPs reach.
| URnetwork provider | Mysterium node | |
|---|---|---|
| How you connect it | An auth code from ur.io/app | A panel login, then your MystNodes account |
| Inbound ports | None | The panel port, open to your IPs only |
| Where you manage it | Your URnetwork account | The node panel and MystNodes |
| Where earnings show | Your URnetwork account | Your MystNodes account |
Mysterium details from our Mysterium node template.
When a Mysterium node is the better choice
When you want a panel on the server itself to watch sessions and traffic. URnetwork keeps everything in its online account, so there is nothing to open on the server and nothing to see there either.
Status
Five checks on every URnetwork provider
- Every service is health-checked every 60 seconds.
- Running means signed in. The console marks the node Running only after it has traded its code for a URnetwork login.
- No inbound port is published for it. The provider only connects out.
- The node identity survives an auth code change. Replacing the code keeps the same node.
- Your password never reaches the server. The template asks for an auth code, not your login.
~10 min to deploy
The console estimates about ten minutes for the URnetwork template after the server is ready; first-time server provisioning adds time.
Notes
URnetwork Docker provider limitations
- No local interface. There is no dashboard on the server; you see and manage the node only in your URnetwork account.
- Running is not earning. The console reads Running only once the node has signed in to URnetwork, but its traffic and earnings are up to URnetwork. Check the provider in your account after deploying.
- A rejected code needs you. The node uses its auth code once, at its first start. If URnetwork rejects it or later stops accepting the node's login, paste a fresh code in the console; there is no automatic retry. The node keeps its identity.
Nothing here in your way? The template deploys in about ten minutes.
Launch URnetwork Planning
Running providers on more than one network?
Tell us which networks and how many servers you have in mind. We reply with the sizes we would pick and what they cost a month.
Help
Frequently asked questions
Can I run a URnetwork node on Selfhost.dev?
Yes. Running a URnetwork provider is permitted on our project servers; we checked with our infrastructure provider before adding the template. The node shares the server's bandwidth with the URnetwork network, connects out only and needs no inbound ports. Other people's traffic then reaches the internet from your server's IP address, not your home. You deploy it with an auth code from your URnetwork account.
Where do I see what the node earns?
In your URnetwork account at ur.io/app, where you also pause or remove the node. There is no local interface on the server. The console reads Running once the node has signed in, but whether it carries traffic and earns is up to URnetwork, so check the provider there after deploying. See pricing.
What happens when the auth code expires?
Nothing, once the node has started. It trades the code for its own URnetwork login at its first start and reuses that login on every restart. If URnetwork rejects the code before then or stops accepting the node's login later, paste a fresh code in the node's settings in the console. The node keeps its identity and its deployment starts again; there is no automatic retry.
Does a URnetwork provider need open ports?
No. The provider only makes outbound connections to the URnetwork network, so nothing is published on the server for it. There is no web interface or domain to set up either. Everything you would manage, from pausing to earnings, lives in your URnetwork account.
Do I need to give the template my URnetwork password?
No. You paste an auth code from ur.io/app when you deploy. That is all the template asks for. Some community Docker images ask for your account email and password in environment variables; this one never does. The node spends the code at its first start and signs in with its own login after that.
Share your server's bandwidth. On a host that permits it.
- A URnetwork provider in Docker, permitted on our servers
- One auth code, no ports and no password stored
- A European 4 GB server, about $15 to $16 a month
About Selfhost.dev
Selfhost.dev is a managed self hosting platform for developers and small teams. Open source apps and databases on dedicated servers you control, billed by the hour, in six locations across three continents.
Best for: URnetwork, Mysterium, WireGuard and managed PostgreSQL, MySQL, Redis, ClickHouse, OpenSearch and Kafka.