Old laptop as a home server
A Dell laptop from 2013 sat unused in a cupboard. Now it runs Ubuntu Server day and night, with the Art Store for the TV, the daily Gmail triage and Claude Code on it. This is how it went, step by step.
- Laptop from
- 2013
- Memory
- 16 GB
- Time taken
- 2 weeks
- Ports open in router
- 0
One laptop, three jobs
The laptop sits with its lid closed on a network cable. It runs the Art Store in Docker, the Gmail triage every morning and Claude Code, which I use to work on the server from my phone or laptop. When I am out, I reach it through Tailscale. The settings live in their own GitHub repo.
From dusty laptop to server in ten steps
Claude wrote the step-by-step plans, the scripts and the configuration, and worked out why things went wrong. I chose the hardware and the security rules, and typed every command that needed admin rights (sudo) myself.
-
1
Check the specs first
ClaudeA Dell Inspiron 7537 with an Intel i7-4500U (2 cores, 4 threads), 16 GB of memory and a 256 GB SSD. That is well above what Ubuntu Server needs, and enough for a handful of Docker containers. A low-power mini PC or a Raspberry Pi 5 was the alternative, but the laptop was already here.
-
2
Install Ubuntu Server
UbuntuUbuntu Server 26.04 LTS put on a USB stick with Rufus, the whole SSD wiped and installed with LVM and OpenSSH, without extra snaps. The installer used only 100 GB of the disk; later one command added the rest. Then Docker and Docker Compose from the official source.
-
3
A GitHub repo for the configuration
GitHubEvery settings file on the server is in a private repo, with a note on where it belongs. The Restore section in the README rebuilds a fresh server the same way with a handful of commands. Claude proposes changes as a pull request; I merge them. Passwords and keys are never in it.
-
4
Run the updates
UbuntuFirst everything was brought up to date. After that, Ubuntu installs security updates by itself every day. Regular updates and Docker I do by hand, and automatic restarts are off: I choose when the server is briefly away.
-
5
A fixed IP address
RouterThe server and the TV each got a fixed reservation in the router. That way everything finds each other again after a restart, without setting anything on the server itself.
-
6
Keep running with the lid closed
ClaudeUbuntu now ignores the lid, and the screen turns off after a minute. Surprise: with the lid closed this Dell switches the wifi off hard, and that cannot be prevented. Claude found the cause; the fix was a network cable to the router. It is also faster (1 Gbps) and more stable. Wifi stays only as a backup.
-
7
Battery out, for fire safety
SafetyA thirteen-year-old battery on the charger day and night, with no charge limit in the BIOS: I did not want that. The battery is out and handed in at a collection point. Then I checked that the processor does not slow down without a battery: still 2.7 GHz under load. Downside: in a power cut the server goes off at once. Ubuntu recovers from that and everything starts again by itself.
-
8
Claude Code on the server
Claude CodeClaude Code runs on the server itself and starts by itself after a restart, with Remote Control. So I work directly on the server from the Claude app on my phone or laptop, instead of retyping commands. Without a password Claude may only install updates and read a few things; everything else with
sudoI do myself. -
9
Tailscale, for the Art Store on the go
TailscaleThe Art Store has no login of its own, so it must never be open to the internet. Tailscale makes a private network between the server and my phone. On the go I open the Art Store by the server's name, from an icon on my home screen. Nothing is open in the router.
-
10
Gmail triage moved over
JevClaudeThe Gmail triage ran as a scheduled task on my Windows laptop, so only when that was on. Now a timer on the server starts it every morning at 07:30. The task on the laptop is paused.
House rules for a server at home
- Never open ports in the router. From outside only through Tailscale.
- The firewall only allows logging in (SSH) from the home network.
- Logging in only works with an SSH key: no password, no root. A new device gets its own key.
- Claude gets limited admin rights. Anything beyond that, I type myself.
- Every change to the server goes into the GitHub repo, through a pull request that I merge myself.
- Passwords, tokens and keys are never in git.
What is in it
| Part | Choice |
|---|---|
| Hardware | Dell Inspiron 7537 (2013), Intel i7-4500U, 16 GB, 256 GB SSD, power adapter only |
| System | Ubuntu Server 26.04 LTS, LVM, automatic security updates |
| Network | Cable (1 Gbps) with a fixed reservation in the router, wifi as backup |
| Access | SSH with a key from the home network, Tailscale on the go |
| Apps | Docker and Docker Compose (Art Store) |
| Jobs | systemd timers (Gmail triage daily at 07:30) |
| Management | Claude Code with Remote Control, configuration in a private GitHub repo |
Four things I did not expect
- The installer took only 100 GB. The rest of the SSD sat unused. One command later the server had the whole disk.
- Lid closed means wifi off. That is built into this Dell and cannot be turned off. Without a cable the server is then unreachable.
- The cable goes into the router, not the modem. In the provider's modem the server got no address on the home network.
- 1.80 GHz in the BIOS is not a problem. That is the base speed of this processor. What counts is the speed under load, and that is 2.7 GHz, even without a battery.
What you need
An old laptop with at least 4 GB of memory and an SSD, an 8 GB USB stick, a network cable and a Claude subscription. Count on an afternoon for the installation and a few evenings to set everything up properly. In doubt about your battery? Take it out.
Updated 11 November 2026.