Backend operations for Linux servers
Run your apps on your own servers.
Deploy and manage apps on your own Linux servers. Check health and logs, control managed traffic, and handle failures from one dashboard.
See each app’s server, release and health. Choose an action and check its result.
Runs configured app processes, collects logs and checks health. Applies managed traffic rules and limits restarts.
Compatible apps run on your Linux server without an Infraveil SDK.
After deployment
Server online.
API unhealthy.
An update fails. You need the app’s release, server, logs and traffic to decide what to do next.
A completed deployment can still leave a failing app.
See its release, health and logs beside its server.
Choose a target and a supported action.
The software running the app also reports its health and logs. That connects the failure to its release, server and available controls.
Fleet operations
Manage apps
across your servers.
Check server capacity, app health and report freshness. Try a restart, pause new assignments or check placement in the example.
Fleet / Production
Choose a server and workload, then try an action.
| 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 |
Selected host / api-01
Drain stops new assignments. Existing services remain running until separately stopped.
Choose the workload and target
Command scope: api-01 / Payments service
Before moving this workload, confirm that it has stopped and that a recent report shows it is no longer running on the original server.
Requested placement / reported service state
Inspect the Payments failure| 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 |
Confirm that the workload has stopped on its original server before moving it. Moving its assignment does not move its data or confirm its health. Read the operating details
Release / Payments service
The release being tested in this failed-update example.
What the runtime does
Example configuration
Managed traffic / Payments route
A separate request example: the configured gateway permits this request.
From request to application
Where the control applies
Service failure / Payments service
The API on api-01 is unhealthy. Its output and supervisor state guide the next action.
Connect the health check and application output
Current operating state
Service outcome / Payments service
Follow the selected version, local action and reported health.
Action and service result
What this example demonstrates
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
Controls for apps and servers.
Choose an area to explore.
Fleet operations
Manage apps across your servers.
Compare capacity and app health. Choose where a workload runs, pause new assignments or act on selected hosts and workloads.
How Infraveil works
A dashboard connected to your servers.
The dashboard sends settings and actions to software on each server. That software runs the apps and reports their health and logs.
Sends settings and receives server reports.
Manages the agents assigned to this server.
Starts the app and reports its health.
Runs the app using persistent files on your server.
Traffic + policy
Apply rules before requests reach the app.
Enable the local gateway to check requests against your rules before forwarding them to the app. Its rules apply only to traffic through that gateway.
Normal request example selected.
What happens next?
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
Stop retries.
Choose how to recover.
The agent checks health and restarts failed processes within configured limits. When the limit is reached, retries stop.
Try the approved 1.8.3 package, 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
Check the version.
Check its health.
After an action, check the running version and its reported health.
Keep its release, process state and managed route in view.
See what was requested and what the server reported. Use health and logs to investigate; history alone does not prove the app works or explain the cause.
See this example’s activity history
Security and data
What runs locally. What gets shared.
Apps run on your servers. Infraveil receives selected operating reports and stores source you upload for deployment.
| 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 |
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.
What information is sent to Infraveil?
Selected status, health, logs, requests, security events and change records. Source-upload deployment also sends application source.
What remains local?
Applications, persistent data, caches and retained local history stay on your servers. Your team holds the release-signing private key.
Connected tools
Manage the app.
From release to recovery.
Manage releases, processes, managed traffic and recovery together. Enable integrations to send selected reports to your team’s other tools.
Choose an area to see how it fits.
Release execution
Prepare the selected package and run its configured install, build, and start steps.
Your team keeps its existing infrastructure and specialist tools.
Pricing
One plan. Clear 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.
- 2 connected servers
- 5 managed services
- Additional server · $19/mo
- Additional service · $9/mo
- The published plan has no usage-based charges for traffic, requests, logs, or security events.
- A signed order applies if it explicitly sets different commercial terms.
- Server hosting is paid separately. Talk to Infraveil about your setup and contract requirements.
See in operation.
Explore app and server controls in the demo.