A server, in the same environment the site was built and tested in
Optional, agreed together with the project
No plugins to update. No update you forgot to install.
Server, domain, backups and updates. Fewer pieces to maintain than a WordPress site, because there are no third party pieces.
Sound familiar
The site belongs to your company. The domain is registered under a nephew's name.
The server was set up by someone who no longer works there, with an email address that no longer exists, and the password was on a piece of paper in a drawer that got emptied in a move. Everything works, so nobody looks at it. It works until the day it stops working, and that day the round of phone calls begins.
What is included
Six pieces, already built
A domain registered under your company's name
Backups of the site and of the data edited from the panel
Updates to the environment, not third party plugins
The same infrastructure every demo runs on
One point of contact, not a call centre
How it works
Four steps
1
It gets decided together with the project
Do you run it yourself or do we. Both answers are fine.
2
If you already have hosting, we use it
Requirements get checked and it gets deployed there.
3
If not, the site is published on our own server
The same environment as in testing.
4
The domain moves to the company's name
With access handed to someone still at the company.
Questions
Frequently asked questions
Do I have to take this from you?
No. It is optional and gets agreed together with the project.
Why is this lighter than maintaining a WordPress site?
Because there are no plugins. On WordPress, maintenance mostly means patching third party pieces.
Whose name is the domain under?
Your company's. Always.
What happens to the data I edit from the panel?
It lives on the server and is included in the backups.