One target release
Release Assurance
Reproducible technical evidence for a defined React Native release, evaluated against acceptance criteria agreed before work begins.
€2,500–€4,000
Included
Evidence and decision support.
- Reproducible iOS/Android build evidence.
- CI/release configuration review.
- Native dependency and AI-assisted diff review.
- Up to three agreed critical-flow checks.
- Store/privacy evidence.
- Rollback checklist.
- Residual-risk register.
- Release recommendation.
- One validation rerun.
Deterministic pricing
The release workload selects the band.
Standard — €2,500
Single-app repository, one production iOS scheme and one Android variant, up to 40 non-generated changed files, and no modified custom native module.
Complex — €4,000
One mobile app in a monorepo plus directly referenced shared packages, or modified custom native/New Architecture integration; up to 100 non-generated changed files and up to two production variants per platform.
Generated files and lockfiles are excluded from the changed-file count. Both bands retain all listed deliverables, up to three critical flows, and one validation rerun. A workload within the overall caps that does not meet every Standard condition uses Complex.
More than 100 non-generated changed files, more than two production variants per platform, more than one mobile app, or more than three critical flows requires separate scope and price before purchase. Implementation is not included.
AI-aware verification
Verify outcomes, not claimed authorship.
ReleaseOps does not detect AI authorship. It verifies outcomes regardless of human or agent authorship and records declared AI usage without pretending to infer who wrote a change.
Review can cover the declared agent workflow, target diff, dependency and configuration changes, human approvals, tests agents claimed to run, independent reproductions, native/config drift, skipped platform changes, test relevance, secrets exposure, rollback readiness, and unsupported claims.
Evidence and acceptance
Every conclusion has a boundary.
Checks record commands, relevant logs, timestamps, environment, status, and evidence references. Statements are labeled observed when directly verified and inferred when reasoned from incomplete evidence.
Completion is measured against explicit acceptance criteria in the agreed scope. Unavailable evidence is recorded as a limitation or an unmet criterion, never silently assumed. The engagement includes one validation rerun against those criteria.
Exclusions
Release ownership stays with the buyer.
- Store approval.
- Zero-regression guarantee.
- Code changes and additional reruns.
- Store submission, legal advice, or compliance certification.
- Production deployment or emergency response.
The buyer retains release ownership, store submission authority, credentials, legal/privacy interpretation, and decisions on residual risk.