Managed Nextcloud Hosting: Your Files, Run for You (2026)

I am Manoj. I lead ERPNext, Frappe and open-source deployments at MithTech, a team of Frappe specialists in Bengaluru, and Nextcloud is one of the open-source tools we set up for clients. The install is the easy part now. Honest take: a Nextcloud that nobody upgrades or restores is fine for a while, and then it is a problem all at once.

What does managed Nextcloud hosting cover?

It covers the work between the install and the files: the server, the stack around Nextcloud, the apps, the upgrades and the backups.

Most Nextcloud servers today are one of two kinds. An All-in-One (AIO) install runs Nextcloud, the database, the cache and the backup tool as containers managed by one master container. A plain install puts Nextcloud on a web server with PHP, a database and usually Redis, set up by hand. Nextcloud's backup guide names MariaDB as the recommended database engine for that kind of install. Our self-hosting guide walks through the AIO setup step by step.

Either way, someone has to own these jobs:

• The server and its stack. The operating system, Docker or the web server, PHP, the database and the cache.
• The apps. Calendar, Contacts, office editing and the rest, each of which has to support the next Nextcloud version before you move.
• Upgrades. Point releases, then each major version in turn.
• Backups. Taken on a schedule, copied off the server, and restored to prove they work.
• The admin login. Who holds it, and who else has one.

A managed host takes these on under a written scope; doing it yourself means a named person does them.

Why do Nextcloud upgrades and restores need an owner?

Because both have rules that punish a missed step. Nextcloud's admin manual says you cannot skip major releases. Before you move to the next major version, you first apply the latest point release of the one you run. The manual's own example runs 18.0.5, then 18.0.11, then 19.0.5, then 20.0.2. It also says to take a fresh backup before every upgrade.

On AIO, the master container does the upgrade, and the project says it "values stability over new features". It waits for at least the first patch release of a new major version, and for the important apps to support it, before it moves. For Docker, snap or package installs from elsewhere, the manual points you to the update instructions of whoever built them.

A restore has its own rules, and they start with the backup. On a manual install, Nextcloud's backup guide runs in this order:

1. Turn on maintenance mode, which stops new logins so the copy stays consistent.
2. Copy the config, data and theme folders to a location outside the Nextcloud install.
3. Dump the database with your engine's own tool.
4. Turn maintenance mode off.

The restore guide is blunt: "You must have the database, data directory, and configuration files." You copy the folders back, delete the existing database tables, import the dump, then fix any mismatch:

• If the backup is older than what the desktop clients hold, run maintenance:data-fingerprint so the clients recover as much as they can.
• If the database is newer than the data folder, run files:scan to update the database.

On AIO, the backup runs through BorgBackup, and daily backups can be switched on from the AIO interface. The two kinds of install differ like this:

AIO's own warning is that you cannot restore without that password. None of this is hard. It just has to be done every time, by someone whose job it is.

Where do the files live, and can they stay in India?

On whichever server you choose, in the region you choose. That is the point of Nextcloud over a rented drive: the files sit where you put them.

If you run it yourself, you pick the cloud account and the region. With a hosted account from a provider, the region is wherever that provider runs; check its page before you sign up. With a managed setup, the server's region is picked with you, and an Indian region is the usual choice for Indian companies. Backups go to a second location you approve. If a law or a client contract says where data must sit, say so at the start, so the server and the backup copy are set up that way from day one.

On any path, ask where the backup copy goes as well as the server.

Self-hosted, a Nextcloud provider or run for you: how do they compare?

All three keep you on Nextcloud, so moving between them later is a backup and a restore, not a migration. The difference is who does the work.

Nextcloud lists hosting providers on its own providers page. For private users and small businesses, the Simple Signup providers offer hosted accounts. For larger organisations, the same page lists providers offering fully managed hosting, help with self-hosting, or both. Nextcloud Enterprise is a subscription for organisations that want support delivered by Nextcloud's own engineers, a named account manager and long-term support for stable releases. Prices are on each provider's own page and on the Enterprise page.

For a small team that just needs shared files, a provider account is often the simplest path, and that is a fair choice. Running it yourself is cheapest in money and dearest in hours. A managed server sits in between: your own server, without your own sysadmin. The same three-way choice for ERPNext is in who runs ERPNext after go-live.

What do you keep if you leave?

Everything that matters, if it was set up right: the files, the database, the config and the admin login.

How you take them depends on where the server runs. If it sits in your own cloud account, nothing moves: the server is already yours and keeps running. If it sits on the host's servers, ask in advance for a full backup, the code and the settings, restored with you once on the server you choose. On a provider account, read the provider's export terms before you upload the first file.

Because every path runs the same software, the way out is the restore you should already be testing: the config, the data and the database together, or an AIO archive with its password.

Should you run Nextcloud yourself, or have it run for you?

Run it yourself if someone on your team will own the upgrades and test a restore; have it run for you if nobody will, and the files are ones you cannot lose. If you only need hosted storage and no server of your own, a provider account is simpler than either.

Under managed hosting we run Nextcloud on one named server, in your cloud account or ours, not a shared pool: nightly backups copied off the server, one restored on a schedule, every upgrade tried on a copy first, and the master login stays yours. If you leave, a server in your account is already yours; on ours you get a full backup, the code and the settings. It is a monthly fee for running it plus the server, quoted in writing after a call. The self-hosting cost comparator sets that against running it yourself.

Frequently asked questions

For a wider look at what Nextcloud replaces, see the open-source Dropbox alternative guide and, for notes and wikis, the open-source Notion alternatives.