Secure SSH
Harden SSH and stop root signing in directly, verified with a fresh connection so you are never locked out of your own server.
96 Capabilities across 13 categories. Seven are Core, on every server the moment you connect it, and they cover securing the machine and the people who use it. The other 89 are marketplace Plugins you install per Project, so each Project carries only the stack it uses. Every one of them plans, executes, verifies, and rolls back on its own, and adapts to the Linux family your server runs.
Harden SSH and stop root signing in directly, verified with a fresh connection so you are never locked out of your own server.
Close everything that does not need to be open, and keep the ports your own applications answer on.
Give applications an account of their own with only the access they need, so nothing runs as root because it was easier.
Add a person to a server, with or without sudo, without hand editing anything or sharing one login between people.
Take an account off a server when someone leaves, and see it confirmed rather than assumed.
Install and update packages through whichever package manager the server actually uses, with the plan shown before anything runs.
Start collecting load, memory, disk and service counts on a schedule, so a server can tell you how it is doing.
PostgreSQL, MySQL, MariaDB, MongoDB, Redis and Memcached: install one, create a database and a user for an application, or inspect what is already running.
Docker, Docker Compose, Podman and k3s, including reading a Compose file that was on the server before SlideOps ever saw it.
NGINX, Apache, Caddy and HAProxy, put in front of your applications and pointed at the right one.
A certificate issued and renewed for a real hostname, verified by asking for the page rather than by trusting that it worked.
Pull a branch, build it, and run it, with the next deploy noticing there are new commits waiting for it.
Node.js, Python, Go, PHP, Ruby, Rust and Java, installed at a version you choose and removable when you are done with them.
RabbitMQ and NATS, with vhosts and users created for the applications that need them.
Meilisearch and MinIO, for the two things an application usually needs a second server for.
WireGuard interfaces and peers, so servers can talk to each other without going out over the public internet.
Fail2ban, unattended security updates, and key-only SSH enforcement, each verified after it is applied.
Scheduled backups configured on the server itself, so the data outlives the machine holding it.
Read an existing NGINX, PostgreSQL, Docker Compose or k3s install without changing a thing, and bring it under management as it stands.