# A Server is like a houseplant, except the houseplant doesn't have a database

> Independent workspaces need care. A practical guide for people who have already killed one succulent.

Source: https://llll.gg/blog/servers-not-plants

Congratulations on your new Server! It is yours. It has a name, a purpose and a small collection of people who will soon ask why they can't upload a file.

Unlike a houseplant, a Server does not need sunlight. It does need updates, storage, credentials and a backup that actually works. Also unlike a houseplant, putting it in a bigger pot will not solve a permissions problem.

## Watering schedule

An L4 Server owns the Accounts, content and settings of its community. An operator can use a supported Cloudflare or self-hosting path, but each path comes with infrastructure to maintain. Providers may charge for resources; running your own software does not make their bills disappear through the power of optimism.

Then there are backups. A backup is a recovery copy, not a second Server secretly working the night shift, and it only counts once you have restored it somewhere safe ([here's how to think about it](/blog/backups)). “I clicked Backup once” is not a recovery plan, just as “I bought a watering can” is not gardening.

## Ask for help before the leaves turn brown

You don't have to configure every optional capability on the first day. Start with the community journey: owner setup, invitation, conversation and a shared file. Add things like Mail or model providers when you need them and can verify their setup.

Treat ownership as a routine, not an emergency. And if the Server is doing well, please resist the urge to put it near a window.