ServerBox

Mobile-first server management, honestly reviewed. No marketing fluff, just what you get when you manage Linux boxes from your pocket.

TL;DR

• What it is: A Flutter-based, cross-platform server management app that lets you monitor server stats, run SSH sessions, browse files over SFTP, and manage Docker containers — from your phone, tablet, or desktop [README].
• Who it’s for: Homelab runners, indie hackers, and small-team sysadmins who want a native mobile interface for their Linux servers instead of opening a terminal or pointing a browser at a web dashboard.
• Cost: Free. No subscription, no cloud relay, no usage tiers. AGPL-3.0 licensed, source on GitHub [README].
• Key strength: Real native app (not a web wrapper) available on iOS, Android, macOS, Linux, Windows, and watchOS — all from one codebase. SSH, SFTP, Docker, and real-time system charts in a single install [website].
• Key weakness: No significant independent reviews exist. It’s a solo-developer-maintained project with a relatively small community. The AGPL license means you can’t embed it in closed-source products without consequence. Data: no third-party benchmarks or long-term reliability reports are publicly available.

---

What is ServerBox

ServerBox is a Flutter application that connects to your Linux (and some Windows/Unix) servers over SSH and surfaces a monitoring dashboard plus a toolbox of admin utilities. The pitch is on the homepage: “Manage your Linux servers from anywhere” [website].

What you actually get is a native client that wraps several distinct tools into one UI:

• Real-time system metrics (CPU, RAM, disk, network, GPU, temperature sensors, S.M.A.R.T. disk health)
• A full SSH terminal with multi-tab support and virtual keyboard for mobile
• An SFTP file browser with local file management
• Docker container management (start, stop, inspect)
• Process manager and systemd service control

The project is built on top of dartssh2 and xterm.dart — both open-source libraries — which explains how a solo Flutter developer delivered a usable SSH terminal on five platforms without writing an SSH stack from scratch [README].

As of this review the project has 7,673 GitHub stars, ships on App Store, Google Play, F-Droid, and GitHub Releases, and supports 12 languages (with German, Traditional Chinese, Indonesian, French, Dutch, Turkish, and Ukrainian contributed by community translators, and Spanish, Russian, Portuguese, and Japanese generated by GPT) [README].

---

Why people choose it

No major independent review sites have published long-form coverage of ServerBox. The following is based on the GitHub project, the official website, and the broader self-hosted community context.

The appeal is legible from the feature list and the star count: there is no obvious free, native, cross-platform alternative that does all of SSH + SFTP + system monitoring + Docker management in one app.

The mobile-first gap. The standard approach to server monitoring is a web dashboard — Netdata, Grafana, Cockpit — that you open in a browser. That works, but it requires you to either expose a web port to the internet or set up a VPN first. ServerBox tunnels everything over the SSH connection you already have, which is simpler to secure and requires no additional server-side setup beyond having SSH running. As XDA Developers noted in a wider piece on home network monitoring, most people want visibility without engineering-degree overhead [6]. A native SSH-based client with a charting layer is a reasonable answer.

The iOS problem. On iOS, options for SSH + SFTP + monitoring are dominated by paid apps. Termius starts free but gates sync and SFTP behind a $9.99/month subscription. Blink Shell is $20/year. Royal TSX is $40 one-time on macOS but has no mobile counterpart. ServerBox is free on App Store, which makes it the default recommendation in homelab forums for anyone who wants an iPhone-based server dashboard without paying a recurring fee.

watchOS. The README lists a watchOS app as a platform-specific feature. A server dashboard on your wrist is a specific and hard-to-replicate use case — relevant primarily for homelabbers who want a glance-able view of whether their NAS is doing something alarming.

Offline-capable monitoring with ServerBoxMonitor. The base app only displays data while open and connected. To get push notifications and home screen widgets (showing live CPU/RAM without opening the app), you install a companion daemon called ServerBoxMonitor on the server side. This is a deliberate architectural choice: the push path is a separate, lightweight process, while the main app focuses on interactive sessions [README].

---

Features

Based on the README and website:

System monitoring:

• CPU usage (per-core or aggregate), load averages
• Memory and swap usage
• Disk I/O and filesystem usage
• Network throughput (per interface)
• GPU stats (where available)
• Temperature sensors
• S.M.A.R.T. disk health data

SSH Terminal:

• Full terminal emulation via xterm.dart
• Multi-tab support (multiple connections open simultaneously)
• Virtual keyboard layout optimized for mobile (common shell keys accessible without switching keyboards)
• Biometric authentication for stored connection credentials

SFTP:

• Browse, upload, download, rename, delete files
• Local file browser for selecting files to upload
• Works alongside the SSH terminal — same connection, no separate auth

Docker & Process management:

• Start, stop, restart, inspect Docker containers
• View and manage running processes
• Systemd service control

Platform-specific extras:

• iOS/Android: Biometric auth, push notifications (with ServerBoxMonitor), home screen widgets
• iOS: App Store distribution; no sideloading required
• watchOS: Glanceable server stats widget
• Linux/Windows/macOS: Desktop-class layout, same feature set

What’s missing:

• No built-in VPN or tunnel management — you need your server reachable via SSH from outside (direct, Tailscale, WireGuard, etc.)
• No alerting/threshold configuration inside the app (push alerts require the separate ServerBoxMonitor daemon)
• No web-based access — it’s purely a native client, not a self-hosted web app
• No team/multi-user features — connection configs are local to the device

---

Pricing: SaaS vs self-hosted math

ServerBox has no SaaS version. It is free software, period.

ServerBox: $0. Download from App Store, F-Droid, or GitHub [README].

Competing paid options for context:

Tool	Model	Cost
Termius	Freemium SaaS	Free (limited) / $9.99/mo for sync + SFTP
Blink Shell	One-time + subscription	$19.99 setup + optional plan
Royal TSX	One-time (macOS only)	~$40 USD
Screens (VNC)	One-time	~$30

A non-technical founder running 3–5 servers who currently pays $9.99/month for Termius saves ~$120/year by switching to ServerBox, assuming the feature set covers their needs. The practical constraint is that Termius has cloud sync across devices and a more polished onboarding experience. ServerBox connection configs are stored locally per device, with no built-in cloud sync.

Pricing data for third-party competitors cited above is based on public app store listings and may have changed.

---

Deployment reality check

“Deployment” for ServerBox means installing the app. There’s nothing to run on your servers beyond standard SSH (which you presumably already have). The watchOS app and desktop versions are distributed via the same channels.

What you need on the server side:

• SSH daemon running and accessible (port 22 or custom)
• A user account with appropriate permissions
• If you want Docker management: Docker installed, and the SSH user needs access to the Docker socket (either root or the docker group)
• If you want push notifications and widgets: install ServerBoxMonitor and configure it per the wiki

What you need on the client:

• iOS 15+, Android 7+, macOS, Linux, or Windows
• An SSH connection to your server (direct or through a tunnel — the app doesn’t manage the network path for you)

What can go sideways:

The README is candid about issue reporting: paste the entire log, confirm the bug is caused by the app itself, and avoid subjective feedback like “I think another UI looks better.” This is the tone of a solo-developer project where the maintainer has limited bandwidth — reasonable, but it means support response time is unpredictable [README].

There is no documented REST API for the app itself (it’s a client, not a server). There is no enterprise support tier. If the project stalls or the maintainer moves on, you’re on an AGPL codebase with no commercial backer.

The F-Droid distribution channel means the Android version is available without Google Play — relevant if you’re running a de-Googled device [README].

Biometric auth is listed as a feature for stored credentials. This is significant on mobile: you’re storing SSH credentials (passwords or keys) in the app, and biometric lock is the protection layer. The README doesn’t detail the credential storage implementation (secure enclave vs. app-level encryption), which is worth investigating before storing private keys to production servers.

---

Pros and cons

Pros

• Actually free. No subscriptions, no “pro” tier for basic features, no telemetry-funded free tier. AGPL-3.0 source on GitHub [README].
• True cross-platform. One app covers iOS, Android, macOS, Linux, Windows, and watchOS — not a web wrapper, a native Flutter app with platform-appropriate UI adaptations [README][website].
• SSH-native security model. All communication goes over SSH. No cloud relay, no agent, no vendor getting between you and your server. If you trust your SSH setup, you trust this [README].
• No server-side install required for the core monitoring and terminal features. Drop it in, connect, done.
• watchOS support is a unique differentiator — genuinely hard to find elsewhere.
• F-Droid available for Android without Google Play dependency [README].
• Docker + process management in the same interface as the terminal reduces context-switching for Docker-heavy setups.
• Community translations in 8+ languages, maintained by volunteers [README].

Cons

• No independent reviews or benchmarks. The project’s real-world reliability at scale (many servers, high-frequency monitoring) is unverifiable from public sources. Data: no third-party reliability reports found.
• Solo-developer project. One primary maintainer. Bus factor: 1. The AGPL license protects you from the code disappearing, but active maintenance could stall.
• No cloud sync for connection configs. If you use the app on three devices, you configure each separately. Termius and similar tools solve this; ServerBox does not.
• AGPL license. Copyleft, meaning you can’t embed ServerBox in a commercial product without open-sourcing the whole thing. Not a problem for personal or internal use, but worth noting for anyone building on top of it.
• No alerting configuration inside the app. Threshold alerts require the separate ServerBoxMonitor daemon — an extra setup step that the core app doesn’t simplify.
• Credential storage transparency gap. The README doesn’t document how SSH credentials are stored. Before putting private keys to production systems in this app, verify the implementation.
• Community is not massive. 7,673 stars is respectable but small compared to projects like Termius or Blink. The Discord, Telegram, and QQ channels exist but community-sourced help may be sparse for edge cases.

---

Who should use this / who shouldn’t

Use ServerBox if:

• You manage 1–10 Linux servers for personal projects or a small team, and want a single app for SSH, SFTP, monitoring, and Docker across all your devices.
• You’re an iOS user looking for a free alternative to Termius or Blink Shell that doesn’t require a monthly subscription for SFTP access.
• You have a watchOS device and want glanceable server stats on your wrist.
• You’re running a de-Googled Android phone and want an F-Droid-available option.
• You’re comfortable with SSH being your security perimeter and don’t want a web-based dashboard exposing another port.

Skip it (consider Termius) if:

• You work across multiple devices and need connection configs to sync automatically. Termius handles this; ServerBox doesn’t.
• You need a team-shared server list with access control. ServerBox has no multi-user or team features.
• You need enterprise support with SLAs.

Skip it (consider Cockpit) if:

• You want a web-based dashboard accessible in a browser without installing anything on client devices. Cockpit runs on the server and exposes a UI at a port — easier for non-technical collaborators who aren’t comfortable with SSH app setup.

Skip it (consider Portainer) if:

• Docker management is 80% of what you do. Portainer is purpose-built for it, has a richer UI, and supports Swarm and Kubernetes.

Skip it (consider Netdata or Grafana) if:

• You need historical metrics, alerting, and dashboards accessible to multiple team members simultaneously. ServerBox is a personal client, not a monitoring platform.

---

Alternatives worth considering

• Termius — the most polished cross-platform SSH client. Free tier limited; SFTP and sync require subscription. Closed source.
• Blink Shell — iOS/macOS, developer-focused, strong terminal emulation. Paid.
• Cockpit — web-based server management dashboard. Runs on the server, accessible in browser. Free, open-source, actively maintained by Red Hat.
• Portainer — Docker-focused. Web UI, free community edition, team features on paid Business tier.
• Netdata — real-time monitoring dashboard with historical data, alerting, and cloud integration. Free open-source; cloud features paid.
• Royal TSX (macOS) — professional-grade connection manager. Supports SSH, RDP, VNC, and more. One-time purchase, macOS only.

For a non-technical founder who mainly needs to check if servers are healthy from a phone, the realistic shortlist is ServerBox vs Termius. Pick ServerBox if cost matters and you can tolerate per-device config. Pick Termius if sync and polish matter more than the subscription fee.

---

Bottom line

ServerBox fills a specific gap: a free, native, cross-platform SSH client with a monitoring layer, for people who don’t want to pay Termius prices and don’t want to expose a web dashboard port. It does SSH, SFTP, Docker management, and real-time system charts in one app, on every platform including watchOS, with no server-side agent required. The trade-offs are what you’d expect from a solo-maintained AGPL project: no cloud sync, no team features, no enterprise support, and limited external validation of long-term reliability. For a homelab runner or indie founder who manages a handful of servers from their phone, it’s the obvious free choice. For teams, regulated environments, or anyone storing credentials to critical production systems, verify the security implementation before committing.

If setup or SSH configuration is the blocker, that’s the kind of infrastructure work upready.dev handles for clients — one-time, no ongoing fees.

---

Sources

1. XDA Developers — “3 ways to monitor your home network that don’t require expensive software” (Dec 24, 2025). https://www.xda-developers.com/ways-to-monitor-home-network-that-dont-require-expensive-software/
2. selfh.st — “This Week in Self-Hosted (25 October 2024)”. https://selfh.st/weekly/2024-10-25/

Primary sources:

• GitHub repository and README: https://github.com/lollipopkit/flutter_server_box (7,673 stars, AGPL-3.0)
• Official website: https://serverbox.lpkt.cn
• App Store listing: https://apps.apple.com/app/id1586449703
• F-Droid listing: https://f-droid.org/packages/tech.lolli.toolbox
• ServerBoxMonitor companion: https://github.com/lollipopkit/server_box_monitor