SSD Nodes Learn Hosting plans →
Guides Matt ConnorBy Matt Connor

Is self-hosting legal? What actually stops you

Self hosting is legal. What stops you is your ISP contract, a blocked port 25, CGNAT, and licences like SSPL and BSL. Here is what each one really blocks.

Yes. Self-hosting is generally legal, but the rules depend on your country and what you run. What stops people is a contract they agreed to, or a network they do not control. Four constraints do almost all of the blocking: a residential internet service provider's terms of service, a blocked outbound port 25, CGNAT (carrier grade network address translation), and the licence on the software itself.

Renting a VPS removes the residential contract and, with a public address, the CGNAT problem; port 25 still depends on the host. It changes nothing at all about the fourth. That asymmetry is most of the reason people who start on a home broadband line end up on a rented server.

One note before the detail: this is written by people who run servers, not by lawyers, and it is not legal advice. Which rules apply to you depends on your country and on what you choose to serve.

Your ISP says "no servers", and that is a contract, not a law

Many residential broadband contracts contain a clause that forbids running servers on the connection. Breaking that clause is a contract matter between you and your ISP. The consequences depend on the contract; Xfinity's residential acceptable use policy allows suspension or termination. There is no criminal exposure in the clause itself, which is why the question "is self-hosting legal" and the question "will my ISP let me" have different answers.

The gap between the clause and what gets enforced is wide, and it is worth understanding why. ISPs monitor network activity and investigate abuse complaints; AT&T also explicitly scans network addresses for vulnerabilities. A quiet service is no guarantee that a server prohibition will not be enforced.

Two other residential facts matter more than the clause in practice. A dynamic address needs dynamic DNS to keep its public name current, and an address change can interrupt access while records and caches update. A business-class plan is worth checking for permission to run servers and the option of a static address; neither is guaranteed just by the word "business".

Why is port 25 blocked, and can I get it opened?

Port 25 is the TCP port that SMTP (simple mail transfer protocol) servers use to hand mail to each other. Consumer ISPs including AT&T block outbound connections to port 25 to reduce spam and malware abuse.

Providers block it too. As of November 3, 2026, AWS blocks outbound port 25 on EC2 by default, not only for new accounts. The EC2 User Guide says traffic over port 25 "is blocked to public IPv4 addresses and IPv6 addresses", with exceptions for your VPC's primary CIDR block and the RFC 1918, RFC 6598 and RFC 4193 ranges. It is a block rather than a quota you raise, and you can request that the restriction be removed. Google Cloud also blocks connections to destination TCP 25 on external addresses by default, but permits connections within your own VPC (virtual private cloud), to peered VPCs and to on-premises networks connected through Cloud VPN or Cloud Interconnect, subject to firewall rules. Its firewall documentation says Google Cloud "automatically removes this block once it determines a project is at low risk" of sending large volumes of unencrypted email, and a banner on the VPC networks or Firewall policies page in the console shows whether your project permits the traffic. Other hosts keep the block permanent: LightNode says port 25 cannot be opened on request.

The direction matters. Inbound port 25 is how your server receives mail. Outbound port 25 is how it delivers mail. So a blocked outbound 25 produces a server that accepts mail perfectly and never delivers any: the queue grows, and the log fills with connection timeouts to the recipient's MX host. Where submission ports 587 or 465 are open, you can still send through a third party relay and keep receiving on your own box. DigitalOcean blocks ports 25, 465 and 587 on all Droplets by default, so check those ports before choosing a relay; an email service's HTTPS API is another route for application mail. Whether the whole exercise is worth it is a separate question, and self-hosting email has costs beyond one open port.

CGNAT leaves you with no address to be reached at

CGNAT means your ISP has put multiple customers behind a shared public IPv4 address. Your router's WAN address commonly comes from 100.64.0.0/10, the shared address space reserved in RFC 6598, or from an ordinary private range, though an ISP can also number that link from globally unique addresses. Port forwarding on your own router then does nothing, because the translation that matters happens on ISP equipment you have no access to. Unsolicited inbound IPv4 connections need a mapping at the ISP's translation layer too.

The test takes thirty seconds. Read the WAN IPv4 address from your router's status page, then compare it with the public IPv4 address reported by an address-checking page. A WAN address from 100.64.0.0 through 100.127.255.255 is a sign of CGNAT. A WAN address outside that range does not rule CGNAT out, because the ISP may number the link from public addresses. Different addresses alone do not establish CGNAT: another router in your home can cause the difference, and you need to forward the port on that upstream router too. Ask your ISP to confirm whether it uses CGNAT if you cannot account for the upstream translation.

There are four ways out. Ask the ISP whether it offers a public IPv4 address and what it costs. Use IPv6, if your ISP gives you a real prefix and you accept that visitors on IPv4-only networks cannot reach you. Keep the service at home and put the public listener on a VPS, reaching back over a tunnel, which is what advertising your home network from a subnet router on a VPS does. Or move the service onto the VPS and stop fighting the access problem. Those last two are different goals, and a VPS and a VPN answer different questions.

Do software licences like SSPL and BSL stop me self-hosting?

No, and this is the constraint readers misjudge most often. Several widely self-hosted projects have moved off standard open source licences since 2018. The restrictions differ: SSPL covers making the software's functionality available to third parties as a service, even for free and even when the operator is an individual. Running an instance for your own use or your employer's internal work is different from offering that functionality to third parties, but each licence's terms still apply.

The SSPL (Server Side Public License), used by MongoDB from 2018 and by Elasticsearch from 2021, states the obligation directly in its section 13: "If you make the functionality of the Program or a modified version available to third parties as a service, you must make the Service Source Code available via network download to everyone at no charge, under the terms of this License." The trigger is offering the functionality as a service. A login does not exempt a service you provide to third parties. Elasticsearch also offers AGPLv3 as an option for the free portions of its source code, added in 2024; its default distribution remains under Elastic License 2.0.

The BSL (Business Source License) version 1.1 comes from MariaDB and is used by HashiCorp's Terraform, among others. It grants non-production use outright, and each vendor can add an Additional Use Grant on top. Terraform's grant reads: "You may make production use of the Licensed Work, provided Your use does not include offering the Licensed Work to third parties on a hosted or embedded basis in order to compete with IBM Corp.'s paid version(s) of the Licensed Work." Every BSL release also carries a Change Date, at most four years after publication, when it converts to the Change License. For Terraform that is MPL 2.0, so each release becomes open source on a schedule.

n8n uses its own Sustainable Use License. It permits you to "use or modify the software only for your own internal business purposes or for non-commercial or personal use", and allows you to pass it on "only if you do so free of charge for non-commercial purposes". Automating your own company's work is inside that grant. Selling hosted n8n to other people is not. Redis is a third pattern: as of Redis 8, released in 2025, contributions are offered under a choice of RSALv2, SSPLv1 or AGPLv3, while 7.2 and earlier remain BSD 3-clause.

The AGPL deserves one line of its own, because people fear it without reading it. Its network source obligation applies when you modify the program and let users interact with that version remotely; distributing copies brings separate source obligations. Run an unmodified build for yourself and you owe nobody anything.

A useful test: are you making this software's functionality available to other people as a service? If the answer is yes, check the exact licence even if nobody pays you. A licence breach can lead to a copyright claim and loss of your permission to use the software. Copyright infringement can also be criminal in specified circumstances, so there is no blanket exemption from criminal law.

What renting a VPS changes, and what it does not

Three of the four constraints change when you choose a rented server with a public address and a suitable mail policy.

  • The residential "no servers" clause is gone, because a VPS acceptable use policy assumes you are running servers. That is the product.
  • A routable public IP address removes the CGNAT obstacle; inbound access still depends on firewall rules and provider restrictions.
  • Port 25 depends on the host. AWS accepts removal requests, while LightNode says its block is permanent.

Licensing changes by exactly nothing. It is the same software under the same terms, and the line it draws is about who you serve rather than where the CPU lives.

Renting also adds an obligation that home hosting mostly hides from you. You become the operator of record for a public IP address, so traffic leaving it is attributed to you. When something goes wrong the notice lands at your host and then in your inbox, which is worth reading about before it happens: what an abuse complaint is and how to answer one and the operational duties you accept when you rent a server.

What a host's acceptable use policy usually restricts

Acceptable use policies differ between providers, and you should read the one you signed rather than trusting a summary of the genre. This one included. What follows is the pattern these documents share, not any single company's position.

  • An open SMTP relay, meaning a mail server that accepts mail from anyone and forwards it anywhere. Spammers find one within days of it appearing, and the first consequence is your address on public blocklists.
  • An open DNS resolver. A short query can produce a large answer, so an attacker who spoofs the source address turns your resolver into a way to aim traffic at someone else. That is why a recursive resolver is expected to answer only your own networks.
  • Open proxies and exit nodes that you do not police. A proxy anyone can use makes your IP address the visible source of whatever they do; legal responsibility depends on the facts and applicable law.
  • Unauthorized outbound port scanning and login brute force, whether you launched it or a compromised container did.
  • Distributing material you have no right to distribute, which is the policy line that usually arrives as a copyright notice rather than as a technical complaint.

Resource rules sit in the same document and are worth a glance: shared plans often cap sustained CPU use, and some hosts prohibit cryptocurrency mining outright. Those are contract terms, not law.

The act of running a server is not where your risk lives. Two other things are.

The first is what you serve. Copyright is the common case. A media server playing your own discs to your own household is one question, and sharing that same library with people outside it raises separate copyright questions about reproduction, distribution and public performance under local law. Defamation, regulated content and anything requiring a licence to publish work the same way: the server is neutral, and the content is what a claim would be about.

The second is whose data you hold. Under the GDPR (general data protection regulation), Article 2(2)(c) puts purely personal or household activity outside the regulation entirely. So a Nextcloud holding your family's own files is not in the same position as a forum with two hundred registered accounts. Holding other people's personal data alone does not make you a controller: outside the personal or household exemption, that role depends on deciding the purposes and means of processing, rather than processing only on someone else's instructions. Controllers need a lawful basis and must answer applicable subject access requests. They must document personal data breaches and notify the authority without undue delay, where feasible within 72 hours of awareness, unless a breach is unlikely to risk individuals' rights and freedoms. IP addresses in logs can be personal data, which is why self-hosted analytics you can configure to discard identifiers is a calmer starting position than a stack that keeps full addresses forever. Purely personal or household processing stays inside the exemption, so keeping your budget in a self-hosted app is a security responsibility rather than a compliance one.

There is one US-specific point worth knowing if you host content other people upload. The DMCA safe harbour in section 512(c) is available only to a service that has designated an agent with the Copyright Office. Skipping that registration does not create liability on its own. It removes a defence you would otherwise have.

Where to start now that the answer is yes

The remaining decisions are practical once you have checked the rules that apply to your service: which services earn the maintenance they cost, and what the first one looks like end to end. Start with which services are actually worth self-hosting, then follow how to self-host a website on a server you control for the first deployment.

FAQ

Can my ISP cancel my internet service for running a server?

It can, because a residential contract that forbids servers makes this a contract matter and termination is one of the remedies a contract allows. Do not assume that a small service is exempt or that a warning must come first. Check whether a business plan permits your server and offers a static address; the address can be an optional extra.

Why can my self-hosted mail server receive email but not send it?

A blocked outbound TCP port 25 is one cause. Receiving uses inbound 25, while delivery needs an outbound connection to port 25 on the recipient's mail exchanger, so a block leaves queued mail and connection timeouts in the log. Consumer ISPs including AT&T block outbound 25 to reduce abuse. Some providers block it by default too: as of November 3, 2026, AWS blocks port 25 to public addresses on EC2 by default and accepts removal requests. Google Cloud blocks external destination TCP 25 by default, with exceptions for your own VPC, peered VPCs and on-premises networks connected through Cloud VPN or Cloud Interconnect, subject to firewall rules; it automatically lifts the external block for projects it judges low risk. Send through a relay on port 587 or 465 where those ports are open, or host somewhere that will open 25 on request. DigitalOcean blocks all three ports by default, so application mail there needs another permitted route, such as an email service's HTTPS API.

Does an SSPL or BSL licence stop me self-hosting the software?

No. SSPL section 13 only applies when you make the software's functionality available to third parties as a service, and a BSL 1.1 release grants non-production use outright plus whatever production use the vendor's Additional Use Grant allows. Terraform's grant permits production use unless you are offering a hosted or embedded version that competes with the paid product. n8n's Sustainable Use License permits use for your own internal business purposes or personal use. Payment is not the universal dividing line: SSPL's service obligation also covers free services and individual operators.

Do I need to think about GDPR for a server only my family uses?

Article 2(2)(c) of the GDPR excludes processing carried out for purely personal or household activity, so a photo library or file sync server used by your own household falls outside it. Accounts for friends do not automatically end that exemption; the circumstances determine whether the activity remains personal or household. Outside the exemption, deciding the purposes and means of processing makes you a controller. That brings a lawful basis, applicable access rights and breach duties: document every personal data breach, and notify the authority without undue delay, where feasible within 72 hours of awareness, unless it is unlikely to risk individuals' rights and freedoms. The practical step is to decide early which side of that line a service is on, and to keep logs and analytics configured so you are not storing identifiers you never wanted.

Was this article useful?

#self-hosting#legal#isp#terms-of-service#licensing#vps