Appearance
Automatic organisation savings
Open Savings under Organisation. The dashboard automatically estimates the OTA service fees your recorded usage would cost on Revopush, compared with PushOTA’s $0 software licence fee. All amounts are in US dollars (USD). No bill, provider, currency or cost form needs to be filled in. Every organisation member sees the same read-only comparison.
What the number means
Estimated OTA fees saved = estimated Revopush monthly fee for recorded usage − PushOTA software licence fee ($0).
The estimate includes Revopush’s free allowance. If your measured usage fits that allowance, the estimated saving is $0.00. It does not automatically assume you would buy a paid subscription. The lowest estimated cost across the published Starter, Startup, Growing, Business and Professional monthly plans is selected, including their published overage rates.
This is a comparison of provider service fees, not proof of money you previously spent or net profit. Hosting, backups, network charges, maintenance, taxes, negotiated contracts and other services are not subtracted or inferred. The dashboard makes no annual or lifetime savings claim.
Usage is measured automatically
The comparison uses the current UTC calendar month, not a rolling 30-day window:
- Active installations: distinct app installations that successfully checked for an update, including checks where no update was available. Repeat checks from the same installation count once in that app for the month. Switching between Staging and Production does not create another installation.
- Installations with downloads: distinct identified installations reporting a downloaded update. Multiple releases downloaded by one installation do not turn it into multiple active installations.
- Download reports: identified download reports are deduplicated for the app, package content and installation within the month, including promotion of the same package between deployments. Reports without an installation ID are shown separately and never invented as distinct devices.
- Artifact deliveries and data: the server records completed API package transfers and imports completed CloudFront deliveries, including cache hits. CDN logs are checked every 15 minutes and may arrive later from AWS. Requests are deduplicated, so retries of log collection do not inflate the total. Partial downloads, interrupted transfers and ambiguous attribution are conservatively excluded and surfaced as coverage warnings. These observations do not prove installation or constitute a provider invoice. Traffic through an independently configured cache is outside this meter unless it is integrated explicitly.
An installation is an app installation identifier, not a person or a physical phone. Different apps and reinstallations can have different identifiers. Public client identifiers are client-reported; this is operational measurement, not billing-grade device attestation. Raw installation identifiers are not stored by the usage meter; app- and month-scoped hashes are stored instead.
The provider calculation uses active installations and measured delivery data. Downloads are useful supporting context; publishing a release alone does not count as a new device.
Coverage and history
The panel states when measurement began. Existing bounded client reports are not converted into a fictional historic monthly audience or bandwidth total. The older Downloads card may therefore show reports from before the new Savings meter began. The estimate covers recorded usage so far and does not extrapolate the rest of the month.
Missing identifiers, measurement limits or collection errors are surfaced as coverage warnings. Incomplete figures are not represented as a verified full-month bill. Usage survives a server restart, and organisation totals remain isolated from other organisations. The meter retains the current month and the preceding 12 months. Restarting or re-upgrading a metered database marks the current month as resumed tracking: the system cannot certify whether a preceding server version served unmetered traffic during that interval. Existing counters remain intact, but such gaps are never reconstructed.
Price assumptions
The published Revopush prices were checked on 11 November 2026. This estimate uses monthly list prices, decimal GB (1,000,000,000 bytes), proportional overage rates and a final total rounded up to the nearest cent. The public page does not establish every invoicing rounding rule, so a real invoice may differ. Annual discounts, mid-month subscription proration, tax and Enterprise contracts are excluded. The selected plan’s base fee and usage components are shown with the pricing date and source.
Prices are a versioned reference; they are not fetched from a vendor’s billing account at runtime. See Revopush pricing, its billing documentation, and our dated five-provider comparison.
Upgrade from the earlier manual comparison
The manual cost-entry form and its write endpoint have been removed. Previously entered figures do not affect automatic estimates. Existing stored figures are retained for server rollback compatibility; they are not used or exposed by the new Savings response.