Skip to content

Servers

Every server you run, in one place.

Install the agent on any Linux VPS, bare-metal box or Raspberry Pi and it shows up in your workspace within seconds. See its health, group it with labels and manage the whole fleet without SSH-ing into each machine.

Start for free Explore the live demo

Free for up to three servers · No credit card required

A fleet table listing six servers across four regions with their operating system, role label, CPU and memory use, and status. One server in Singapore is marked degraded.

Connect

One line, and it's part of your fleet.

The install command carries a one-time token, so the server joins the right workspace and nobody copies keys around.

  1. 1

    Copy the command

    Servers → Connect gives you the command with a fresh token. Add labels now or later.

  2. 2

    Run it on the server

    The agent installs as a systemd service and registers. It takes about ten seconds.

  3. 3

    Target it by label

    Deploys, jobs and alerts that point at role=api pick the new server up automatically.

root@fra-prod-01 
$ curl -fsSL https://get.fwoop.dev | sh -s -- --token $FWOOP_TOKEN --labels role=api,region=eu
✓ Installed fwoop-agent 2.3.1 (linux/amd64)
✓ Registered as fra-prod-01 in workspace acme
✓ Connected to the control plane over TLS 1.3
$ fwoop agent status
connected · 0 inbound ports · labels: role=api, region=eu

Compatibility

If it runs Linux, it runs Fwoop.

Mix providers, regions and architectures in one workspace. The agent doesn't care where a machine lives.

Providers
Hetzner, DigitalOcean, AWS, Google Cloud, OVHcloud, Scaleway, Vultr, Akamai, or your own rack.
Operating systems
Ubuntu 20.04+, Debian 11+, RHEL, Rocky and Alma 8+, Fedora, Amazon Linux 2023 and Raspberry Pi OS (64-bit).
Architectures
amd64 and arm64, from a 1 GB VPS to a 128-core box.
Network
Outbound HTTPS on port 443. Nothing inbound, and it works behind NAT, proxies and home routers.
Footprint
About 30 MB of memory and under 1% CPU when idle. Docker Engine 24+ for services.

The agent

What it does, and what it never will.

It does

  • Runs as its own fwoop system user
  • Starts, stops and updates the containers you deploy
  • Runs the jobs and backups you schedule
  • Reports health and metrics every 10 seconds
  • Updates itself, and rolls back if an update fails

It never

  • Opens a port or listens for connections
  • Acts without an instruction from your workspace
  • Sends your logs or application data to Fwoop
  • Writes your secrets to disk
  • Leaves anything running after you uninstall it

How Fwoop handles security

Questions about servers

Do I need to open any ports?

No. The agent only makes outbound HTTPS connections to the control plane, so your firewall can stay closed to inbound traffic.

What can the agent do on my server?

It runs as its own fwoop system user with access to Docker for your services. It only acts on instructions from your workspace, and every action lands in the audit log.

Can I connect servers behind NAT or a corporate proxy?

Yes. As long as the server can reach the control plane over HTTPS, it works behind NAT, a proxy or a home router.

How do I remove a server?

Disconnect it in the dashboard or run fwoop agent uninstall on the machine. Your containers keep running; Fwoop just stops managing them.

Bring your first server online in five minutes.

Start free with three servers. No credit card, no sales call, and your workloads stay on machines you own.

Start for free Book a demo