These plans run a specific application for you, so you are not maintaining a server underneath it. You work in the application; we look after everything below it.
What we look after
- The server, its operating system and its security updates
- Installing the application and keeping it running
- The network, and monitoring that the service is up
- Backups of the platform
What is yours
- What you create in the application — your posts, your workflows, your data
- Accounts and who has access to them
- Anything you connect it to, and the credentials for those services
- Your own copies of anything you would not want to rebuild
The short version: if it is infrastructure, it is ours. If it is content or configuration inside the application, it is yours.
Managed Ghost
Ghost is a publishing platform, built for blogs, newsletters and paid memberships. It is faster and simpler than a general-purpose CMS, at the cost of doing fewer things — there is no plugin ecosystem to get lost in, which is the point rather than a limitation.
It suits you if you are publishing writing and want it to load quickly and look right without assembling a site out of parts. It suits you less well if you need a shop, complex forms or heavy customisation.
Sign in at /ghost on your domain to write and configure.
Managed Make
Make connects services together and automates work between them — when something happens in one system, do something in another. It covers the same ground as n8n, with a more visual approach to building the automations.
It suits you if you want to remove repeated manual steps between tools you already use, without writing code to do it.
If you are weighing this against running n8n yourself, the trade is roughly: Make is quicker to build in, n8n gives you more control and keeps everything on your own instance. Ask us and we will tell you honestly which fits what you are trying to do.
Managed Database hosting
A database server we run, patch and back up, which your application connects to over the network.
It suits you if your application is hosted somewhere else and needs a database it is not responsible for maintaining, or if several applications need to share one. It is not the right choice if you only have one small site here — the database that comes with your hosting account is simpler and already included.
Which plan, and what are the limits
Storage, capacity and the specifics of each application — versions, available database engines, how connections are secured — vary by plan, and they change as the underlying software does.
Tell us what you are planning to run and we will tell you which plan fits, rather than you sizing it from a table and discovering the answer later. Open a ticket or contact sales from the client area. If you are already a customer and want to know exactly what your current plan provides, ask and we will confirm it for your account.
Backups
We back up the platform so that a failure on our side is recoverable.
Keep your own copies of anything you would not want to rebuild. Ghost can export your content, Make can export scenarios, and a database can be dumped — all three take minutes and none of them depends on us. Platform backups answer “the server broke”; they answer “I deleted the wrong thing an hour ago” far less well, and that is the more common way people lose work.
If you need a restore, open a ticket and tell us what you need back and roughly when it was last correct.
Getting help
For anything about the service itself — it is down, it is slow, it needs restoring — open a ticket from the client area.
For questions about using Ghost or Make themselves, their own documentation is more current and more detailed than anything we would maintain, and worth going to first.
