Run production ops
inside your
boundary.
Permanu is a private control plane for deploys, runtime signals, incidents, and recovery on infrastructure your team already controls. Start with Git-to-runtime deploys; attach runtime signals and remediation context as your residency posture matures.
for deploy, signals, incident, and audit
by architecture, staged by rollout area
recovery actions with human approval
“Production context should stay connected to the infrastructure it describes.”
Deploy state · runtime truth · governed recovery
Release visibility that reads like product.
Deploy with visible state
Every release exposes clone, build, health gates, traffic handoff, and rollback conditions in one surface.
- Traffic handoff
- Health gates
- Rollback logic
Observe the runtime as it changes
Logs, metrics, traces, and health signals stay attached to the exact deployment path you are operating.
- Path-aware logs
- Runtime signals
- Health convergence
Resolve from the same control
When signals degrade, the resolution path—scaling, restarts, rollbacks—is available in the same context.
- Contextual scaling
- Fast restarts
- One-click rollback
Deploy with visible state
Every release exposes clone, build, health gates, traffic handoff, and rollback conditions in one surface.
- Traffic handoff
- Health gates
- Rollback logic
Observe the runtime as it changes
Logs, metrics, traces, and health signals stay attached to the exact deployment path you are operating.
- Path-aware logs
- Runtime signals
- Health convergence
Resolve from the same control
When signals degrade, the resolution path—scaling, restarts, rollbacks—is available in the same context.
- Contextual scaling
- Fast restarts
- One-click rollback
One path for deploy, signals, recovery.
Release routes, service state, runtime signals, and remediation context stay in one authored surface instead of fragmenting into tool hops.
Production teams should not choose between speed and boundary control.
Modern teams want managed deploys and real operational context, but many cannot casually push deploy history, runtime signals, and incident context into another vendor-owned cloud.
Fragmented Stack
Hosted platforms
Fast deploys, but region, cost, and data-boundary choices are constrained.
Raw infrastructure
Cheap compute, but deploys, TLS, logs, rollback, and ownership become scripts.
SaaS telemetry
Runtime signals leave the infrastructure boundary before the team can reason about them.
Incident workflow
Humans reconstruct release context from chat, dashboards, CI, and SSH.
Resident Control Plane
Private control plane
Permanu runs the production workflow against infrastructure the customer controls.
Signal graph
Deploys, runtime state, incidents, approvals, and audit stay connected.
Guided recovery
Rollback, restart, scale, and investigation paths are gated by policy and runtime context.
Residency posture
The product shows what is resident today and what is staged for the next rollout area.
Deploy, observe, resolve, and govern in one loop.
Start with deployment control. Add runtime signals, incidents, approvals, audit, and residency posture without forcing teams to reconstruct production context from separate tools.
Git-to-runtime rollouts with real gates
Ship from source to healthy traffic with visible checkpoints and operator-facing release state.
Run where the customer boundary requires
Point the control plane at VPS, private cloud, or required regions without making compute a platform resale.
Log streams in the release path
Read build and runtime logs where the deploy is happening instead of treating them as an external feed.
Metrics tied to runtime posture
Attach throughput, latency, and saturation to the rollout path as resident telemetry is brought in area by area.
Trace the exact path that changed
Follow hot paths and slow edges through services without losing the deployment context.
Incident context in place
See degradations where the operator is already working so the response loop stays short.
Remediation with signal and approval
Treat rollback, restart, and recovery as governed production actions, not detached buttons.
Shared residency posture
Give engineering, platform, and SRE teams one view of what data is resident, staged, and audited.
Operate the resident release path.
Release propagation
A release enters the graph with intent attached. Commit, target environment, and health policy move together.
Signal convergence
Logs, metrics, and traces attach to the runtime they describe as each resident telemetry area comes online.
Incident branch
A regression appears as a visible branch, not a separate hunt. Isolate noisy services with deploy context intact.
Recovery loop
Recovery is policy-gated and auditable. Treat rollback, restart, and scale as governed production actions.
Trust starts with a visible boundary.
The trust layer belongs inside the same system language: visible data boundaries, consistent runtime posture, approval-gated recovery, and audit trails that are readable before procurement asks for proof.
Runs on infrastructure you control
Permanu deploys onto VPS, private cloud, or customer-required regions instead of reselling compute as the only path.
Residency posture is visible
The product should show which operational data is resident today, which telemetry is staged, and which exports need review.
Honest about where we are
We are an early-stage alpha. We will not claim certifications or full telemetry residency before the architecture earns them.
Your infra, your data
Visible posture
Short response
Alpha, openly
Request a pilot. Bring one real stack.
We will connect one app, one server, and one production workflow so your team can see deploy state, runtime signals, incident context, and residency posture in one control plane.