Public services on a small server
Hosted the company’s public services on a single‑core 512 MB host —
a git forge, a web server for seven domains, Tor, two
alternative‑protocol servers and intrusion banning — treating 464 MB
of usable memory as the design constraint; backup automation is a
separate implementation.
September 2026

Situation. The company's production host is a single‑core cloud
instance with 512 MB of memory, of which about 464 MB is usable, and
10 GB of disk. Everything the business runs in public sits on it:
the web server terminating TLS for seven domains, the git forge, a
Tor onion service, a Gemini server, a Gopher server, intrusion
banning and separately implemented backup automation. The usual
reaction to that list is to buy a larger box.

Task. The constraint had to be treated as an architectural input
rather than a problem to spend money on, because the honest question
was not whether a bigger machine would work but whether the design
needed one.

Action. Memory became the argument that settled decisions. There is
no monitoring agent, no metrics pipeline and no dashboard —
reporting is a pull, seven commands that read the host and render
Markdown, changing nothing and running only when asked. The
supervisor is systemd rather than a second process manager layered
on top of it, and the container plane is Quadlet units under the
same supervisor rather than a daemon with its own. Web‑panel
platforms were ruled out at the design stage for the same reason.
When the question came up of whether the host could carry an onion
service, the answer came from a day of measured samples rather than
an opinion: available memory never fell below about 310 MB of 464,
swap sat at 2.6 per cent and the processor was 99.7 per cent idle.

Result. The recorded public‑service setup ran on a machine that cost
less per month than a lunch, and the design is better for the
discipline rather than merely cheaper. What it cost is headroom for
anything careless — mail is deliberately not on this box at all — it
is written as an install scaffold awaiting a host of its own,
because a mail server needs headroom this machine has already spent,
and that is written down rather than discovered later.

Categories:
1Platform Architecture	/categories/platform-architecture/	platform.engineer.company	70
1Solution Architecture	/categories/solution-architecture/	platform.engineer.company	70
1Infrastructure	/categories/infrastructure/	platform.engineer.company	70
1Reliability & Backups	/categories/reliability/	platform.engineer.company	70
1Linux & Servers	/categories/linux/	platform.engineer.company	70
1Performance Tuning	/categories/performance/	platform.engineer.company	70
1System Administration	/categories/system-administration/	platform.engineer.company	70

Services:
1Platform & Solution Architecture	/services/platform-architecture/	platform.engineer.company	70
1Cloud Infrastructure & Migration	/services/cloud-infrastructure/	platform.engineer.company	70
1Infrastructure as Code	/services/infrastructure-as-code/	platform.engineer.company	70
1System Administration	/services/system-administration/	platform.engineer.company	70

hThis page on the web	URL:https://platform.engineer.company/portfolio/a-whole-company-on-one-small-server/	platform.engineer.company	70
