Secure your servers, then run Projects on them
How SlideOps works, in plain language: connect and secure a server, create Projects, install only what each one needs, and deploy. Read it straight through, or take the one page that answers your question.
Start at the beginningStart here
Build
- ProjectsOne stack, the servers it runs on, and the Services inside it.
- ServicesA deployed workload, its status, and what you can do with it.
- DeployingWhere a workload comes from and how it runs on the machine.
- Deploying with a DockerfileStep by step, one container built from your repository.
- Deploying a Compose stackStep by step, several containers that find each other by name.
- Environment and secretsConfiguration values, sealed secrets, and when they take effect.
- Redeploying and rollbackShipping a new commit, and getting the last one back.
Infrastructure
- ServersConnecting a machine, checking it, and securing it.
- Server usersThe accounts on a machine and what each one may do.
- CapabilitiesInstalling something, and managing it afterwards.
- Private networkLetting your servers reach each other without the public internet.
- TerminalA real shell on a server or inside a Service.
Connect
Observe
- ActivityWhat happened, to what, and in what order.
- LogsReading what a Service printed, live and after the fact.
- ReportsVerification evidence, posture, inventory and health, gathered.
- Performance profilingCapturing where a Service spends its time or memory, down to the function.
- Reading a flame graphThe answer, hot spots, colours, zoom, search and every question a profile asks.
- Comparing profilesWhat changed between two profiles, and before and after a deploy.
- Continuous profilingA profile every few minutes, and a capture whenever CPU spikes.
- Server profiles and debug symbolsWhat a whole machine is doing, and naming a stripped binary's functions.
- Profiles and recommendationsEvery profile in the Workspace, what they say to fix, and AI summaries.