Postclic premium unlimited: promotional offer at $1.61 for 48h, then $87.71 per month without commitment

Cancellation service #1 in Australia
Heroku is a managed platform-as-a-service that runs applications in isolated containers called dynos and provides managed data services such as Postgres and key-value stores. It targets developers and teams who want to deploy and scale apps without operating raw infrastructure. Heroku bills for compute, storage and add-ons on a usage or plan basis; some compute tiers are metered by the second while selected entry tiers use flat monthly fees.
From a financial perspective, Heroku is positioned as a convenience-first offering: it reduces operational overhead but moves costs from capex to recurring opex. That trade-off is central when deciding whether to keep, downgrade or cancel a subscription.
Heroku’s runtime billing uses a mix of metered hourly/second-based charges for most dynos and flat monthly fees where specified (for example, Eco dynos are a flat low-cost option with a shared hours pool). Usage pages state per-hour rates and monthly caps for each dyno family and explain that many charges are prorated to the second.
In financial terms: expect a final invoice that reflects any usage through the billing cut-off and possible charges for data services or add-ons that were active in that period. Certain low-cost plans (Eco) can be charged as a full month even if subscribed mid-cycle.
| Plan (typical) | Typical AU price (approx) | Notes |
|---|---|---|
| Eco dynos (shared hours) | A$7.50/month (approx) | Flat monthly pool for 1,000 hours; charged as a monthly fee for the month subscribed. Converted from US$5 using mid-market USD/AUD ~1.497. |
| Basic / hobby-size dynos | A$10 - A$11/month (approx) | Metered rates with low monthly caps; converted from published per-hour caps. |
| Standard / production dynos | A$37 - A$75/month (approx) | Metered to the second; heavy use will approach published monthly caps. See dyno size page for specifics. |
| Performance / enterprise dynos | Varies (typically A$200+ / month per dyno, approx) | Enterprise-class pricing and limits; actual AU cost depends on USD list and exchange. |
Public reviews and community threads show a mix of experiences. Many users praise Heroku for ease of deployment and developer ergonomics, but billing and cancellation show recurring negative feedback focused on unexpected charges and slow support responses. Trustpilot and community threads contain numerous reports of ongoing billing after users believed they had ended services and difficulties securing refunds.
Representative paraphrased feedback from customers includes: "I was charged for months after I thought everything was closed" and "support responses were slow or automated, making dispute resolution lengthier than expected." These direct sentiments appear repeatedly in third-party reviews.
Recurring issues identified by reviewers: unclear triggers for billing (residual add-ons or services), prorated versus flat fees, and delays in refund handling. From a consumer-rights and budgeting perspective, these patterns create cashflow risk if not monitored.
Practical takeaway: treat Heroku charges as ongoing operational costs until you have documented confirmation that all billable resources and invoices are closed. Keep a timeline of invoices and communications for dispute purposes.
Considering that Heroku converts infrastructure costs into monthly operational charges, the core financial question is whether the platform’s convenience justifies the recurring spend. Calculate a monthly all-in cost (dynos + data + add-ons) and compare to self-managed or alternative managed platforms.
From a financial perspective: if the Heroku monthly run rate materially exceeds the estimated cost of a self-managed cloud VM plus your engineering time, cancellation or migration is a valid optimisation. Include migration and data transfer time as part of the upfront cost when modelling break-even.
| Alternative | Typical pricing note (source) | Cost posture |
|---|---|---|
| Vercel | Pro plans start from US$20/user; free hobby tier for static deployments. Convert to AU as needed. | Often cheaper for frontend frameworks and serverless functions; metered model for advanced features. |
| Render | Compute billed with per-second/prorated usage; community notes on pricing change in 2023. | Comparable alternatives for full-stack apps; savings depend on resource profile. |
| Fly.io | Community threads show variable billing; features geared to distributed apps. | Can be cost-efficient for certain workloads but watch for unexpected network/IPv4 costs. |
Heroku’s public documentation and community resources indicate that refunds are handled case-by-case and that final invoices may include charges accrued through the billing period. Expect proration rules to apply where stated and some flat-fee exceptions for entry tiers.
Under Australian Consumer Law, consumers retain guarantees for digital services and may be entitled to remedies if a service is not supplied as described or cannot be accessed. For Heroku this can be relevant when a paid service fails to deliver core functionality or if billing is misleading. Lodging a formal complaint with the relevant regulator or seeking dispute resolution are options when direct resolution fails. Keep any evidence that demonstrates non-delivery or misleading conduct.
If a charge appears incorrect, financial escalation options typically include raising a formal billing dispute with your payment provider and providing documentation. Monitor statements for recurring entries and, where appropriate, consider temporarily blocking the payment method if unauthorised continued billing is suspected. Keep in mind that blocking a payment method may affect contracted services.
For larger commercial customers, invoice disputes and chargeback routes can be more formal and contract-driven. Maintain a clear cost-recovery calculation when seeking refunds or credits so the vendor sees the quantifiable impact.
After a cancellation or final account change, act immediately to protect cashflow and operations: reconcile the final invoice against your expected costs and archive all invoices and export logs for at least the duration recommended by your finance or compliance team.
From a budgeting perspective, reintegrate the recurring cost into your forecast and compare realised savings against migration or re-provisioning costs. If you migrated workloads, maintain a short-term monitoring period to confirm traffic, latency and cost assumptions.
In terms of value: if Heroku’s convenience previously justified the fee but your usage profile has changed, document the non-recurring migration costs and the ongoing opex savings to support the decision. Consider negotiating terms or volume discounts if you return at scale.
Final actionable checklist:
Key references used for pricing, billing mechanics and customer reviews: Heroku pricing and usage documentation; third-party user reviews and billing guides; mid-market USD/AUD exchange data for approximate AU price conversions; and Australian consumer guidance on digital services.
Already sent a letter? Enter its tracking number to see its proof of dispatch and certified timestamp.
Written by Ethan Martin
Digital-law graduate · 4 years experience
Graduate in digital law and passionate about secure written communication, I have been writing guides on certified mail and electronic registered delivery for 4 years.