
Manage Supabase
What you don't know !
Silent Waste
84%
of people lose money every month on unused services
Lack of Transparency
60%
of users feel lost facing cancellation terms
Budget Illusion
82%
of consumers underestimate the cost of their automatic withdrawals
Fear of Commitment
44%
of subscribers have experienced a 'commercial trap' experience
Legal Validation
All our letters are written by legal experts to guarantee their compliance.
Legal Commitment
We generate legally binding documents that your provider is obligated to honor.
Immediate Efficiency
Free yourself from your commitments in less than 2 minutes, directly online.
Budget Optimization
Regain control of your finances by stopping superfluous withdrawals.
Cancel Supabase: The Right Way
How to cancel supabase and reclaim your cloud database investment
What supabase is and why you might cancel
Supabase is an open-source backend-as-a-service platform that gives developers a hosted PostgreSQL database, authentication, storage, real-time features and edge functions without the overhead of managing servers yourself. It's designed to replace or complement traditional cloud database stacks by combining managed infrastructure with developer tooling in one place.
If you're reading this, you've likely decided that Supabase no longer fits your project needs, budget or technical direction. That's a practical decision, and Stopee understands that cancelling a development tool requires careful planning to avoid unexpected charges and data loss.
Why developers cancel supabase
Common reasons include migrating to a different database provider, sunsetting a project, reducing operational costs, or finding that usage fees have crept beyond your original estimates. Whatever your reason, you deserve a clear, step-by-step path to cancellation that protects your data and clarifies your financial obligations.
Key facts before you cancel
Supabase bills organisations on a monthly cycle combining a flat plan fee with variable compute and usage costs. Once you downgrade or cancel, the platform issues credits for unused time rather than cash refunds-meaning you won't receive monetary compensation for partial months. Your final invoice will include any unbilled usage from the billing cycle in which you cancel. Understanding these facts now prevents frustration later.
Supabase subscription plans and australian pricing
Below is a breakdown of Supabase's current plan structure with approximate Australian dollar (AUD) entry prices, converted from USD and subject to exchange-rate fluctuations.
| Plan | Typical entry price (AUD) | Key features | Best for |
|---|---|---|---|
| Free | A$0 | Basic database size, limited monthly active users (MAU), community support | Hobby projects and prototypes |
| Pro | A$37.50 approx | Higher MAU quota, expanded storage, email support, daily backups | Small production apps |
| Team | A$900 approx | Single sign-on (SSO), SOC2 compliance, extended backup retention, priority support with SLAs | Medium teams and regulated industries |
| Enterprise | Custom pricing | Dedicated support, custom SLAs, bring-your-own-cloud (BYO) options | Large organisations with unique needs |
Compute add-ons are billed hourly, while storage, egress and MAU overages are metered. This means your final invoice after cancellation may include usage charges from the most recent billing cycle.
Should you cancel supabase or downgrade instead
Before you commit to full cancellation, consider whether downgrading to the Free tier might preserve your options without ongoing charges.
When full cancellation makes sense
Cancel entirely if you're sunsetting the project, migrating permanently to another platform, or have no plans to return. Cancellation is also the right choice if you've experienced persistent billing problems or support delays that Stopee recognises as legitimate frustrations worthy of a fresh start with a competitor.
When downgrading is smarter
If you may revive the project later, downgrading to the Free tier preserves your data and project history without monthly charges. The Free tier includes basic database functionality-enough for development or occasional testing. You avoid the risk of permanent data loss and can return to a paid plan when needed.
For&against cancelling supabase
| Reason to cancel | Reason to downgrade instead |
|---|---|
| Project is permanently discontinued | You may need the project in 6-12 months |
| Switching to a competitor permanently | Running a small hobby project long-term |
| Recurring billing errors despite complaints | Usage costs exceeded expectations slightly |
| Unresolved support issues over multiple requests | You simply want to pause spend temporarily |
How to cancel supabase step by step
Supabase cancellation requires written notice to the company's registered office, including your account details and a clear statement of intent. Follow these steps to ensure your cancellation is processed correctly and documented for your records.
Step 1: gather your account and billing information
- Log into your Supabase account and navigate to your organisation settings
- Note your organisation name, registered email address and any project IDs associated with your account
- Download your most recent invoices and any billing statements from your billing dashboard
- These serve as proof of your account history if a dispute arises
- Note the invoice numbers and dates of your last three charges
- Export usage reports (storage, MAU, egress) from your project dashboard
- Record the final billing cycle dates and any outstanding usage charges
- Screenshot or export compute instance sizing and hourly usage logs
- Take note of your current billing period end date
- This determines when your charges officially cease
- Supabase will issue a final invoice for any usage accrued up to cancellation
Step 2: prepare your written cancellation notice
- Draft a clear, professional letter addressed to Supabase's registered office
- Include the full date and your contact details at the top
- Use formal language: "I hereby give notice to cancel my Supabase account"
- State your organisation name and primary email address associated with the account
- List all project IDs linked to your organisation
- This prevents confusion if Supabase has multiple records under your name
- Specify your intended cancellation date
- Allow at least 30 days from the letter date to give Supabase processing time
- Requesting cancellation at the start of your billing cycle minimises final charges
- Request written confirmation of cancellation and a final invoice showing zero balance
- This creates a clear audit trail for your records
- Sign the letter by hand or use a verified digital signature
Step 3: send your cancellation notice via tracked post
- Print your signed letter on plain white paper
- Address it to Supabase's registered office (you'll find this on their official website under "Company" or "Legal")
- Use the full legal entity name for Supabase
- Write the complete mailing address including country and postcode
- Send via Australia Post with tracking enabled (Registered Mail or Priority Mail with tracking)
- This ensures you have proof of posting and delivery date
- Keep your receipt and tracking number for your records
- Do not email your cancellation notice unless Supabase explicitly accepts email cancellations
- Email is easier to ignore or claim was missed
- Written tracked post creates enforceable proof
- Allow 14-21 business days for processing after delivery
Step 4: export your data before cancellation takes effect
- Access your Supabase project dashboard and navigate to the Database section
- Use the PostgreSQL export tool to download your full database as a SQL dump
- This captures all tables, schemas, functions and data
- Export any custom authentication rules, edge function code and environment variables
- Store these in version control (GitHub, GitLab) or a secure backup location
- Download any files stored in Supabase Storage buckets
- Use the Supabase CLI to bulk-download storage contents locally
- Complete all exports at least 5 days before your intended cancellation date
- This gives you time to verify data integrity before access is revoked
Step 5: monitor for confirmation
- Watch your email for a response from Supabase support within 14 days of your letter's delivery
- Expected replies include acknowledgement of your cancellation request and a timeline for closure
- If you receive no reply within 14 business days, send a follow-up email citing your tracking number and cancellation request date
- Reference Stopee's guidance if you need reassurance about what constitutes reasonable response time
- Once your account is cancelled, verify that you no longer see active projects in your dashboard
- Confirm that no new charges appear on your payment method
- Request a final invoice showing a zero balance
- This document proves the account is closed and all charges are settled
Understanding supabase refunds and credits
Supabase does not offer monetary refunds for unused time on monthly plans. Instead, the platform issues account credits that can be applied to future charges, but these credits expire and are non-refundable under Supabase's Terms of Service.
How credits work after cancellation
If you cancel mid-month, Supabase calculates the daily rate for your plan and credits the unused portion back to your account. You can apply these credits to pay for a resumed subscription, additional compute resources, or storage upgrades. However, if you cancel permanently and do not return within a specified period, those credits simply vanish-they cannot be converted to cash.
Your rights under australian consumer law
The Australian Consumer Law (ACL) protects you when goods or services fail to meet consumer guarantees. If Supabase has failed to provide services as described, billed you incorrectly, or refused to provide support despite your paid plan, you may be entitled to a refund regardless of their Terms of Service.
- Service not as described: If Supabase promised certain uptime, support response times or features and failed to deliver, the ACL entitles you to compensation
- Misleading billing: If charges were applied without clear disclosure or your consent, you can dispute them
- Failure to refund: If you cancelled and Supabase continues charging, this is a breach of the ACL and you can escalate to the Australian Competition and Consumer Commission (ACCC)
Common mistakes when cancelling supabase
Cancelling a production-critical service can feel stressful, and mistakes often happen when you rush. Take a breath-Stopee has compiled the most frequent errors so you can avoid them.
Stopping payment without formal notice
Removing your payment method or stopping a payment does not cancel your Supabase account. Instead, it triggers a failed payment notice, and Supabase may suspend your project or pursue collection action. Always send formal written cancellation notice before stopping payment.
Forgetting to export your data
Once your account is deleted, Supabase's data retention policies may delete your database within 30-90 days. If you need that data later, you cannot recover it. Export everything before cancellation is finalised.
Not keeping copies of invoices and correspondence
If a billing dispute arises after cancellation, your proof of invoices, payment receipts and cancellation letters is your only evidence. Store these documents for at least two years-the time limit for credit card disputes and consumer claims under Australian law.
Cancelling during a billing cycle without clarity on final charges
Your final invoice will include usage costs accrued between your last invoice date and your cancellation date. If you cancel on day 15 of a 30-day cycle, you'll be charged for 15 days' usage plus any compute overages. Align your cancellation date with billing cycle ends if possible, or budget for a partial month charge.
Ignoring support response delays
Supabase support times vary by plan. Pro plan customers report slower response times (5-10 business days) compared to Team or Enterprise accounts (1-2 business days). If you're on a Pro plan, don't expect instant confirmation-allow 14-21 days and follow up if needed.
What happens after your supabase account is cancelled
Once Supabase confirms your cancellation, several changes take place automatically. Understanding this timeline helps you plan your final data migration and avoid surprises.
Immediate access restrictions
Within 24 hours of cancellation, your project dashboard becomes read-only and you cannot deploy new functions, modify databases or update authentication rules. Your existing projects remain visible but inactive.
Data retention and deletion timeline
Supabase retains your data for 30 days after cancellation, allowing you to retrieve it if you change your mind. After 30 days, your database and storage buckets are queued for deletion. After 90 days, all data is permanently destroyed. If you think you might return, download your database backup before the 30-day window closes.
Final invoice and credit settlement
Your final invoice appears in your billing dashboard within 7-10 days of cancellation confirmation. This invoice includes all usage charges through your cancellation date. Any remaining account credits are applied automatically; if credits exceed the final invoice amount, the balance is forfeited (non-refundable).
Lingering charges or unexpected activity
Monitor your payment method for 60 days after cancellation. In rare cases, Supabase applies additional charges for compute overages or storage that were not invoiced immediately. If you see unexpected charges after cancellation is confirmed, contact Stopee's escalation guide for next steps, and file a chargeback dispute with your bank if needed.
Documentation checklist for your supabase cancellation
Before you send your cancellation letter, gather and organise the documents below. This checklist ensures you have everything needed to prove your cancellation and protect yourself if disputes arise later.
| Document | Why you need it |
|---|---|
| Copy of signed cancellation letter | Proves you sent formal notice and its content |
| Australia Post tracking receipt and number | Proves delivery date and method; required for escalation |
| Last 3 months of invoices | Documents your billing pattern and account history |
| Final invoice after cancellation | Confirms all charges are settled and account is closed |
| Database export (SQL dump) | Preserves your data in case you need it later |
| Written confirmation of cancellation from Supabase | Proof the account is officially closed |
Store these documents in a secure folder (cloud backup or external drive) for at least two years. If you file a dispute with your bank or the ACCC, these records will be your strongest evidence.
Real user experiences with supabase cancellations
Community forums and developer discussions reveal patterns in how Supabase handles cancellations and what problems users face most often.
What users praise about supabase
Developers consistently highlight the platform's ease of use, responsive feature rollouts and clear pricing tiers. Many users appreciate the Free tier for experimentation and find the Pro plan reasonable for small apps. Teams and enterprise customers praise priority support and dedicated resources.
Common complaints during and after cancellation
Users report billing clarity issues, particularly around compute charges appearing unexpectedly. Some describe delays resolving billing errors-Pro plan customers especially note slower response times compared to Team or Enterprise SLAs. A few users report rare cases of double billing that took weeks to resolve. Support response delays for billing queries (5-10 days for Pro, 1-2 days for Team) frustrate developers expecting faster resolution.
Lessons from user feedback
Recurring themes emerge: monitor your usage dashboard weekly to catch overages early, expect credits rather than cash refunds, and assume slower support response times unless you have an SLA. One user noted that requesting cancellation during their monthly billing cycle actually delayed the final charge cutoff, costing them an extra week of fees. Plan your cancellation timing carefully.
Supabase billing comparison and what to watch
Understanding how Supabase's billing structure compares to your actual usage helps you make an informed cancellation decision and choose your next platform wisely.
| Billing element | How it works | Impact on cancellation |
|---|---|---|
| Plan fee (flat monthly) | Pro A$37.50, Team A$900, Enterprise custom | Charged regardless of usage; pro-rated refund as credits only |
| Compute (hourly metered) | Charged per CPU-hour; instances run 24/7 unless you stop them | Can accumulate unexpectedly; final invoice may include unbilled hours |
| Storage (metered) | Charged per GB stored | Overages billed; credits issued but not refunded as cash |
| MAU (monthly active users) | Charged per user once you exceed quota | Can spike unexpectedly if your app gains users; monitor weekly |
| Egress (data transfer out) | Charged per GB transferred from Supabase | High-traffic apps incur surprise charges; factor this into cost review |
| Credits (issued after cancellation) | Applied automatically to next invoice; non-refundable if unused | Do not count as cash refund; you forfeit if you do not return |
If your cancellation is driven by unexpected billing, review this table carefully. Many developers cancel after discovering compute or egress charges they didn't anticipate-often preventable by right-sizing instances or monitoring usage dashboards.
Your australian consumer law rights and escalation
The Australian Consumer Law provides protections beyond what Supabase's Terms of Service claim. If the company refuses your cancellation, withholds a refund you believe is fair, or continues billing after you've cancelled, you have legal recourse.
When you can claim a refund under the ACL
You're entitled to a refund or credit if Supabase failed to provide the service as described, billed you misleadingly, or refused support despite your paid subscription. The ACL overrides any clause in Supabase's Terms that disclaims liability for these failures.
How to escalate if supabase refuses
- Send a formal dispute letter citing the specific ACL breach
- Example: "Your platform failed to provide promised email support within 48 hours, in breach of the Australian Consumer Law section X"
- Request a response within 14 days and set a deadline for resolution
- If Supabase does not respond or refuses, file a complaint with the Australian Competition and Consumer Commission (ACCC)
- Visit accc.gov.au and use their online complaint form
- Attach all correspondence, invoices and proof of the breach
- The ACCC investigates and can impose penalties or force corrective action
- If the amount is under A$20,000, you can pursue the claim in small claims tribunal or district court
Key takeaways and your next steps
Cancelling Supabase requires careful planning, but the process is straightforward once you understand the steps. You now know how to gather your information, send formal written notice, export your data, and protect yourself under Australian law if problems arise.
Start by downloading your database export and gathering your invoices today. Then draft your cancellation letter, send it via tracked post, and allow 14-21 days for processing. Monitor your payment method for 60 days after confirmation to catch any lingering charges.
If Supabase refuses a refund you believe is fair or continues charging after cancellation, do not hesitate to escalate to the ACCC. Your consumer rights are protected under Australian law regardless of what their Terms of Service claim.
Stopee has helped thousands of consumers cancel services cleanly and recover unfair charges. Whether you're switching to a competitor like Firebase, AWS Amplify or Vercel, or sunsetting your project entirely, you deserve a smooth, documented exit. Use this guide to protect yourself every step of the way, and remember that Stopee is here to support your consumer rights as you take control of your subscriptions.
How to contact supabase to confirm cancellation
Use the details below when sending your formal cancellation notice. Always send via tracked post to ensure proof of delivery.
Supabase registered office address: You will find the official legal mailing address on Supabase's website under "Company," "Legal," or "Contact." Common addresses include their San Francisco headquarters or their official business registration. Confirm the correct address on their official site before posting your letter, as office addresses can change.
Email support (reference only): While email is faster, it does not create the same legal proof as tracked post. Use email only as a secondary follow-up after you've sent your formal letter via post.
For billing-specific disputes, reference your invoice numbers and project IDs in all correspondence. Keep copies of everything you send and receive.