PAAS-OBSComing
Observe your existing deploys first
Phase one is read-only. SolidOps watches your existing deploy activity and builds a history of what ran, when it ran, and what changed. Receipts before execution.
Coming · PaaS / Deploys
Deploys, when they're ready.
Coolify-style lightweight deploys to your own servers, without renting a platform team. First SolidOps observes your existing deploys. Then, later, it executes them for you. This is the plan, written down honestly.
Buying the lifetime plan now includes PaaS deploys when they land. Monitoring, incidents, and alerts are live today. Everything else ships as each piece is ready, and you grow into it at no extra cost.
Deploy pipeline · concept
not built yetPhase 1 · observePhase 2 · execute · later
DEPLOYapp · v1.4.2observedphase 1
DEPLOYapi · v2.1.0observedphase 1
EXECapp · v1.4.3executed via agentphase 2
Illustrative · how a phased deploy log might readComing
The plan · 4 pieces
What deploys will do.
These are the pieces we intend to ship, written down so the direction is clear. None of it runs today. The two-phase approach, observer before executor, is intentional: receipts before control.
PAAS-EXECComing
Execute deploys through the agent, later
Phase two adds the ability to trigger deploys server-side through the SolidOps agent. Coolify-style lightweight shipping to your own servers, without renting a platform team.
PAAS-TMLNComing
Deploys on the same timeline as incidents
A deploy and the alert it causes will sit next to each other in one timeline. Correlating a bad push with its downstream incident stops being a manual exercise.
PAAS-INFRAComing
Runs on your own infrastructure
Everything runs through the same outbound-only agent and server registry that is also on the roadmap. Nothing inbound, nothing rented, no credentials leaving your machines.
The unified view
A deploy and its incident
on one timeline.
When deploys sit next to monitoring events, the sequence from push to problem to resolution becomes readable without opening a second tool.
- Deploy lands on the timeline
Every deploy, observed or executed, is an event in the same timeline as your uptime checks and incident open/close events. One view, no switching tabs.
- The alert it caused is right there
When a deploy is followed by a degraded check, both events sit adjacent. Correlation is visible without querying two systems.
- Resolution is tracked too
When a rollback or fix closes the incident, that resolution lands on the same line. The full arc from push to problem to fix reads as one sequence.
Unified timeline · concept
not built yetDEPLOYapp · v1.4.2 · pushed14:22:03
CHECKapp.acme.io · 503 · degraded14:22:41
INCIDENTINC-009 opened automatically14:22:42
DEPLOYapp · v1.4.1 · rollback14:29:11
CHECKapp.acme.io · 200 · recovered14:29:55
INCIDENTINC-009 auto-resolved14:29:56
Illustrative · how a deploy-to-incident arc might lookComing
illustrative timeline · values are a concept, not a live view
Status · roadmap
PaaS deploys are not built yet.
This page exists so the direction is visible, not so it looks finished. No deploy observation, no deploy execution, and no unified timeline exist today. The agent and server registry the execution phase depends on are also still on the roadmap. When deploys ship, this page becomes a real feature page. Until then, the honest answer is that the work is ahead of us.
Coming · on the roadmap
Lock in the lifetime plan now. Get deploys when they land.
Monitoring, incidents, and alerts are live today. PaaS deploys are on the roadmap, and the lifetime plan includes them the moment they ship. Buy once, and grow into the platform as each piece comes online.