How it works

Your app stays your app. Its operations become managed.

Connect a supported Linux server and define how your service runs. Infraveil’s launcher and agents manage the runtime around your application: starting processes, supervising health, routing managed traffic, and coordinating recovery. The supported supervised-process path does not require an Infraveil SDK or application source instrumentation; service configuration is required.

Try the guided demo Read the setup guide

The simple boundary

An operating layer around your application

On your servers

Your app, its process environment, and its persistent files run on infrastructure you control. The local launcher manages agents; agents run and supervise configured service processes and operate supported gateway routes.

In the hosted dashboard

The hosted control plane coordinates requested releases, approval settings, and operations across connected servers. Local components execute the managed work and report state, health, and incidents back to the dashboard.

Four steps

From a server to a managed service

Configure the service outside its application logic: how it starts, what it needs, how health is checked, and which traffic reaches it. Once connected, the runtime components carry out supported operations under those settings.

  1. Connect a server

    Install the launcher on a supported Linux server you control. It connects the machine to the hosted control plane and manages the local agents responsible for configured services.

    The server is still yours. Infraveil does not sell the compute.

  2. Add your service

    Provide the application package and service configuration: install and build commands where needed, start command, working directory, environment, port, and health check. These settings tell the supervisor how to run the service without embedding Infraveil calls in its business logic.

  3. Choose your approval mode

    Require a person to approve changes, allow known-safe changes, or automate approval where that fits your risk. You decide the operating rule.

  4. Run, supervise, and recover

    Start and supervise configured processes, apply policy to managed gateway traffic, and follow service health. When a service fails, configured restart limits and available recovery controls guide the next action.

What changes for your team

The operating work continues after deployment.

Deployment is the first transition, not the whole operating cycle. Infraveil continues supervising configured services, managing gateway routes and policy, and coordinating supported recovery actions. Your team still owns the infrastructure, application behavior, and service configuration.

See the product See how trust works