Infrastructure and hosting
Where the site runs, who can log in, how it is patched, and whether the backup has ever been restored.
Where it goes wrong
Nobody knows who has the server password. The backup runs every night, and nobody has ever restored one. Updates wait until something breaks. The person who set it up left, and the hosting bill goes to a personal card.
What we do
- Linux servers configured for Drupal or WordPress, with web server, PHP, database, and cache set up for the site's actual load.
- Accounts reviewed so each person has the access they need and no more.
- Backups stored off the server, and a restore tested.
- Security updates on a schedule you can see.
- Monitoring that tells someone when the site stops answering.
How it runs
We can run the site on infrastructure we administer, or work on an account your organization owns. The second is often better for a public agency or a campus, because the accounts stay in your name. Either way, the agreement says who pays the provider and who holds each login. A launch includes one restore test. Regular restore tests can be part of care.