Back to Build, Automate & Deploy ↗.
Supabase provides the backend behind an app: a Postgres database, user authentication, file storage and other services. It is useful when your app needs to remember information and decide who is allowed to see or change it.
For example, a client portal needs more than a login page. It needs each client to see their own requests without exposing another client’s records. Supabase gives developers the pieces to build that properly; it does not automatically make every generated app secure.
What this offer includes
Supabase Pro for 1 year, activated with a coupon on your own account and the agreed organisation.
The current Pro plan includes 8 GB database disk per project, plus allowances including 100 GB file storage, 250 GB egress, 100,000 monthly active users and 2 million Edge Function invocations. Many usage allowances are pooled across the organisation rather than multiplied by every project you create.
Current Pro also includes 10 US dollars in monthly compute credits and daily database backups retained for 7 days. Compute credits do not roll over. Each project has its own compute resources, so creating several projects can increase costs even before the app has many users.
Confirm the redeemed organisation’s actual entitlement. A coupon covering the subscription does not promise unlimited infrastructure, additional organisations or every add-on.
A smarter way to use this: make the database reject the wrong user
Most beginners hide a button or filter records in the app interface and assume the data is protected. Row Level Security, or RLS, lets the database itself enforce which rows a user can access.
- Create a test table with an owner field tied to the authenticated user. Use sample data, not real client records.
- Enable RLS and define the permitted operations. Reading, creating, changing and deleting records need the appropriate policies; an update should also check that ownership cannot be changed improperly.
- Make two test accounts. Confirm the owner can perform the intended action and the other account cannot read or change that record, even through a direct request rather than the visible interface.
- Repeat while signed out. Test files and storage-bucket permissions separately; protecting a database row does not automatically protect a publicly accessible file.
- Keep those cases as repeatable tests before changing your schema or permissions. Ask a qualified developer to review policies when the app handles sensitive data.
This is particularly valuable for a portal or multi-customer app. It moves an important rule out of the appearance of the interface and into the data-access layer.
The cost-control detail worth checking first
Pro’s spend cap is enabled by default for covered usage, but it is not a universal bill ceiling. Compute, branching compute, read replicas, custom domains, point-in-time recovery and several other add-ons are outside its coverage.
Keep the cap on unless you understand why you are changing it. Check the actual list of exceptions and each project’s compute size. A temporary branch, extra project or test replica can still consume resources after you stop looking at it.
Monthly allowances are not a bank of unused capacity that grows forever. Monitor storage and egress as well as user count; a small number of users downloading large files can create meaningful traffic.
First setup
Choose the intended organisation and a suitable region. Build a small schema, enable the required permissions, and test authentication with two users. Set billing controls and alerts, then check backup and restore procedures.
A database backup is not automatically a backup of every file object and external service your app uses. Keep the recovery plan broad enough to restore the actual application, not only its tables.
Who it suits
Developers and technically supported founders building apps with structured data, authentication or file storage. It pairs with an app builder, but you still need to understand who owns the data and how access is enforced.
ShreeTools activation and support
Use the one-year own-account Pro coupon in the agreed organisation. Follow How 1-Year Coupon Activation Works ↗ for official checkout and any card requirement. Confirm the covered term, organisation plan, usage and renewal settings.
Extra resources and usage are your responsibility. Warranty follows the confirmed offer and Warranty, Support & Refund Policy ↗.
Official references
Current Pro allowances · Spend cap and its exceptions · Row Level Security
Vendor references checked 17 September 2026.
Message ShreeTools Support on WhatsApp for current availability and ordering →