Manage application updates, monitor service health, and investigate problems from one dashboard.
Choose where an update runs, set its approval requirements, and review the result reported by the server.
Practical tools, guides, and open projects for teams running applications.
Learn about Infraveil, how the product works, and its security and data-handling practices.
Application deployment and operations
Infraveil provides one dashboard to release updates, monitor applications, and manage recovery. Your applications run on supported Linux servers your team controls.
Choose updates and approval settings, then review the reports sent by your servers.
An agent checks approved updates, runs a service, and reports its health.
Your application runs on your server, alongside the files and resources it needs.
Why Infraveil exists
When an update causes a problem, your team needs to see what changed, how the application responded, and what can be done next. Infraveil brings that information together.
What will change, and who approves it?
Is the application running, and what is reaching it?
What action was taken, and did the service recover?
Spend less time piecing together what happened.
Capabilities
Choose an area to see what your team can do, what happens on your server, and what the dashboard reports.
Requested update · Payments service
Send version 1.8.4 to the selected server. Check that it starts and that the server reports the version you requested.
Inside the dashboard
Explore the same example service across its server, update, traffic, incident, and change-history views.
Compare what should be running with what each server reports.
| Service | Release | Server | Requested | Reported | Operation |
|---|---|---|---|---|---|
| Payments service | 1.8.4 | Primary server | running | degraded | Managed release |
| Identity | 3.2.8 | Server B | running | healthy | — |
| Catalog worker | 4.3.0 | Primary server | running | healthy | — |
| Gateway | 2.14.1 | Server B | running | healthy | — |
Managed release · target Primary server.
Payments service · conceptual request path simplified for this walkthrough.
Payments service · release 1.8.4 · Primary server.
Compare the request, approval, action taken, and reported result.
Interactive example with sample data. The views show how information connects; they are not live product screenshots.
How Infraveil works
Infraveil hosts the management dashboard. Software on each connected server applies your settings, runs your services, and reports their health.
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
A gateway routes requests to your services and applies the rules you configure. Follow an example request through the decision, response, and record. These controls cover traffic sent through that gateway.
Normal request example selected.
The restore is awaiting approval. No recovery action has started.
Recovery controls
This example uses manual approval to restore an earlier version after failed health checks. Approve or decline the action, then review the reported result.
Change history
See the requested update, its approval, the action taken, and the health reported afterward.
The update, who approved it, which service changed, what ran, and the result reported by the server.
The record helps reconstruct events. It does not guarantee that the application works correctly or that one request caused a failure.
The full change record stays on your infrastructure. Infraveil receives selected reports and, when configured, a reference to that local record.
Security and data
Your applications run on your servers. Infraveil receives selected health reports, logs, and events. Some deployment options also store application source files with Infraveil.
| 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 | Full local record |
| 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.
Infraveil has not completed an independent external security audit. Published documentation and inspectable code do not replace one.
Workspace access uses an authenticated account. Confirm support with Infraveil before relying on separate permissions for individual team members.
Depending on your setup, Infraveil receives server status, service settings and health, selected logs and request records, security events, and records of managed changes. Some deployment options also upload application source files.
The application runs on your servers, where its working files, caches, saved data, and full local change record are stored. You retain control of the release-signing private key.
Connected tools
See application updates, health checks, traffic decisions, and incidents in one place. Send selected reports and alerts to the tools your team already uses.
Choose an area to see how it fits.
Track the update, its approval, and the version your server is running.
Your team keeps its existing infrastructure and specialist tools.
Pricing
Professional includes two connected servers and five managed services. A service is a separately managed part of an application, such as a payments API or background task.
Explore the dashboard and see how Infraveil would work with your applications.
