# A self-hosted CMS you can run from one file | Sophia Stack X

Source: https://sophiastack.sophiaxt.com/self-hosted-cms

# A self-hosted CMS you can run from one file

# A self-hosted CMS you can run from one file

Self-hosted means you run the software on a machine you control, and your content stays there. Sophia Stack X is built for that. It sends no content or data to SOPHIA XT. It contacts the download site only when you ask it to check for an update.

This page covers what you need, how installing and updating work, what you are responsible for, and how to leave if you want to.

## What you need

On your own computer: Windows 10 or 11 (64-bit), a 64-bit Linux machine (Intel, AMD or ARM), or a Mac with Apple silicon. Download the file, open it, and fill in one setup page. It makes a `sophia-data` folder beside itself and opens the setup page in your browser.

On a server: a 64-bit Linux server with systemd, root access, and a domain name pointing at it. One command does the rest:

```
curl -fsSL https://sophiastack.sophiaxt.com/download/install.sh | sudo sh -s -- --domain example.com --tls-email you@example.com
```

The installer downloads the program and checks it against the signed release list. It then installs it under its own account in a locked-down service that listens only on `127.0.0.1`, sets up nginx or Caddy for your domain, gets an HTTPS certificate when you give it an email, and prints a one-time setup link. Until someone uses that link, the setup page turns everyone away, so a stranger who finds your address first cannot become the owner.

Prefer to read the script before running it? The [Verify a download](https://sophiastack.sophiaxt.com/verify) page shows how to fetch it, check its signature, and run it only if it matches.

## There is no database server and no runtime

The program is the web server, and the database is one SQLite file. You do not install PHP, Node or MySQL, so there are none of them to patch. The live site is plain files, with the admin served by the same program.

## Updates you can check

Updating on a server is one command, run as root:

```
sudo /opt/sophia/current/sophia update --latest
```

It fetches the list of the newest files and checks that the list is signed with the SOPHIA XT release key built into the program. Then it downloads the new version and checks its SHA-256 against the signed list. If either check fails, nothing changes. If the update works, it stops the service, copies the database, switches versions, and waits for the new one to answer. If it does not answer within 30 seconds, the previous version and the database copy come back by themselves. Three versions and three database copies are kept.

## Backups and rollback

**Back up now** in the admin, or `sophia backup`, writes one zip with a consistent copy of the database, every site's pictures, installed extensions, trusted keys and settings. Fourteen are kept by default. To restore, `sophia restore <file> --into <folder>`, then start the program with `--data <folder>`.

For content mistakes, publishing makes numbered releases. The last ten are kept and any of them goes live again in one click. If you let an AI agent work on the site, it can publish and roll back through the same releases.

## What you are responsible for

Self-hosting is a trade. We can say plainly what falls on you:

*   **The server.** Operating system updates, firewall, disk space and the domain's DNS.
*   **Backups kept off the machine.**`sophia backup` makes the zip, but copying it somewhere else is your job.
*   **Your sign-ins.** Turn on two-step sign-in. **This install > Security** lists what still needs doing before a site is public.
*   **Email delivery.** A site that sends mail needs a mail account. Setup has presets for common providers.
*   **Updates.** Nothing updates itself without you running the command or republishing on your schedule.

SOPHIA XT does not host your site or run it for you. The [changelog](https://sophiastack.sophiaxt.com/changelog) states the support policy.

## Security by design

The site visitors get is published files by default. On a server, the program runs as its own user, can write only its data folder, and listens only on `127.0.0.1` behind your web server. Passwords are stored with Argon2, sign-in attempts are slowed down, and every change by a person or an AI agent goes in the audit log. Extensions are sandboxed and get only the permissions they declare. [Security and backups](https://sophiastack.sophiaxt.com/docs/security) has the full list.

## Leaving

You can walk away. Your sites are published as plain HTML files, and every page has a Markdown copy. Any web server can serve them, and your content sits in one SQLite database file you control. The program itself is free to use for any site but not open source, so the admin and updates stop if you stop using it. The [license](https://sophiastack.sophiaxt.com/license) explains the terms.

## The cost

Sophia Stack X is free for any site, including paid work for clients, on any number of computers and servers. You pay for the server and domain you choose. Compare it with WordPress, Joomla and Ghost on the [comparison page](https://sophiastack.sophiaxt.com/compare).

## Next step

Pick one: [install it](https://sophiastack.sophiaxt.com/install), [try the live demo](https://demo.sophiastack.sophiaxt.com/demo/start) without installing, or read how [deploying from your computer](https://sophiastack.sophiaxt.com/docs/deploy) works.
