From deployment to daily operation
Run your apps. Manage what happens next.
Software on your Linux servers runs and supervises compatible apps. If an API fails a health check after an update, use the hosted dashboard to check its release and logs, request a supported action and verify the result. The same dashboard coordinates actions for selected workloads across a fleet.
What runs where
One hosted dashboard, a runtime on each server
On your servers
Your app processes and persistent files stay on your servers. A launcher on each server starts and supervises its assigned agents, which run configured apps and apply policy to traffic through the optional gateway.
In the hosted dashboard
Choose a release, change settings or request an action in the dashboard. The local runtime carries out supported requests and reports what it did and what it observed.
Four steps
From a server to a managed service
Configure how each service starts and how to check its health. Compatible managed apps need no Infraveil SDK in their code.
-
Connect a server
Run the selected server’s setup command on a supported Linux host. The launcher connects that host and manages the agents assigned to it.
You supply the server and its compute.
-
Add your service
For managed deployment, supply the app package and a runtime contract with its startup, environment, port and health check. To observe an existing systemd service, use attachment. Its current service manager keeps responsibility for deployment and restarts.
-
Choose your approval mode
Your key signs each exact release hash. Review hashes individually, use an allowlist of hashes you’ve already approved, or enable automatic signing without a per-release review. Operating actions have their own authorization.
-
Run, supervise, and recover
Agents collect app output, check health and stop restarting a failed process when its retry budget runs out. Restore compatible app code from a verified known-good package when one is available. Agent updates have their own rollback path. Keep database restores and cross-host recovery in your separate recovery plan.
What changes for your team
Operate one app or a group across your servers.
Compare reported capacity before assigning workloads. Set startup order, plan maintenance and choose the workloads you intend to change. Check each execution result and the app’s reported health afterward. Your team is responsible for app behavior, data backups and host security.