Run releases, supervise processes, govern managed traffic, and use supported recovery controls.
Choose the operating workflow your team needs—from releases and service failures to scoped production access.
Practical tools and guides for teams running applications.
Learn about Infraveil, how the product works, and its security and data-handling practices.
Backend operations control plane
Infraveil runs and monitors compatible apps on your Linux servers—connecting releases, health, logs and controls across your fleet.
See each workload’s host, release, health and supported actions.
The agent runs your configured processes, captures output and checks health. It also operates managed routes and supported recovery.
Compatible apps run as ordinary processes on your Linux server, without an Infraveil SDK.
When the release is done, the work continues
Specialist tools solve different problems. When an API fails after an update, you still need its version, server, logs and traffic context to choose an action.
A finished deployment can still leave an unhealthy app.
Find the app’s version, host, health and output together.
Choose the app or fleet scope, then a supported action.
The runtime knows the app it supervises, so its context and controls stay connected.
Fleet operations
Compare server capacity, latest reports and app health. Try a restart, drain new assignments, or check where an app can run.
Inspect a host. Choose a workload. Keep the action scope visible.
| Host | Last report | CPU | Memory | Storage | Load / cores | Assignments |
|---|---|---|---|---|---|---|
| Current8 seconds ago | 68% | 72% | 54% | 2.4 / 4 | Open | |
| Current11 seconds ago | 24% | 38% | 42% | 0.9 / 4 | Open | |
| Stale4 minutes ago | — | — | — | — | Fresh report needed |
Drain stops new assignments. Existing services remain running until separately stopped.
Command scope: api-01 / Payments service
Before moving this workload, confirm its completed stop and fresh absence on the original host.
| Service | Release | Requested host | Reported host | Health |
|---|---|---|---|---|
| Payments service | 1.8.4 | api-01 | api-01 | Unhealthy |
| Catalog worker | 4.3.0 | api-01 | api-01 | Healthy |
| Identity | 3.2.8 | worker-02 | worker-02 | Healthy |
| Email worker | 2.1.6 | worker-02 | worker-02 | Healthy |
| Gateway | 2.14.1 | edge-03 | edge-03 | Last healthy · report stale |
Moving a workload requires confirmed stop evidence from its original host. Placement does not migrate data or prove health. Read the operating details
The release being tested in this failed-update example.
A separate request example: the configured gateway permits this request.
The API on api-01 is unhealthy. Its output and supervisor state guide the next action.
Follow the selected version, local action and reported health.
The release, supervisor and recovery action belong to the same service. Check its health after the action.
Illustrative outcome. Approved packages must fit your data and configuration; code deployment does not restore data.
Five sample workloads. These controls change the illustration only; they never operate production.
Capabilities
Choose an area to explore its fleet and application controls.
Fleet operations
Compare hosts and app health. Choose a suitable host, drain new assignments, and target supported actions at specific hosts and workloads.
How Infraveil works
Software on each server runs and monitors your apps. Your dashboard connects their health, logs and controls across the fleet.
Coordinates requested settings and receives reports from your servers.
Applies server settings and manages the service agents.
Checks updates, starts the service, and reports its health.
The application runs on your server, with its persistent files stored there.
Traffic + policy
The gateway routes requests and applies your rules before they reach the app. Only traffic through that gateway is covered.
Normal request example selected.
Retries stopped. Deploy the approved 1.8.3 package in this example, or keep 1.8.4 selected and investigate.
Recovery is an operating action
Supervision continues after deployment. Health checks detect failures; restart limits prevent endless retries.
Your team has approved version 1.8.3 in this example. Deploy it and check health, or keep 1.8.4 selected and investigate.
Illustrative deployment. It does not undo database migrations or restore application data.
The service after the action
Choose an action above. Follow the service’s selected version, local execution and health together.
Investigate and act on the same service, with its release, process and managed route in view.
History shows the action and reported result. It does not prove application correctness or the cause of a failure.
Security and data
Your apps run on your servers. Infraveil receives selected operational reports; source-upload deployments also store application source.
| Responsibility / state | Hosted by Infraveil | Your infrastructure |
|---|---|---|
| Requested changes | Recorded in the dashboard | — |
| Requested settings | Sent to the server | Applied on the server |
| Launcher | — | Connects and manages the server |
| Service supervision | Selected health reports | Runs and monitors each service |
| Running applications | — | Customer-controlled |
| Persistent application files | — | Customer-controlled |
| Health and change records | Selected reports and optional local-record references | Retained local records |
| Release-signing private key | Not held by Infraveil | Held by your team |
You can inspect the launcher and agent code on your servers. The hosted dashboard code is private.
No independent external security audit has been completed.
Workspace access requires authentication. Contact Infraveil about individual team-member permissions.
Selected status, health, logs, requests, security events and change records. Source-upload deployment also sends application source.
Applications, persistent data, caches and retained local history stay on your servers. Your team holds the release-signing private key.
Connected tools
Use connected runtime controls for releases, processes, routes and recovery. Send selected reports to your specialist tools.
Choose an area to see how it fits.
Prepare the selected package and run its configured install, build, and start steps.
Your team keeps its existing infrastructure and specialist tools.
Pricing
Professional includes two connected servers and five managed services. A service is an independently enrolled workload; it can contain configured APIs, workers, and other application processes.
Try the example, read the features and architecture, or request a guided demo.
