A platform team wants automation to change production. The blocked decision is whether the effect can receive exact authority and survive stale state, concurrency, missing responses and recovery.
Identity, RBAC, admission, GitOps and workflow tools may already satisfy the requirement. Nikxius must demonstrate an advantage over that stack to justify another execution component.
The product hypothesis
A customer-controlled Runtime binds authority to an exact operation and independently read native state. It freezes the command, enforces review, records dispatch before I/O and retains outcomes and unresolved obligations. Kubernetes and your IdP remain authoritative.
The first scope is one nonproduction Deployment rollback to a permitted prior image, bound to an earlier committed operation on the same native resource.
Four weeks to a decision
- Week 1: agree workflow, owner, native alternative and decision criteria.
- Week 2: install identity, credentials and the bounded operator path.
- Week 3: compare the same stale-state, lost-response and restart cases.
- Week 4: customer engineer runs acceptance; record costs and decision.
Proposed fee: US$15,000, split equally at signing and agreed acceptance. This is unvalidated pricing; written scope defines responsibilities, milestones and legal terms.
What establishes value
Value means a meaningful deficiency closed or lower control/recovery burden. Measure installation, custom engineering, operation and support separately. Founder assistance is not customer independence.
Local tests do not establish customer compatibility, production security or willingness to pay. Those are evaluation questions. A committed resource change is not proof of application health.
Use the native stack if it meets the contract economically. Continue with Nikxius only for a repeatable advantage. Production authorization and annual terms are separate decisions.