Run releases, supervise processes, govern managed traffic, and use supported recovery controls.
Choose the operating workflow your team needs—from releases and service failures to scoped production access.
Practical tools and guides for teams running applications.
Learn about Infraveil, how the product works, and its security and data-handling practices.
Features
Start configured services, supervise their processes, control managed traffic, investigate failures, and coordinate recovery from one backend operations control plane. Launcher and agents perform the local work on supported Linux servers. Supported supervised services need configuration—not an Infraveil SDK or source instrumentation.
Choose the service version and target server, approve it under your release-signing policy, and run its configured install, build, and start steps. Manual, exact-hash allowlist, and automatic modes provide different levels of release review.
Compare assigned services, active versions, process state, health, and report age across connected servers. Find the service that needs attention and move into its operating controls without reconstructing the fleet from separate terminals.
Run configured service processes, follow health checks, and apply restart limits when they fail. Managed-package mode owns that lifecycle. External attach observes an existing service without taking over its package or restart policy.
Apply supported rate limits, IP and geographic rules, WAF controls, and honeypot routes without rebuilding the same middleware in every app. These controls cover configured managed gateway traffic—not bypass listeners or upstream volumetric attacks.
Open the service’s health, logs, request context, release history, and incident activity together. Follow the change before the failure, inspect what the server reports, and decide which operating action fits. Timing alone does not establish the cause.
Use supported restart, rollback, and recovery controls, then check the service’s health. Available actions depend on runtime mode, package compatibility, application data, and host state; restoring code does not automatically reverse a database change.
Your application, its process environment, and persistent files stay on the servers you control. Infraveil does not provide the compute.
Selected service health, releases, logs, changes, and incidents support hosted coordination. Managed-package uploads may include application source. Review the trust page and technical architecture for the setup-specific boundary.
Follow a service update, a failed health check, and a recovery choice in the guided demo. Then connect a supported server when you are ready to configure a real service.
