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.

A dashboard for apps on your servers. Hosted dashboard / your servers
Hosted Dashboard

See each app’s server, release and health. Choose an action and check its result.

See how it works
Operating settings selected
Your infrastructure Server connection

Connects your server to the dashboard.

See how it works
connected / ready
Your infrastructure App supervision

Runs configured app processes, collects logs and checks health. Applies managed traffic rules and limits restarts.

See service controls
Processes supervised
Your infrastructure Your app

Compatible apps run on your Linux server without an Infraveil SDK.

Review data handling
Your application code
WorkspaceProduction
Fleet3 connected Linux hosts
Workloads5 managed workloads
AttentionHealth + report freshness
Operating scopeSelected host and workload
Illustrative architecture and service examples—not live customer telemetry.

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.

Release completeIs the app healthy?

A completed deployment can still leave a failing app.

The server is onlineWhich app needs attention?

See its release, health and logs beside its server.

A decision is neededWhat should change?

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.

INFRAVEIL / OPERATIONSIllustrative workspace · 3 hosts / 5 services

Fleet / Production

Choose a server and workload, then try an action.

2 items need attention
Connected hosts03
Configured services05
Need attention02
Pending requests00
Attention combines unhealthy services and stale host reports.
Select a host to inspect its workloads and operating controls.
HostLast reportCPUMemoryStorageLoad / coresAssignments
Current8 seconds ago68%72%54%2.4 / 4Open
Current11 seconds ago24%38%42%0.9 / 4Open
Stale4 minutes ago————Fresh report needed

Selected host / api-01

ConnectionCurrent · 8 seconds ago
Host capacityCPU 68% · memory 72% · storage 54%
Existing servicesPayments service, Catalog worker
New assignmentsAllowed

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.

Select a host to inspect its capacity and services, or try a scoped operating action.

Requested placement / reported service state

Inspect the Payments failure
ServiceReleaseRequested hostReported hostHealth
Payments service1.8.4api-01api-01Unhealthy
Catalog worker4.3.0api-01api-01Healthy
Identity3.2.8worker-02worker-02Healthy
Email worker2.1.6worker-02worker-02Healthy
Gateway2.14.1edge-03edge-03Last 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

Five sample workloads. These controls change the illustration only; they never operate production.

An example update

Release it. Run it. Handle failures.

Follow a release, a failure and a recovery choice. The dashboard directs the work; software on your server does it.

Payments service / 1.8.4Managed release · Production · api-01
01 / CONFIGURE

Describe how the service runs.

Choose the service and server. Configure its startup command, environment, health check and route without adding an Infraveil SDK to the app.

Current step Payments service · configuration ready
HostedControl plane

Coordinates releases, settings and actions.

requested update recorded
Customer hostLauncher

Connects the server and manages its agents.

waiting for approval
Service supervisionAgent

Runs app processes, checks health and manages configured routes.

update not started
Your applicationApplication

Your application, running on your server.

Your application code
Payments service · configuration readyIllustrative service lifecycle · not live telemetry

Update requested.

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.

You inspectHost capacity, connection freshness, and service health
You chooseTarget host, workload placement, or maintenance scope
Runtime actionLocal launchers and agents carry out supported commands
ResultRequested changes alongside reported runtime state
Operating details and approval modes

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.

Control plane

Coordinates releases and settings; shows reported results.

Launcher

Connects the server and manages assigned workload agents.

Agent

Runs app processes, captures output and checks health. Manages configured routes.

Application

Your app, running on your own server.

See how the system responds
Illustrative flow
HostedControl plane

Sends settings and receives server reports.

Requested service settings available
Customer-controlled infrastructure / api-01Runs on your server
MachineLauncher

Manages the agents assigned to this server.

Managing the service agents
Service supervisionAgent

Starts the app and reports its health.

Supervising process and health
ApplicationApplication

Runs the app using persistent files on your server.

Application running on your server
Health and activity reportsService state available in the dashboard
New changesAvailable
ApplicationsRunning
ReportingCurrent
What this meansLocal runtime performs the work

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.

Request story / Payments service
POST/v1/paymentsShared request
Requestreceived
RoutePayments service
Policyevaluating
Applicationwaiting
Responsewaiting
Change historywaiting
Arrivalrequest receivedShared request
Routeroute matchedPayments service
Policyrequest-rate policyallow
Responseapplication response200
The gateway permits this request within its configured rate limit. The service returns a successful response (200) in this example.record linked

Normal request example selected.

Interactive example · a failed releaseThe new version is unhealthy.
What happens next?
Service needs attention
The new version is unhealthyVersion 1.8.4 failed its configured health check.Failed
Automatic retries have stoppedThe restart budget was exhausted; the supervisor stops this retry loop.Retries stopped
A replacement release is preparedYour team has prepared and approved package 1.8.3 through the normal release workflow in this example.Package approved
Your choice controls the next actionDeploy the approved package, or leave version 1.8.4 selected while you investigate.Waiting for your choice
Check the service after the actionThe example shows its running version and health after your choice.Result pending
Failing version1.8.4
Approved replacement package1.8.3
This exampleReplacement package approved

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.

Stop the retry loop.Restart limits prevent endless retries.
Choose a recovery path.Local fallback needs an available known-good package. A replacement deployment needs an approved release.

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.

PAYMENTS SERVICE / EXAMPLE OUTCOMEIllustrative · not live telemetry

The release failed. The supervisor stopped retrying.

Selected version and reported healthVersion 1.8.4 · Unhealthy
Recovery choiceDeploy approved version or investigate
Runtime actionNo replacement deployment started
Service resultRecovery needed
Act on the app you investigate.

Keep its release, process state and managed route in view.

See what changed.

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
Payments service / activityillustrative
ReleaseVersion 1.8.4 startedRunningapi-01
HealthConfigured check failedUnhealthyRestart budget exhausted
ChoiceRecovery choiceDeploy or investigateNo replacement deployment started
ResultService conditionUnhealthyPayments service · version 1.8.4

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 / stateHosted by InfraveilYour infrastructure
Requested changesRecorded in the dashboard—
Requested settingsSent to the serverApplied on the server
Launcher—Connects and manages the server
Service supervisionSelected health reportsRuns and monitors each service
Running applications—Customer-controlled
Persistent application files—Customer-controlled
Health and change recordsSelected reports and optional local-record referencesRetained local records
Release-signing private keyNot held by InfraveilHeld by your team
Source visibility

Inspect the launcher and agent code on your servers. The hosted dashboard code is private.

Independent review

No independent external security audit has been completed.

Team access

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.

Work across your tools

Choose an area to see how it fits.

Connected app controls

Release execution

Prepare the selected package and run its configured install, build, and start steps.

Your team keeps its existing infrastructure and specialist tools.

Send reports and alertsSlackTeamsincident.ioGitHubSigned webhooks

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.

Professional$99per month · no setup fee
Plan includes
  • 2 connected servers
  • 5 managed services
  • Additional server · $19/mo
  • Additional service · $9/mo
Billing details
  • 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.

Campaign update

Infraveil is in an active prospecting campaign

About the campaign