Runtime source

Read what operates on your servers.

Infraveil connects backend operations through a hosted control plane and local runtime software. Explore the published components that connect a server, manage its agents, and operate configured applications on infrastructure you control.

The operating relationship

Hosted coordination. Local operation.

The control plane connects workspace settings, releases, requested actions and received state. On your server, the launcher and workload agents carry out the configured operating work. Inspect those local responsibilities here, then follow them into the full feature reference.

01 / Server

The launcher manages the agents.

A launcher connects an enrolled server to the control plane, receives its workload assignments and manages the local agent processes. It reports host and runtime state and coordinates eligible agent-runtime updates.

That host-to-workload relationship supports both individual application operation and fleet context across enrolled servers. A registered server, an assigned workload and a healthy application are separate states.

Read the launcher template

02 / Workload

The agent operates configured services.

The workload agent prepares configured release packages, starts supported service processes, captures output, checks configured health and applies restart budgets. Its optional gateway routes managed traffic to local services through the configured policy.

For the supported supervised-process path, service configuration sits outside application business logic; an Infraveil SDK is not required inside compatible application code. Existing-service attachment is a separate observation mode and does not take over that service's lifecycle.

Read the service-agent template

03 / Setup and review

Inspect the setup and approval path.

The local Trust Console supports enrollment, customer-held approval keys and review of named component hashes. The installer source shows the setup path; the launcher and agent templates show the operating components it prepares.

Start installation through the supported portal setup flow for your workspace and run its setup command on the intended Linux server. A public template is reading material, not a personalized installer or authorization to run a new release.

Read the Trust Console · Read the installer source · Read the setup documentation

Find the component.
Read the implementation.

These links open the published source directly. With JavaScript, select a file for an inline preview and line navigation. The browser never runs the source or requests files outside this list.

Select a published file

Choose a file from the tree or the operating map above.

The implementation appears here as plain text. Raw-source links and the Git clone endpoint remain available independently of this viewer.

Preview limits: 1 MiB / 12,000 lines. Larger files remain available through their raw links.

Read in context

Source you can inspect. Boundaries you can understand.

Versions

Compare the version you intend to run.

Public source endpoints can change as releases change. Launcher and agent files ending in .j2 are templates: workspace settings and rendering can change installed bytes. This page does not claim every running component is identical to the current public file.

Use the named release and hashes shown in the Trust Console to review a proposed installation or update. Keep the source and version you reviewed when making a comparison. Manual approval retains a review step; choosing automatic approval changes that policy.

Supporting tools

Follow the implementation and its records.

The ledger utility checks a local audit ledger against a head anchor you supply. It supports inspection of the checked record chain; it does not establish that an application is safe or that every recorded action achieved its intended result.

The runtime README provides the public project guidance. Read the published license for its terms, or use the existing public Git endpoint with your own source tools:

git clone https://repo.infraveil.com/runtime.git
Scope

Customer-side source and hosted responsibilities.

This collection publishes customer-side runtime components, examples and supporting tools. The proprietary hosted control-plane implementation and customer workspace data are outside this public source collection.

Local execution does not mean no data reaches the control plane. Configuration, operating observations and source custody depend on the selected mode. Native process supervision is not an operating-system sandbox, gateway policy covers traffic that traverses the configured gateway, and local runtime recovery is not a substitute for database backups or cross-host failover.

Read the security and data boundaries and the technical architecture alongside the implementation.

See the runtime in the operating model.

Connect the local components to the application and fleet workflows they support, from process supervision to managed traffic and scoped operating actions.