Nikxius is execution control and recovery infrastructure for production automation. We test whether one blocked operation becomes easier to authorize, execute and recover than with your existing stack.
Start with a Kubernetes Deployment rollback to one permitted prior image, tied to an earlier committed image operation. The rollback gets new authority and a separate outcome.
What we install
A customer-controlled Runtime Node, PostgreSQL and a narrowly scoped Kubernetes identity in one nonproduction environment. The agent proposes; the Node holds the mutation credential. Your IdP, RBAC/admission, GitOps, monitoring and emergency procedures remain.
A broad agent credential can permit writes outside the task. Nikxius requires that the agent cannot reach an equivalent writer or the Node’s credential. We review that boundary together.
What we test
- Bind exact target, permitted image, authority and current native state.
- Reject changed actions, stale state and unauthorized retries.
- Persist dispatch; retain UNKNOWN after a missing response.
- Restart, reconcile without blind replay, and export evidence.
- Have your engineer compare the same contract with your native stack.
What we need
A platform owner, security reviewer, disposable target, approved identity/secrets, PostgreSQL and your current execution path. The local fixture needs Node 22+, Docker, kind and kubectl; real customer identity integration is a separate check.
No model key, payment credential, public Runtime endpoint or unrelated production access is required. Support access is agreed explicitly.
The decision
After the proposed four weeks: customer-operated acceptance, measured native comparison and a continuation or exit decision. A committed patch is not application health; UNKNOWN may remain unresolved. This kit grants no production authorization.