CONTROLLED CONFIGURATION · SEPARATE REVIEW PATH
Your real operating need. Inside a product we still control.
Controlled Configuration is limited work within the supported, shared OperalonOS architecture. It lets an eligible partner ask us to assess a tightly scoped need without turning OperalonOS into a software house or transferring control of the product.
A request can begin only after real paid use.
After the affected Workspace completes two full, consecutive, successfully paid monthly billing periods verified in Nightvault's authenticated billing record, while its paid Base Plan is active and in good standing, an authorized Customer sponsor may submit a sanitized request for review. The Calibration Period cannot be waived. Eligibility permits a request only; it does not guarantee review, approval, a proposal, capacity, timing or delivery.
HOW IT WORKS
Four controlled decisions. No hidden entitlement.
- 01
Use the product
Complete two full, consecutive, successfully paid monthly billing periods for the affected Workspace.
- 02
Request a review
After Nightvault verifies eligibility and sponsor authority, use the sanitized intake instructions we provide.
- 03
Receive a decision
We may accept, decline, defer, narrow or ask for clarification. Eligibility is never a delivery promise.
- 04
Contract exact work
Approved work begins only under a separate Configuration SOW with scope, price and acceptance criteria.
NON-NEGOTIABLE BOUNDARY
Configuration—not custom development.
Nightvault keeps final control over feasibility, architecture, implementation, reusable components, security, testing, release, supportability and product evolution.
- No customer-specific product fork or separate codebase.
- No source-code access, escrow or on-premises deployment.
- No dedicated engineering team, staff augmentation or managed operations.
- No automatic entitlement, guaranteed acceptance, timeline or delivery.
- No Customer control over architecture, security, release or product roadmap.
- No project charge without a separately accepted Configuration SOW or Change Order.
COMMERCIAL CONTROL
Every accepted project stands on its own.
Controlled Configuration is not included in a Base Plan or Boost. Any accepted work is separately scoped, priced and contracted in a mutually accepted Configuration SOW. Scope or price changes require a written Change Order before implementation.
The public contact form is a general business channel and is not intake. When an eligible Workspace exists, Nightvault verifies billing history and sponsor authority before providing sanitized intake instructions.
ONE SHARED PRODUCT