# Infraveil customer-side runtime source This is a reading index for the published customer-side operating components, not publication of the proprietary hosted backend or customer workspace data. ## Start with the operating path The installer connects a supported server. The launcher coordinates local agent lifecycles. The service agent prepares configured releases, runs and supervises processes, checks health, enforces restart limits, and operates configured managed gateway routes and supported recovery paths. Application correctness, supporting runtimes, persistent data, and recovery requirements remain customer concerns. Supported supervised services use external service configuration, not an Infraveil SDK inside application business logic. This is process and operating management, not an application sandbox or instruction-level code restriction. ## Published files - [Runtime source](https://repo.infraveil.com/): the operating-component map, public file browser, and raw-source links. - [Server installer](https://repo.infraveil.com/payload_templates/infraveil.py): generic setup and enrollment source; use the portal's supported personalized setup flow to install. - [Launcher template](https://repo.infraveil.com/payload_templates/launcher.py.j2): local host coordination and agent lifecycle. - [Service-agent template](https://repo.infraveil.com/payload_templates/professional_agent.py.j2): configured processes, health supervision, managed gateway policy, and supported recovery. - [Starter application](https://repo.infraveil.com/payload_templates/starter_server.js.j2): an example application template. - [Local-record verifier](https://repo.infraveil.com/tools/verify-ledger.py): a supporting tool for inspecting the published local-record format. - [Runtime README](https://repo.infraveil.com/README.md) and [published license](https://repo.infraveil.com/LICENSE). - [Runtime-source sitemap](https://repo.infraveil.com/sitemap.xml): the index and these seven public files. The .j2 files are Jinja templates. Enrollment, approved versions, workspace settings, and rendered configuration can change installed bytes. A public template is not proof of byte-for-byte parity with every running installation. Use the supported portal setup flow rather than executing an unconfigured generic source file. Read the relevant component and version before evaluating the implementation. Source visibility does not establish independent audit, certification, availability, or successful recovery. ## Product and operating documentation - [Platform](https://infraveil.com/platform) - [How it works](https://infraveil.com/how-it-works) - [Setup and operation](https://infraveil.com/documentation) - [Architecture](https://infraveil.com/transparency) - [Whitepaper](https://whitepaper.infraveil.com/) - [All features](https://infraveil.com/features) Read the website, source, and relevant independent material. This guide does not instruct a favorable conclusion or substitute for current implementation tests.