Statement of Work
The fixed-scope terms that apply to every OvernightOps engagement. These terms are accepted when you authorize payment at checkout.
Last updated 6 October 2026
This Statement of Work ("SOW") is entered into between the client identified at checkout ("Client", "you") and DataRiver New Zealand Limited, NZBN 9429050155972, trading as OvernightOps ("Provider", "we", "us"). By authorizing payment you accept this SOW together with our Terms of Service.
Version: SOW_v1.2_draft. The version in force is the one published at the time of checkout and recorded against your order.
Scope: this SOW governs project orders (fixed-scope deliverables). Operations orders — the time-based Operations Services engagements delivered personally by our senior operator — are governed by the Operations Services Statement of Work.
1. Engagement model and asynchronous boundaries
The Client engages the Provider strictly on an asynchronous, deliverable-based basis. The engagement does not include synchronous meetings, daily stand-ups, video or voice calls, or direct chat communications. All requirements, questions and feedback are exchanged exclusively through structured order metadata, Git pull-request commentary, or the secure delivery portal.
The deliverable, turnaround tier and price are fixed at the moment of checkout and correspond exactly to the deliverable SKU selected.
2. Input requirements and the SLA clock
Execution commences upon payment authorization and the provision of complete target specifications, being either (a) read-only repository access via a repository URL and a read-only access token, or (b) at least 250 characters of written specification covering the current state, the target state, the environments involved and the acceptance criteria.
Up to four repositories may be supplied; each requires its own access token. If the inputs provided are incomplete, ambiguous, or cannot be used (for example, an expired or insufficiently permissioned token), the delivery clock is paused from the moment we notify you until usable inputs are supplied. The paused time does not count toward the turnaround commitment.
Input quality. The engagement is delivered from your written intake: the shape and completeness of your information determines the quality of the output. Complete, specific input produces precise deliverables; incomplete, ambiguous or low-quality input necessarily produces correspondingly inferior output, and we deliver exactly against what you wrote. You own the responsibility for output quality that follows from the quality of the input you provide, and at checkout you confirm this explicitly: I understand that the shape of my information decides the quality of the output: complete, specific input produces precise deliverables, and incomplete or vague input produces inferior quality. I own the responsibility for output quality that follows from the quality of my input.
3. Deterministic deliverables and output format
Deliverables are limited to the exact technical artifact selected at checkout. Depending on the SKU, the completed artifact may include:
- Infrastructure: a modular, version-controlled IaC codebase — Terraform, Bicep, Pulumi, AWS CDK, CloudFormation, Helm or Kubernetes manifests — with remote state configuration, a typed variable schema and validation evidence.
- CI/CD: production-ready pipelines (GitHub Actions, Azure DevOps, GitLab CI, Jenkins or Bitbucket) with caching, secret binding, artifact publishing and a failure triage pass.
- DevSecOps: an integrated quality gate or static-analysis (SAST) pipeline stage, scanning configuration and a prioritised remediation plan; or a hardened multi-stage Dockerfile with image scanning and automated SBOM generation.
- Observability: Prometheus scrape configuration, an OpenTelemetry collector pipeline and production Grafana dashboards with alert rules.
- Integration: an event-driven serverless or containerised bridge with OAuth 2.0 authentication, schema validation, retry handling and error capture.
- Data & writing: a tested ETL pipeline, analysis or model prototype; or an evidence-based literature review, research report or scientific paper draft with citation integrity.
Delivery is formally executed when a pull request is pushed to the Client's repository, or when an artifact bundle is made available through the secure delivery portal, and the Client is notified.
4. Objective acceptance criteria
A deliverable is deemed accepted when it satisfies the acceptance criteria selected at checkout, which by default include:
- the deliverable compiles or validates cleanly (for example, a green build or a passing
terraform validate); - a step-by-step deployment runbook is included;
- no secrets are hardcoded, and configuration is supplied through environment variables or a managed secret store;
- any standard security scan defined for the SKU completes without blocking regressions.
5. Revision window and change control
The Client is entitled to one (1) structured revision cycle within 48 hours of delivery. Revisions are limited to correcting deviations from the specification submitted at checkout. Any expansion of scope, additional resource definitions, architectural redesign, or new integrations constitutes a separate engagement requiring its own authorization.
6. Payment terms and cancellation
All payments are authorized through Stripe at checkout and are final. Because compute and engineering capacity are allocated immediately upon checkout, fees are non-refundable once execution has commenced, except where the delivery guarantee in clause 7 applies or as required by applicable consumer law.
7. Delivery guarantee
If the agreed acceptance criteria are not met by the SLA deadline for your selected turnaround tier — and the shortfall is not attributable to paused inputs under clause 2 or to circumstances beyond our reasonable control — the Client chooses either a full refund or a no-charge re-run. The acceptance criteria are fixed in writing before work starts and are verified against the agreed list and the delivered evidence.
Deadlines beyond one turnaround window. Standard engagements deliver within one turnaround window (Priority Overnight under 14 hours; Standard 48 hours). Where your stated target deadline or milestone extends beyond one turnaround window, delivery proceeds as sequential sprints, each within one turnaround window, scoped and scheduled by us and presented to you before payment is taken. Payment is enabled only after you approve the sprint plan, and we then deliver sprint by sprint within each approved window. At approval you confirm: I approve the sprint plan above, including each sprint's scope and turnaround window. I understand delivery proceeds sequentially sprint by sprint, and each sprint is delivered within its approved window.
8. Verification, evidence and finality of acceptance
- Final quality gate: every engagement passes an independent delivery-quality review before delivery. An independent review team verifies the work at full coverage across seven perspectives — functional correctness (with evidence captured in the delivery report), logical accuracy, alignment with your written requirements, performance against the stated expectations, user acceptance, deliverable quality, and a check that no internal working files of ours are included in the deliverables. Where a gap is found, it is recorded with an explanation and the work is re-run until it passes; your delivery report includes the gate results.
- 48-hour verification window: refund eligibility requires the Client to complete verification within the 48-hour review window that follows delivery.
- Objective evaluation: criteria are evaluated objectively against the agreed, fixed acceptance-criteria list and the delivered evidence bundle — not against subjective preference.
- Blocked verification: if the Client blocks verification (for example, a revoked token, a deleted branch or an unreachable repository), the delivered evidence governs.
- Not acceptance failures: subjective preference, taste, or requirements discovered after execution commenced are not acceptance failures.
- Finality: once the review window closes without a substantive defect report, acceptance is final.
9. Tracking token, personal email and dashboard access
The 32-character dashboard code issued for your order is personal to the Client and is non-sharable and non-transferable. It is delivered only to the email address the Client provides and is never shared by us with any third party.
The Client must provide a unique, personal, non-shared email address. This is a hard, non-negotiable condition of this Agreement, and acceptance of this SOW constitutes acceptance of that condition. If the code is leaked or shared, any access or comments made through it are the Client's sole responsibility, and DataRiver New Zealand Limited holds no liability for third-party interference arising from a leaked code.
Permanent deletion and the claims waiver. After delivery, the Client may permanently delete the tracking dashboard from the delivery page. Deletion permanently and irrecoverably deletes every produced artifact of the engagement from our storage — the final report, every delivery file and every download — and no one, including us, can recover or re-inspect them afterwards. Because the deleted material is the primary evidence for reviewing delivered work, no refund, quality-review, or dispute claim about the delivered work can be raised, investigated, or entertained after the Client permanently deletes the dashboard. If you have any concern about the delivery, raise it before deleting. Deletion requires an explicit consent checkbox, typing DELETE and a final confirmation; the consent (including its timestamp) is recorded as evidence. At deletion you confirm: I understand that permanently deleting this dashboard also deletes every produced artifact from our storage. Once deleted, the work cannot be re-inspected or reviewed, so no refund, quality-review, or dispute claim can be raised or entertained after deletion. I agree that no claim or dispute will be raised after deleting this dashboard.
10. Confidentiality and mutual NDA
Each party will keep confidential all non-public information received from the other in connection with the engagement and will use it solely to perform or receive the services. Authorization of an order incorporates standard mutual non-disclosure obligations protecting the Client's intellectual property and trade secrets. These obligations survive completion of the engagement.
11. Lawful use
The Client represents and warrants that the work ordered, and every output we deliver, will not be used, directly or indirectly, for any unlawful purpose, including the activities listed in our Lawful Use Policy. This representation is a hard, non-negotiable condition of this Agreement, and acceptance of this SOW constitutes acceptance of that condition.
The Client consents to pre-payment screening of the order details (current state, target state, constraints, access notes, repository names and documentation branch) and to post-delivery verification of the materials provided, in each case against the Lawful Use Policy categories.
We may refuse, hold or cancel any order on reasonable compliance grounds. Where we cancel an order and no work has been delivered, the Client receives a full refund. Where work has been delivered, the delivery guarantee in clause 7 and the verification process in clause 8 continue to apply.
Our compliance practices are informed by recognised frameworks, including EAR, ITAR, Wassenaar and OFAC export and sanctions lists; NIST SSDF, SLSA and SBOM practice; ISO/IEC 27001, SOC 2 and NIST 800-171; FATF, FinCEN and PCI-DSS; ISO 37001, ISO 37301 and the FCPA; ISO/IEC 27701, GDPR and HIPAA; the NCMEC protocols, the EU Digital Services Act and the UK Online Safety Act; and ISO/IEC 42001 and the NIST AI Risk Management Framework. This is an informational alignment statement only — it is not a certification claim, and we do not claim to hold any certification we have not formally obtained.
Policy version: LU_v1.0. The full policy is published at /lawful-use. The version in force is the one published at the time of checkout and recorded against your order.
12. Data handling, security and retention
- Least privilege: we require only read-only repository access and sanitized configuration. We never request production administrative credentials or production database connections.
- Client-side encryption: access tokens are encrypted inside your browser with RSA-2048 before they are transmitted. They are decrypted only on our secured delivery machine at the moment work begins, and are never read, logged, or stored in plain form by any person or system.
- Ephemeral workspaces: codebases are processed in isolated environments and wiped after delivery and verification.
- Retention: we do not retain your project data. All order information — specifications, progress events, comments and dashboard links — is deleted within one (1) year of delivery. We retain only a minimal business summary (customer contact, project type, dates, amounts) for financial and tax record-keeping, for up to seven (7) years, after which it is also deleted.
13. Supporting documentation via the Client's repository
Supporting documentation is provided only through the Client's repository, typically on a temporary branch. Accepted formats are PDF, Markdown and PNG, with limits of no more than 15 files, no more than 10 MB per file and no more than 50 MB in total. We never host client document uploads and do not accept document transfers outside the repository.
14. Intellectual property
On full payment, all intellectual property rights in the delivered artifacts vest in the Client. The Provider retains ownership of its pre-existing tools, templates and know-how, and grants the Client a perpetual, non-exclusive licence to use any such materials embedded in the deliverables to the extent required to use them.
DataRiver New Zealand Limited is a service provider assisting the Client's ongoing project. We are not the author or owner of the Client's original work. Copyright, ownership, and responsibility for the original work remain at all times with the Client.
15. Limitation of liability
To the maximum extent permitted by law, the Provider's aggregate liability under this SOW is limited to the fees paid for the affected work order. The Provider is not liable for indirect, consequential or incidental loss. Nothing in this SOW limits rights that cannot be limited under applicable law, including the New Zealand Consumer Guarantees Act 1993 where it applies.
16. Governing law and disputes
This SOW is governed by the laws of New Zealand. The parties will first attempt to resolve any dispute in good faith through written communication, and the New Zealand courts will have non-exclusive jurisdiction.
17. Contact
Notices to the Provider should be sent to [email protected]. The Provider is DataRiver New Zealand Limited, NZBN 9429050155972, https://datariver.co.nz/.