Privacy architecture
How AnonVPS is built to keep your data small: access-key sign-in, optional contact, RAM-only plans, encrypted storage and an honest threat model.
Read more →Updated 2026-11-11 · Published by AnonVPS
How it works
The operating system image is loaded into memory at boot and the root filesystem lives in RAM. There is no local disk to write to, so nothing persists across a reboot or power-off.
Good uses
- Gateways and relays that should not leave state behind.
- Short-lived workloads: builds, scrapers, test environments.
- Sensitive tools where you want a clean slate every boot.
Trade-offs
- Everything must fit in RAM, including your data and the OS.
- Anything you want to keep must be stored elsewhere and loaded at boot.
- Configuration should be automated, so a reboot does not mean starting from scratch.
What it does not protect against
The host runs your server, so it controls the memory. RAM-only reduces what is left on hardware and what could be recovered from a disk. It does not stop a host that is able and willing to inspect a running instance. See privacy architecture for the threat model.
Getting started
- Pick a plan on the RAM-only page.
- Boot your chosen OS image.
- Pull configuration and secrets from a source you control on every boot, over an encrypted channel.
Sizing a RAM-only server
The filesystem and your applications share the same memory. A CIRRUS plan with 8 GB of RAM does not have 8 GB for your application: the operating system, the filesystem and every file you write use some of it. Measure what your workload needs, then leave headroom.
Rebuilding after a reboot
- Keep configuration in a git repository or a small bootstrap script.
- Pull data from external storage at boot, encrypted in transit.
- Test a full restart before you rely on the server.
FAQ
Common questions
Can I add storage to a RAM-only plan?
RAM-only plans have no local disk by design. Use external storage you control, or use a disk-backed plan.
What happens when a RAM-only server reboots?
Everything in memory is lost, including the filesystem. The server starts from its base image.
Is RAM-only more private?
It leaves less on disk, but the host still controls the hypervisor. See privacy architecture.
Can I keep data on a RAM-only plan?
Not locally. Store it elsewhere and load it at boot.
Keep reading
Related pages
Encrypt a VPS with LUKS and unlock it remotely over SSH
Step-by-step: full-disk encryption on a Debian or Ubuntu VPS with LUKS and dropbear in the initramfs for remote unlock.
Read more →Host your own
Host your own apps on a private VPS: what size to choose for common self-hosted services, backups, updates and where to start.
Read more →