Supabase paywall

An open-source backend for developers: Postgres, auth, storage and APIs in one project.

Supabase

Add-ons sold where the problem shows up

Supabase surfaces paid add-ons inside the screens where you hit the limit (IPv4 in the connect modal, custom domains in settings) and backs them with clear usage and spend-cap pages.

B2BupsellpaywallMay 2025

01

Dedicated IPv4 add-on panel

A side panel explains the IPv4 add-on, prices it per database, and tells Free users they need a plan upgrade first.

Supabase: Dedicated IPv4 add-on panel
  1. 1

    Honest about need (working)

    "If you are connecting via the Shared connection pooler, you do not need this add-on" talks some users out of buying.

    Trust signals

  2. 2

    $0 vs $4.00 side by side (working)

    Two option cards show the free path and the paid one with "/ month / database" pricing.

    Anchoring

  3. 3

    Two purchases in one (not working)

    The $4 add-on is "unavailable on the Free Plan", so the real cost is a plan upgrade plus $4, and only the $4 is shown.

    Transparency

  4. 4

    Docs one click away (working)

    "About dedicated IPv4 addresses" links out for people who need more detail.

    Progressive disclosure

02

Connect to your project

The connection modal flags that the direct connection is not IPv4 compatible and offers the add-on right there.

Supabase: Connect to your project
  1. 5

    Problem flagged in context (working)

    "Not IPv4 compatible" with a red icon appears next to the connection string you are about to copy.

    Contextual timing

  2. 6

    Paid and free fix together (working)

    "IPv4 add-on" sits next to "Pooler settings", so users choose instead of being pushed.

    Default effect

  3. 7

    Moment of need (working)

    The string users came for is right there, so the upsell meets an active task.

    Time to value

  4. 8

    Detail folded away (working)

    "Some platforms are IPv4-only" stays collapsed until someone needs it.

    Progressive disclosure

03

Custom domains in project settings

General settings mix a Pro-plan add-on card with transfer and delete actions, under a persistent grace-period banner.

Supabase: Custom domains in project settings
  1. 9

    Price in the copy (working)

    "Custom Domains for an additional $10/month per domain" is stated before the upgrade click.

    Transparency

  2. 10

    Specific CTA (working)

    "Upgrade to Pro" names the plan, so there is no mystery destination.

    Clarity

  3. 11

    Faint warning banner (not working)

    "Grace period is over" in pale amber on yellow is easy to read past, though it describes a service cutoff.

    Visibility of system status

04

Billing: grace period and spend cap

The billing page explains the end of the grace period, the current Free plan and how the spend cap works.

Supabase: Billing: grace period and spend cap
  1. 12

    Date and consequence (working)

    "ended on 22 Oct, 2024" and "requests will respond with a 402 status code" are concrete for developers.

    Clarity

  2. 13

    Same warning, again (not working)

    The banner, the grace box and "This organization is limited by the included usage" repeat one message three times.

    Signal vs noise

  3. 14

    Spend cap explained (working)

    "You won't be charged any extra for usage" plus what happens instead removes fear of a surprise bill.

    Trust signals

  4. 15

    Plan is visible (working)

    "Free Plan" in green with "Change subscription plan" right below makes the current state obvious.

    Visibility of system status

Takeaways from Supabase

  1. Offer an add-on in the screen where the user hits the problem, next to any free workaround.
  2. State the add-on price in the copy, and say when a plan upgrade is also required.
  3. Say a warning once, clearly, instead of stacking banners that all say the same thing.