Server administration and security hardening

The Linux servers under your website kept patched, locked down, monitored, and backed up by the person who also knows the site running on them.

What you get

  • A server where every login is a named person with a key, and root is not one of them.
  • Security patches applied within days of release, with a record you can read.
  • A backup restored on a schedule, so the first restore is not during an outage.

Start a project Pick a time

Where it goes wrong

A server set up for a launch is rarely touched again. Root logs in with a password. The firewall is whatever the image shipped with. The operating system is two releases behind, and the PHP version went out of support last year. The backup job writes to the same disk it protects. Nobody is told when the disk fills or the site stops answering, so the first alert is a member's email. The person who knew the setup has left, and the notes were never written.

What we do

  • Administer Ubuntu and Debian servers on Linode, AWS, Azure, or your own hardware: the web server, PHP, the database, the cache, and the mail relay, configured for the site's actual load and documented.
  • Harden each host. SSH by key only, no root login, a second factor on the console accounts, a firewall that allows what the site needs and nothing else, TLS kept current with HSTS, and kernel and package security updates applied on a schedule you can see.
  • Review access so each person and each service has one named account with the permissions it needs and no more, and remove what nobody uses. Sudo, database grants, API tokens, and deploy keys included.
  • Find and close the ordinary exposures before someone else does: unsupported PHP or database versions, admin paths open to the world, writable directories, leaked configuration, a database listening on a public port. We check what is reachable and what is advertised, and fix what we find.
  • Monitor the hosts and the sites. Disk, memory, failed services, certificate expiry, failed logins, and whether the home page and the login page still answer, with an alert sent to us when they do not.
  • Back up off the server, encrypted, with the database and the files on separate schedules, and restore from those backups on a calendar so the procedure is known before it is urgent.
  • Keep it that way. Monthly patching, log review, and a short written report of what changed, what was found, and what is next.

How it runs

It starts with a written review of what you have: every host, every account, every open port, every scheduled job, with the risks ranked and the fixes priced. The first round of hardening is a fixed-price project. After that it is a monthly line in your care plan or its own agreement, from a price set in the review. The servers and the accounts stay in your organization's name, and you get the documentation, so you can hand the work to someone else at any time. Leonardo administered the Linux and AWS servers under the sites on the work page, some of them for more than ten years. Monitoring means an alert reaches us. It is not round-the-clock response: care plans do not include guaranteed emergency response, as the service terms say.

Who this fits: Associations, Educational institutions, Foundations, Nonprofits. This service has no published price. We agree on a written scope and a fixed price before the work starts, and the pricing page has the website and care prices.

Ask for a server review

Connected to the systems your team already runs on

Member records, the CRM, the mail list, and staff sign-on stay in step with the website, so nobody enters the same thing twice.

Cloud and infrastructure

  • Amazon Web Services
  • Microsoft Azure
  • Linode (Akamai)
  • DigitalOcean

Content management

  • Drupal
  • WordPress

Membership and CRM

  • CiviCRM
  • Salesforce
  • Higher Logic
  • Novi AMS

Sign-on and mail

  • Keycloak
  • Mailgun
  • Mailchimp

Automation and AI

  • n8n
  • OpenAI
  • Anthropic
  • xAI (Grok)

Logos are trademarks of their owners. Listing them states experience, not partnership or endorsement.

Your next project

What would make your website more useful?

Tell us who it serves, what is in the way, and when you need it. A paragraph is enough to start, and Leonardo reads it himself.

Tell us about it Pick a time

Pick a time. Thirty minutes.

Open the scheduler in a new tab

Tell us about your project

Open the contact page instead