What does managed application hosting mean?

By Noiz / 19th October 2026 | 6 min

Managed application hosting means the provider runs the application for you, not only the server it sits on. It updates the software, backs it up before every change, checks that it still works afterwards and recovers it when something breaks. You keep the parts that are about your business: who has an account, what goes into it and how it is set up. This article explains where that line sits, how it differs from ordinary hosting, and when it is worth paying for.

Three layers, three kinds of service

Every application your business uses online sits on three layers. The service you buy decides who looks after each one.

Layer What it is Example
Infrastructure The server, its network and the hardware underneath A virtual server with an operating system
Application The software installed on the server, its updates, database and backups Odoo, Nextcloud, WordPress, Mailcow
Use Your users, settings, content and data Your stock, your files, your mailboxes

With self-managed hosting, the provider runs the infrastructure and you run everything else. A Noiz Cloud server is that: a clean Ubuntu or Debian install with full root access, where the operating system and everything on it are yours to install, patch and back up.

With a hosted application, you install an application on hosting you rent, and you keep it updated yourself. A WordPress site on a shared hosting plan works this way: the platform is looked after, the site is yours.

With a managed application, the provider runs the infrastructure and the application, and you run the use. The application is the product, not the box it runs on.

What "managed" should cover

The word is used loosely, so it helps to know what the work involves. A managed application service worth the name covers:

  • Updates. Security fixes and updates within the version you use, applied on a schedule rather than when someone remembers.
  • A backup before every change. If an update breaks something, there is a restore point taken minutes earlier.
  • Checks after every change. Someone logs in and confirms the parts you rely on still work: sign-in, the key flows, scheduled jobs.
  • Monitoring. The service is watched, so a fault is noticed by the provider rather than by your customers.
  • Recovery. When the application or its server breaks, the provider triages it and restores it from the most recent usable backup.
  • Support from the people who run it. A fault ticket goes to the team that runs the application, not to a call centre reading from a script.

What it should not quietly include is building things. Setting the application up for your business, writing custom code and moving to a new major version are projects, and a good provider quotes them separately so the monthly line stays predictable.

Where the line sits

The clearest test of a managed service is whether the provider can tell you, in writing, what it runs and what stays with you. At Noiz the split looks like this:

Noiz runs You run
The server, operating system and database Your users and their access
The application, its updates and fixes Your configuration and business set-up
Backups, monitoring and checks after changes What is stored and with whom it is shared
Recovery from the most recent usable backup Custom code, connectors and their compatibility
A final export of your Odoo data if you leave Your legal obligations over the data you keep

Where a managed application needs its own server, the server is billed as a separate line from the management of the application. You can also run an application yourself on a Noiz Cloud server. Managed Odoo can run on hardware at your premises that Noiz administers.

What Noiz manages today

Each managed application has its own page that sets out the work:

  • Managed Odoo. Odoo Community, the open-source ERP, with the server and the application run together: updates within your version, a database and filestore backup before every change, and logins, key flows and scheduled actions checked afterwards. It runs on a Noiz Cloud or dedicated server, or on hardware at your premises that Noiz administers.
  • Nextcloud. An account for each person on the Nextcloud service Noiz runs, for files, calendars and contacts. We keep the service updated, monitored and backed up; you decide who has an account. A Nextcloud of your own, on a server of its own, is scoped and quoted.
  • WordPress Care. Weekly updates of WordPress core, themes and plugins with a restore point first, checks after each cycle, security patching, and clean-up if the site is hacked. It works on a Noiz hosting service or on a site hosted elsewhere.
  • Private Email. Mailcow, the open-source mail server, on a server for one organisation, with the server, the mail software, its backups and support run by Noiz. Each deployment is quoted.
  • ERPNext. The open-source ERP on a Noiz Cloud server, with management quoted.

If you need a different application run for you, get in touch and tell us what it is.

When you need it, and when you do not

You probably do not need a managed application if someone in the business already runs servers, has time to read release notes and test restores, and would rather keep that control. A self-managed server is cheaper and gives you every decision.

A managed application earns its keep when:

  • the application holds something the business cannot do without, such as its accounts, its stock or its mail
  • nobody in the business wants to be the person who applies updates on a Friday afternoon
  • a failed update would cost more in lost hours than a year of management
  • you want the data in a system you own, without running that system yourselves

That last point is the reason open-source applications and managed services work well together. The software is yours to keep, inspect and move, and the work of running it is a service you can stop, change or take in-house without losing the system or the data.

Questions to ask any provider

  • Which layers do you run, and which are ours?
  • Is a backup taken before every change, and who tests that it restores?
  • What is checked after an update, and by whom?
  • When do you do the work, and how soon do you reply to a fault?
  • Are custom code and major version moves included, or quoted?
  • What do we receive if we leave, and in what format?

If you would like an application run for you, start with the page for the one you use above, or open a ticket and tell us what it is and how your business depends on it.

Sources

Checked 19 October 2026.

Noiz

Note: while some of this content was produced with the help of AI, the final editing has been done by a real human being.