Infrastructure should be understandable
You describe the outcome you want, not the commands to type. SlideOps reads your server in plain language and explains every step as you go, so the system teaches as you work.
Infrastructure operations, in plain language
Operate your own infrastructure with confidence.
SlideOps turns SSH, Docker, systemd, databases, and security into one observable control plane. You stay in charge of the servers. Every meaningful change is planned, approved, verified, and recorded.
- Your servers stay yours
- Approval before changes
- Verified after execution
edge-01
Node overviewUpdated just nowServer
Readyedge-01
Ubuntu 24.04 · 4 vCPU · 8 GB
Services
06
2 running nowPosture
92%
1 recommendationCPU usage
34%
last 15 minutes Recent activityView history
Deploy API service
Verified · 2 minutes agoSSH hardening
Completed · todayRepository
Deploy from Git with a repeatable plan.
Container
Adopt running Docker workloads with context.
Capability
Install and manage databases as first-class services.
Why SlideOps
One clear path from intent to a verified outcome
You work in two levels: first secure your servers, then run Projects on them, installing only the stack each Project needs. Underneath, SlideOps separates the Capability you intend from the Provider that carries it out on your platform, so the same goal works across different systems. Three ideas hold it together.
Operators stay in control
Nothing runs until you approve a plan. SlideOps never operates as root, your servers stay yours, your credentials are encrypted, and you are never locked out of your own machine.
Verification and rollback build confidence
Every change is proven before it counts. If a check does not pass, the change is rolled back automatically, so confidence is the result rather than a hope.
The model
Secure your servers, then run Projects on them
The two-level model is the spine of the product. You secure a server once, then let many Projects share it under hard limits, each carrying only the stack it needs. Keeping the two apart is what lets one large server do the work of a fleet.
1
Servers
Over SSHConnect a Linux machine over SSH, run a read-only quick check, and secure it so SlideOps never operates as root.
- Connect over SSHHost key trusted on first use.
- Run the quick checkRead-only Discovery and Assessment.
- Secure with No RootNon-root sudo, root sign-in disabled.
No Root, verified before the switch
SlideOps creates a non-root administrator with sudo, hardens SSH so root can no longer sign in, then switches its stored connection to that account. The new access is proven first, so you are never locked out.
Non-root sudoRoot disabledCredential rotated
2
Projects
On one serverCreate a Project, assign one or more secured servers, install only the Plugins it needs, connect GitHub, and deploy resource-limited Services.
One secured server, many Projects, hard limits
storefront
2.0 vCPU - 4 GB
analytics
1.0 vCPU - 2 GB
Every Service runs under a fixed CPU, memory, and disk ceiling, so Projects share a server without fighting for resources.
Install only this Project's stack
ContainersReverse proxyHTTPSPostgreSQLGitHub
The lifecycle
Every change follows one lifecycle, end to end
From a read-only look to a recorded result, each Operation moves through the same nine steps. The path never skips, so intent, approval, and proof stay in the same order every time.
1DiscoverRead the server as it is.
2AssessJudge what is safe.
3RecommendPropose the outcome.
4PlanLay out exact steps.
5ApproveYou give the go.
6ExecuteCarry out the plan.
7VerifyProve it worked.
8ObserveWatch the result.
9RecordWrite it to History.
Discovery only observes
The read-only quick check reads your server and changes nothing, so you can look before you touch.
Approval is your gate
Nothing executes until you approve the plan. The decision to change anything is always yours.
Verification always follows
Every execution is verified, and a change that would cut you off is caught and rolled back automatically.
Capabilities
Core security on every server, the rest from the marketplace
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.
CoreOn every server, nothing to install
Built in
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.
Built in
Configure firewall
Close everything that does not need to be open, and keep the ports your own applications answer on.
Built in
Create application user
Give applications an account of their own with only the access they need, so nothing runs as root because it was easier.
Built in
Manage server user
Add a person to a server, with or without sudo, without hand editing anything or sharing one login between people.
Built in
Remove server user
Take an account off a server when someone leaves, and see it confirmed rather than assumed.
Built in
Manage packages
Install and update packages through whichever package manager the server actually uses, with the plan shown before anything runs.
Built in
Enable monitoring
Start collecting load, memory, disk and service counts on a schedule, so a server can tell you how it is doing.
Marketplace89 more, installed per Project
28 Capabilities
Databases
PostgreSQL, MySQL, MariaDB, MongoDB, Redis and Memcached: install one, create a database and a user for an application, or inspect what is already running.
9 Capabilities
Containers and orchestration
Docker, Docker Compose, Podman and k3s, including reading a Compose file that was on the server before SlideOps ever saw it.
10 Capabilities
Web servers and proxies
NGINX, Apache, Caddy and HAProxy, put in front of your applications and pointed at the right one.
Security
HTTPS and certificates
A certificate issued and renewed for a real hostname, verified by asking for the page rather than by trusting that it worked.
Deployment
Deploy from a repository
Pull a branch, build it, and run it, with the next deploy noticing there are new commits waiting for it.
12 Capabilities
Language runtimes
Node.js, Python, Go, PHP, Ruby, Rust and Java, installed at a version you choose and removable when you are done with them.
9 Capabilities
Messaging and queues
RabbitMQ and NATS, with vhosts and users created for the applications that need them.
8 Capabilities
Search and object storage
Meilisearch and MinIO, for the two things an application usually needs a second server for.
5 Capabilities
Private networking
WireGuard interfaces and peers, so servers can talk to each other without going out over the public internet.
Security
Hardening add-ons
Fail2ban, unattended security updates, and key-only SSH enforcement, each verified after it is applied.
Backup
Backups
Scheduled backups configured on the server itself, so the data outlives the machine holding it.
Adoption
Inspect what is already there
Read an existing NGINX, PostgreSQL, Docker Compose or k3s install without changing a thing, and bring it under management as it stands.
Security first
Locked down by default, and you keep the keys
Security is the one thing that is Core on every server, and it is not a setting you have to remember. SlideOps drops root, hardens SSH, seals your credentials, and proves it is safe before it commits, so the secure path is also the easy one.
You always own the infrastructure. SlideOps operates it with least privilege and leaves a full, readable record of every change.
Never as root
SlideOps creates a dedicated non-root administrator with sudo and operates only as that account, so root is never the way in.
Hardened SSH
Root sign-in is turned off and the host firewall denies incoming by default, always keeping your current SSH port open first.
Sealed credentials
Connection secrets are encrypted at rest and decrypted only at connection time. They are never shown, logged, or returned.
Trusted on first use
A host key is trusted the first time you connect and pinned after, so a changed key is noticed rather than silently accepted.
Rotate access safely
A server settings page rotates the connection credential and manages the accounts on the server, without ever locking you out.
Verify, then rollback
Every execution is verified, and a change that would cut off your access is caught and rolled back before it can strand you.
Deploy and monitor
Three ways in, however your work already runs
A Service comes from a repository, from an image, or from something already running on the server that SlideOps adopts as it stands. It runs as a container, a Compose stack, or a systemd service with no container at all. Whichever you pick, you get an address, a terminal, monitoring, and every Operation written to a History you can read.
From a repository
Clone a branch, build it, run it. Every redeploy pulls that branch, and SlideOps tells you when new commits are waiting. The only source it can rebuild from, so the only one where redeploy means "take the newest code".
From an image
Run an image that already exists. Nothing is built here, which suits anything published to a registry or built somewhere else.
Adopted
It was already running when SlideOps found it. Adopting changes nothing: not restarted, not rebuilt, not moved. SlideOps starts keeping a record, so a server with years of history joins without a migration.
GitHub pull deploys
- 1Connect your own GitHub OAuth app, once.
- 2A Service with a repository source clones on its first deploy.
- 3On every redeploy it pulls the branch you name. No re-clone.
git pull origin main
Monitoring and history
CPU
Memory
Disk
Service health, on a schedule
Notifications when it matters
Pricing
Priced for the command center, not your hardware
Every Capability runs on your servers, never on ours, so we never cap the CPU, memory, or disk you already own. You use all of it. Your plan sets only what SlideOps provides: the servers you connect, the Projects you run, the seats on your team, and your support.
Free
$0forever
See the whole flow on one server.
- 1 Workspace
- 1 server
- 1 Project
- 1 seat per Workspace
- Core security on every server
- The full marketplace
- 7 days of history
- Community support
Starter
$19per month
A few Projects across a couple of servers.
Everything in Free, plus
- Up to 3 Workspaces
- 3 servers
- 5 Projects
- 2 seats per Workspace
- Automations and scheduling
- 30 days of history
- Email support
Pro
$49per month
Run a real fleet, with your team.
Everything in Starter, plus
- Up to 10 Workspaces
- 15 servers
- 30 Projects
- 5 seats per Workspace
- Advanced monitoring and reports
- 1 year of history
- Audit trail
- Priority support
Enterprise
Custom
For a whole team, at any scale.
Everything in Pro, plus
- Unlimited Workspaces
- Unlimited servers and Projects
- Unlimited seats
- Single sign-on
- A self-host option
- An SLA and dedicated support
Your server's resources are yours. If you want to keep Projects from crowding each other, you can cap a Service's CPU and memory yourself, that is your choice on your own server, never a limit we impose. Every plan includes the full lifecycle and Core security on every server.
Who it is for
Built for anyone who runs their own Linux
From a single machine to a fleet, SlideOps meets you where you are and keeps you in control the whole way.
Developers
Ship your own app to your own server without memorizing a stack of shell commands.
Platform engineers
A consistent, verified way to run the same outcomes across a fleet of different distributions.
Self hosters
Run the services you rely on, hardened and backed up, with a clear record of every change.
Home labs
Experiment freely on your own servers, with a quick check that never changes anything until you say so.
Startups
Stand up secure infrastructure early, and understand exactly what is running as you grow.
Teams
Share one clear lifecycle so every Operator plans, approves, and verifies work the same way.
Questions
Answers before you connect a thing
No. You always own the infrastructure. SlideOps connects over SSH to orchestrate and explain the tools you already run, and it operates with least privilege as a non-root account. It never owns your servers, you do.
No. When SlideOps drops root and switches to a non-root administrator, it proves the new access works with a fresh connection before it commits the change. A change that would cut off your access is caught and rolled back automatically.
Seven Capabilities are Core, on every server with nothing to install: Secure SSH, Configure firewall, Create application user, Manage server user, Remove server user, Manage packages, and Enable monitoring. The other 89, from containers and reverse proxies to databases, runtimes, message queues and private networking, are marketplace Plugins you install per Project.
You connect your own GitHub OAuth app once. A Service with a repository source clones on its first deploy, then pulls the branch you name on every redeploy, so there is no need to re-clone.
The major families: Ubuntu, Debian, Fedora, Arch, Alpine, and openSUSE, across apt, dnf, pacman, apk, and zypper, with systemd and OpenRC. A Capability names the outcome you want, and the right Provider carries it out on your platform.
Connection secrets are sealed: encrypted at rest and never written to a log. When you need one back, you reveal or copy it on purpose from Credentials, and a Viewer cannot. Host keys are trusted on first use and pinned after.
Yes, that is the point of the two-level model. Every Service runs under its own CPU, memory and process ceilings, which you set and can change in place, so many Projects can share one large server without fighting for resources. Your plan never limits them.