squidservers.com

You can run a Minecraft server on your own computer and let friends join without touching router settings by using a desktop hosting app with built-in tunneling. SquidServers is one example: it's a free desktop application for Windows, macOS, and Linux that bundles tunneling through playit.gg, so your server is reachable without port forwarding. The trade-off is that your server only runs while your computer is on and the app is open — it is not a 24/7 hosting service.

Self-hosting vs. paid hosting: what actually changes

Before installing anything, decide whether self-hosting fits how you play.

Self-hosting makes sense when you play in sessions with friends, already leave your computer on, and want to avoid a subscription. Paid hosting makes sense when you need the world online around the clock or your hardware can't keep up.

Check your system before you start

SquidServers lists these requirements:

• OS: Windows, macOS, or Linux
• RAM: at least 4GB (8GB recommended for modded servers)
• Java: version 17 or higher — the app can help install the correct version if yours is out of date

If you plan to run a large modpack, treat the 8GB figure as a floor rather than a target, since the server, the game client, and your OS compete for the same memory.

Set up the server

1. Download and install SquidServers from the official site for your operating system.
2. Launch the app. On first run it checks your Java installation and offers to install the right version if needed.
3. Create a server and choose your edition:
   • Java Edition for the standard experience and mod support.
   • Bedrock Dedicated Server if your friends play Bedrock.
   • Crossplay via GeyserMC if your group is split between Java and Bedrock.
4. Add content if you want it. The app supports thousands of modpacks from Modrinth, plus custom mod installs through CurseForge Server Packs.
5. Configure basic settings — world name, game mode, player limits — then start the server.

Expected result: the server console reports a running server and the app shows a shareable address.

Let friends join without port forwarding

SquidServers includes built-in tunneling provided by playit.gg. When your server starts, the app exposes an address your friends can enter in their Minecraft client — no router configuration on your end.

One caveat from the site itself: for the best performance, port forwarding is still recommended when you can do it. Tunneling adds a relay hop, which can raise latency. If your friends report lag and you're comfortable editing router settings, switching to a direct port-forwarded connection is the better long-term option.

Troubleshooting the common failures

"My friends can't connect."

• Confirm the server is actually running in the app, not just installed.
• Make sure you shared the current tunnel address — it can change between sessions.
• Check that your friend is on the matching edition (Java vs. Bedrock) unless you set up GeyserMC crossplay.

"The server is offline when I wake up." This is expected behavior, not a bug. SquidServers is a desktop application, not a hosting service — the world is only online while your computer is powered on and the app is running. If you need persistent uptime, that's the case for paid hosting.

"It crashes or stutters with mods." Almost always memory or Java. Verify you're on Java 17+, and raise allocated RAM toward the 8GB recommendation for modded servers. Close other heavy applications while the server runs.

"Java version errors on startup." Let the app install the correct Java version rather than fixing it manually — it's built to handle this on first launch.

Quick decision guide

• Play in sessions, PC is usually on, want free: self-host with a desktop app and tunneling.
• Need 24/7 uptime or your hardware is weak: pay for hosting.
• Laggy over the tunnel and you can edit your router: port forward for better performance.

"No port forwarding" means your Minecraft server runs on your own computer, but instead of opening a router port, a tunneling service creates an outbound connection to a relay that players connect through. SquidServers does this with built-in tunneling from playit.gg, so you can host without touching router settings. The trade-off: your server is only online while your PC is on and the app is running, and SquidServers itself still recommends port forwarding when you want the best performance.

Why a local Minecraft server normally needs port forwarding

When you host on your own machine, the server listens on a port (25565 by default for Java Edition). Your router blocks incoming connections from the internet by default, and your computer only has a private address on your home network. Port forwarding tells the router: "send traffic on this port to this machine."

That works, but it requires:

• Access to your router's admin panel
• A stable local IP for your host machine
• Manual port and firewall rules
• Adjustments if your ISP uses carrier-grade NAT (where you may not be able to forward at all)

Tunneling skips all of that by reversing the direction of the connection.

How tunneling exposes a local server without router changes

Instead of waiting for players to reach you, the host machine opens an outbound connection to a relay server. Players connect to the relay's address, and the relay passes traffic back down that existing connection to your local server.

SquidServers includes built-in tunneling services provided by playit.gg, so this is handled inside the app rather than as a separate setup step. From your side, the practical result is:

• No router login, no port rules, no firewall changes
• Works behind firewalls, routers, and networks where you don't control the hardware
• Players get an address to join, and the relay handles the rest

Because the connection is outbound, it also works on networks where inbound port forwarding is blocked or unavailable.

The limits you should know before choosing this route

Tunneling removes the setup barrier, not the physics of running a server on your own PC.

Two points matter most:

1. No true 24/7 uptime. SquidServers is a desktop application, not a hosting service. Your server is online only when your computer is turned on and SquidServers is running. Tunneling doesn't change that — it only changes how players reach you.
2. Performance is usually better with port forwarding. SquidServers states that for the best performance, port forwarding is recommended when possible. Tunneling adds a relay hop, which can show up as extra latency.

When to use no-port-forwarding hosting, and when to forward instead

Use tunneling (the default in SquidServers) when:

• You can't or don't want to log into your router
• Your ISP uses CGNAT or your network blocks inbound ports
• You're hosting for friends and want it working in minutes
• You're on a shared, school, or work network you don't control

Forward ports when:

• You want the lowest possible latency for competitive or large-group play
• You control your router and are comfortable with the setup
• You're running a server that's meant to be reachable as reliably as possible while your PC is on

If you're unsure, start with tunneling. It gets you online immediately, and you can switch to port forwarding later if latency becomes a problem.

What SquidServers gives you alongside tunneling

The app is free with no monthly fees, and it handles the server setup for you. It supports:

• Java and Bedrock Edition, including crossplay between them via GeyserMC
• Modpacks from Modrinth, plus custom mod installs via CurseForge Server Packs
• Windows, macOS, and Linux, with a recommendation of at least 4GB RAM (8GB for modded servers) and Java 17 or higher — the app can help install the right Java version

One thing to plan around: because it's a desktop app, your world stays online only while you leave the app running. If you close it or shut down your PC, players get disconnected until you start it again.

Quick decision guide

• Want it working today with zero router changes? Use the built-in tunneling — no port forwarding needed.
• Care most about ping and stability for a regular group? Forward the port if your network allows it.
• Need the server up when your PC is off? Neither option covers that; you'd need an actual hosting service instead of self-hosting.

Use a desktop Minecraft server application if you want to host on your own computer for free and only need the server online while you're playing. Pay for hosting if you need the server running 24/7, want to support many players, or don't want to tie up your own machine. The deciding factor is almost always uptime: a desktop app runs only while your computer is on and the app is open, while paid hosting runs on a remote machine around the clock.

The core difference: your computer vs someone else's

A desktop server application turns your own PC into the host. You install it, it sets up and runs the server locally, and your friends connect over the internet. Paid hosting runs the same server software, but on a remote machine that stays powered on whether you're there or not.

That single difference drives everything else — cost, uptime, performance, and how much setup you deal with.

Side-by-side comparison

SquidServers, for example, is a free desktop application that includes built-in tunneling (provided by playit.gg) so you can skip port forwarding, and it automates server setup. It supports thousands of Modrinth modpacks plus custom CurseForge server packs, and runs on Windows, macOS, and Linux. Its own FAQ states plainly that it is not a hosting service — your server is online only when your computer is on and running the app.

When a desktop application is the better choice

• You play in bursts — a "two-week phase" with friends, a weekend session, a single modpack run.
• You don't want a recurring bill. Free with no monthly fees is the whole point.
• You want to avoid port forwarding. Built-in tunneling makes the server reachable behind most routers and firewalls.
• You want mods and modpacks without a provider's restrictions.
• You're okay with the server going offline when you shut down your PC.

When paid hosting is the better choice

• You need the world available 24/7 — for a persistent community, scheduled events, or players in different time zones.
• You expect many concurrent players and don't want your own connection or hardware to be the bottleneck.
• You don't want your gaming PC's resources consumed by hosting while you do other things.
• You'd rather not manage Java versions, server files, or updates yourself.

What to check before you decide

1. Uptime requirement. If players will log in when you're asleep or at work, self-hosting on a desktop app won't work.
2. Your hardware. SquidServers recommends at least 4GB of RAM (8GB for modded servers) and Java 17 or higher, and can help install the right Java version. Heavier modpacks need more.
3. Your connection. For best performance, SquidServers recommends port forwarding when possible, though tunneling works without it.
4. Edition and crossplay. If you need Bedrock or Java–Bedrock crossplay, confirm the app supports it — SquidServers supports Bedrock Dedicated Server and crossplay via GeyserMC.
5. Budget tolerance. Free desktop hosting vs. a monthly subscription is often the tiebreaker once uptime needs are clear.

The short version

Choose a desktop application like SquidServers when "free, no port forwarding, runs while I play" matches how you actually use a server. Choose paid hosting when "always online, many players, not my machine" matters more than cost. If your group only plays together in the same sessions, self-hosting wins on price; if the world needs to stay up without you, pay for hosting.

Self-hosting with a desktop app like SquidServers and paying a hosting provider solve the same problem in opposite ways. A paid host runs your world on someone else's machine around the clock, so the server stays online whether or not you're at your computer. A self-hosted desktop app runs the world on your own PC, so it's only reachable while your computer is on and the app is running. SquidServers is free and handles the setup and networking for you, but it is explicitly not a hosting service — that single fact drives most of the trade-offs below.

The core difference: uptime lives on your machine

If your friends play at unpredictable hours and you don't want to leave a computer running, a paid host removes that constraint. If you play in sessions — you start the server when you're online and shut it down after — self-hosting costs nothing and keeps the world on your own disk.

Where free hosted platforms fit

Free hosted platforms (the comparison on SquidServers' site names Aternos and Minehut) sit between the two. They're free but run on shared infrastructure, which is where the common limits come from:

• Time caps. The comparison lists Aternos with a "4 hour daily limit," while SquidServers is marked as having no monthly fees or hidden costs.
• Performance variance. Aternos is described as "laggy at times," and Minehut as using a "P2P connection" that can also lag.
• Mod support differs. SquidServers is listed as supporting mod-based hosting; Minehut is not.

The trade is straightforward: free platforms keep your server online without your PC, but you accept queues, session limits, or inconsistent performance. Self-hosting gives you full control and no time cap, but the server's uptime is tied to your machine.

Port forwarding vs built-in tunneling

This is the part most people get stuck on, so it's worth separating the two options clearly.

Built-in tunneling (what SquidServers does by default). The app includes tunneling provided by playit.gg, which makes your server reachable without touching your router. This works behind any firewall or router, which is why the site lists "no port forwarding" as a headline feature. The trade-off: traffic routes through the tunnel, so the site itself recommends port forwarding "for the best performance."

Port forwarding. You open a port on your router and point it at your PC. It's faster because connections go directly to you, but it requires router access and can fail behind CGNAT or restrictive networks.

Practical rule: start with the tunnel to get playing today, and switch to port forwarding later if you notice latency and your network allows it.

Mods, Java, and Bedrock crossplay

• Mods and modpacks: SquidServers supports thousands of modpacks from Modrinth and custom installs via CurseForge Server Packs. Free platforms vary — check each one if modded play is your main use case.
• Bedrock Edition: SquidServers supports Bedrock Dedicated Server and crossplay between Java and Bedrock using GeyserMC.
• Java version: Java 17 or higher is recommended, and the app will help install the correct version if needed.

System requirements and the real cost picture

SquidServers runs on Windows, macOS, and Linux. The site recommends at least 4GB of RAM, or 8GB for modded servers. Since the server shares your PC's resources, a heavy modpack competes with whatever else you're running.

On cost: the site states SquidServers is "completely free" with "no hidden fees," and the comparison marks it as having no monthly fees. Note that this is a self-hosted app, not a subscription service — but the site's pricing signals do reference "subscribe," so confirm current terms on the download page before relying on it. What you're definitely not paying for is a monthly server rental.

How to decide

• Choose self-hosting (SquidServers) if: you play in sessions, want zero monthly cost, need mod support and Java/Bedrock crossplay, and are fine with the server being offline when your PC is off.
• Choose a paid host if: you need the world online 24/7, want to play from anywhere without leaving a computer running, or your PC can't spare the RAM.
• Choose a free hosted platform if: you want 24/7-ish availability at no cost and can live with time limits or occasional lag.

The honest summary: self-hosting trades always-on uptime for zero cost and full control. If your group's schedule is predictable, that trade is usually worth it.

Desktop software is a program you install and run directly on your computer's operating system (Windows, macOS, or Linux), rather than inside a browser tab. You should choose it over a browser extension or web app when your task needs deeper system access, steadier performance, or offline capability — for example, real-time meeting transcription that captures audio from multiple apps. Browser extensions are lighter and install in seconds, but they live inside one browser and inherit its limits.

What "desktop software" actually means

A desktop app is installed on the machine and runs as its own process. It can:

• Read and write local files without a download/upload round trip
• Access system-level resources like the microphone, speakers, camera, and other running apps
• Keep working when the browser is closed or the network drops (depending on the app)
• Persist settings and data locally

This is different from a web app, which runs in a browser tab and depends on a live connection and browser permissions, and from a browser extension, which is a small add-on that modifies or extends one browser's behavior.

Desktop app vs. browser extension vs. web app

The practical takeaway: extensions and web apps are convenient and low-commitment; desktop apps trade a heavier install for capability and stability.

When a desktop app is the better choice

Pick desktop software when the task depends on one or more of these:

• Capturing audio from multiple sources at once — a meeting where you're on a call and taking notes. A desktop notetaker can tap system audio and the mic; a browser extension generally can't reach outside its tab.
• Real-time transcription and live summaries — Otter's Meeting Agent is described as supporting real-time transcription, live chat, automated summaries, insights, and action items. That kind of continuous processing benefits from a local process rather than a single browser tab.
• Long or resource-heavy sessions — recording and transcribing for an hour is more stable outside a tab you might accidentally close.
• Working across apps — if your workflow spans a video call app, a document, and a notes tool, a desktop app can sit across all of them.

Choose a browser extension instead when you only need to enhance one website (for example, adding a button to a specific web tool), want zero install friction, and don't need system-level access.

How to choose and install a desktop app safely

1. Confirm the task fits a desktop app. If you only need to tweak one website, an extension is lighter. If you need system audio, local files, or offline use, go desktop.
2. Check system requirements. Match the OS (Windows/macOS/Linux) and version. Download only from the vendor's official site — for Otter, that's otter.ai.
3. Review permissions before granting. A meeting/transcription app will ask for microphone (and possibly screen or system audio) access. Grant only what the task needs.
4. Install and sign in. Follow the vendor's installer. If the app requires an account, expect a login step.
5. Verify it works. Run a short test — record 30 seconds and confirm transcription or capture appears as expected.
6. Check update and pricing terms. Otter lists a pricing page at otter.ai/pricing; check it for current plan limits rather than assuming a free tier.

Troubleshooting common desktop software problems

• Install fails — confirm OS version meets requirements, free up disk space, and re-download from the official source (a corrupted installer is a common cause).
• App crashes on launch — update to the latest version, restart the machine, and check whether a security tool is blocking it.
• No audio captured — re-check microphone/system-audio permissions in OS settings, not just in the app.
• Sync or login issues — verify your network and credentials; if the app stores data locally, confirm it isn't blocked by a firewall.
• Extension works but desktop doesn't (or vice versa) — they use different permission models; a feature available in one may not exist in the other.

If your goal is AI meeting transcription with live summaries and action items, a desktop app is usually the more capable choice; if you just need a small tweak inside one website, a browser extension is the faster path.