Connect the server.
The installer establishes the customer-side setup and enrollment path. Use the portal's supported setup flow for your workspace—not an unconfigured source file copied from this browser.
Read the installerInfraveil / Customer-side runtime source
The operating runtime.
In plain source.
Read the components that connect a server, manage its agents, and operate configured backend services. Follow the path from setup to process supervision, managed traffic, and supported recovery—without digging through a private control plane.
01 / THE OPERATING PATHHosted coordination. Local execution.
Manage the agents.
The launcher receives assigned settings, coordinates local agent lifecycles, and reports host/runtime state. It connects hosted coordination to the service agents running on your infrastructure.
Read the launcher templateOperate the service.
The agent prepares configured service releases, runs and supervises processes, checks health, enforces restart limits, and operates configured managed gateway routes and supported recovery paths.
Read the agent templateFor supported supervised services, the application uses external service configuration rather than an Infraveil SDK inside its business logic. This is process and operating control—not an application sandbox or instruction-level restriction on your code.
02 / PUBLISHED FILESSeven public files. Read-only browsing.
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
Open raw sourceChoose 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.
Published source is not a personalized install.
The launcher and agent files ending in .j2 are Jinja templates. Enrollment, workspace settings, approved versions, and rendered configuration can change the installed bytes. A public template is not a blanket claim of byte-for-byte parity with every running customer component.
The public installer also contains setup placeholders. Use the supported portal setup flow to connect a server. Your application, supporting runtimes, persistent data, and recovery requirements remain part of your service configuration.
Use your own source tools.
The public Git clone route remains available. This hub presents the customer-side source scope; it does not publish the proprietary hosted backend or customer workspace data.
git clone https://repo.infraveil.com/runtime.gitStart with the runtime README and published license. For operating concepts, see how Infraveil works and the runtime architecture.