Migrate from Firebase Extensions

Firebase Extensions is shutting down. Here's where each one goes

Firebase Extensions shuts down on 31 March 2027, taking the Stripe payments extension and the RevenueCat in-app purchase extension with it. Anythink does both of those jobs natively, plus the workflow automation extensions normally fill in.

Start free Read the docs

The same task, three ways

Replace the Stripe extension: sell a monthly plan with a 14-day trial.

The Anythink dashboard

Create the plan. It syncs to Stripe once you have connected it.

The Anythink CLI

Create the plan through the API, once Stripe onboarding is done.

$ anythink pay connect$ anythink fetch /integrations/anythinkpay/subscription-plans \--method POST --body '{"plan_name":"pro-monthly",$   "name":"Pro Monthly","description":"Full access",$   "amount":9.99,"currency":"gbp",$   "billing_interval":"month","trial_period_days":14}'$ anythink pay status

✓Stripe onboarding started
✓Plan Pro Monthly created: £9.99 a month, 14-day trial
✓Stripe account status shown

Claude, through MCP

Describe the plan in plain English.

you › “Replace our Firebase Stripe extension: set up a Pro Monthly plan at £9.99 a month with a 14-day free trial, and tell me whether our Stripe account is ready to take payments.”

✓Created plan Pro Monthly at £9.99 a month
✓Added a 14-day trial
✓Checked the Stripe account status
✓Told you what is left to finish onboarding

Anythink vs Firebase + Extensions

Capability	Anythink	Firebase + Extensions
Subscription paymentsFirebase's Stripe payments extension, shutting down 31 March 2027	Built in	Add-on, extension or DIY recipe
Apple in-app purchasesFirebase relies on the RevenueCat extension	Built in	Add-on, extension or DIY recipe
Email on record writeFirebase's Trigger Email extension	Built in	Add-on, extension or DIY recipe
Search, including facets and geo	Built in	Add-on, extension or DIY recipe

● Built in◐ Add-on, extension or DIY recipe– Not available

"Addon" reflects Firebase's own documented reliance on Extensions, a third-party marketplace, for these jobs rather than a native product feature.

The job each extension did, built in

Firebase Extensions wired third-party add-ons into Cloud Functions. Anythink does the same jobs natively, so there's nothing external to re-install after the shutdown.

Stripe payments, without the extension

AnythinkPay handles subscription plans, offer codes, payment methods, charges, refunds and Stripe Connect directly — no extension to install, version, or lose when Extensions closes.

Apple in-app purchases, natively

Apple IAP verification runs against the real App Store Server API, is idempotent on renewals, and binds each purchase to the buying user so a replayed transaction can't be claimed by someone else. This is the job the RevenueCat extension did.

Trigger Email, as a workflow step

The Firebase "Trigger Email" extension watched a collection and sent an email on write. A Send an Email step on an Event-triggered workflow does the same thing, with the record's fields available to the template.

Search, without an Algolia extension

Search is a built-in, Meilisearch-backed endpoint per entity, including facets, geo filters and vector similarity — not a third-party service wired up through an extension and kept in sync by a Cloud Function.

Stripe payments, without the extension

AnythinkPay handles subscription plans, offer codes, payment methods, charges, refunds and Stripe Connect directly — no extension to install, version, or lose when Extensions closes.

01 / 04

Trigger Email, rebuilt as a workflow

The most common extension, as a workflow step

create the workflow.sh

anythink workflows create \
  --name "Welcome email" \
  --trigger Event \
  --entity users \
  --event EntityCreated \
  --enabled

Moving off Extensions before March 2027

Move payments off the Stripe extension

Recreate your products and prices as AnythinkPay subscription plans. The extension's Firestore-synced subscription documents become AnythinkPay subscription records, and your app reads entitlement from the /me endpoints instead of a Firestore listener.

Move Apple IAP off the RevenueCat extension

Point your app's purchase verification at Anythink instead of RevenueCat's endpoint. Verification, renewal handling and ownership binding are built in, so there's no separate service to keep paying for once Extensions closes.

Rebuild event-driven extensions as workflows

Anything that used to run as "on document write, do X" — send an email, call an API, update a related record — becomes an Event-triggered workflow with the matching action step. No Cloud Functions runtime to provision or keep patched.

Frequently Asked Questions

When does Firebase Extensions shut down?

31 March 2027. After that date, extensions can't be installed or edited, which affects the Stripe payments extension and the RevenueCat in-app purchase extension in particular, since both are third-party add-ons rather than native Firebase features.

Does Anythink support Apple in-app purchases without RevenueCat?

Yes. Apple IAP verification is built in: it calls Apple's App Store Server API directly, is idempotent so renewals don't create duplicate entitlements, and binds a purchase to the buying user to block replay from a different account.

What replaces the Trigger Email extension?

A workflow with an Event trigger (on a record being created, updated or deleted) and a Send an Email step. The record's fields are available to the email template through the same variable syntax used everywhere else in a workflow.

Is there a direct replacement for every Firebase extension?

This page covers the extensions teams rely on most: payments, in-app purchases, email when data changes, and search. Most other extensions map to a workflow: react to a record change or a schedule, call an API, run a script, or use a connected integration. Tell us which extension you use and we'll show you how to rebuild it.

Still have questions?

Get in Touch

Ways to build with it

The dashboard, the CLI, MCP and the SDK, plus guides for moving from other platforms.

Solution

Content Management

Anythink works as a headless CMS: model content types, edit them in the Anythink dashboard, and serve them to your website through a public REST API.

Solution

Flexible Data Views

Switch any entity between a grid, a kanban board, a calendar, a map and charts in the Anythink dashboard, all on the same records your API serves.

Solution

Branded dashboard

Brand the Anythink dashboard with your colours, logos, corner radius and menus, and send system email from your own verified domain and sender address.

Solution

TypeScript SDK

The Anythink SDK is an open source React library for sign-in and sessions: an auth client, a provider, a useAuth hook, and a base class for authenticated requests. Data calls go through the REST API directly — there's no hidden query layer to learn.

Solution

Anythink CLI

The open source Anythink CLI runs a whole project from the terminal: entities, fields, data, workflows, roles, users, files, search, secrets and integrations.

Solution

AI & MCP

Build your backend in a conversation, from Claude Code, Cursor or the AI chat in the Anythink dashboard. The same MCP tools reach the whole CLI, from entities and fields to workflows, roles, secrets and payments.

Who it's for

How founders, agencies and enterprise teams use Anythink.

Use Case

For Founders

Anythink gives founders sign-in, a REST API, subscriptions, workflows and an operations dashboard in one project, from first prototype to paying customers.

Use Case

For Enterprise

Anythink gives enterprise teams a managed backend with roles, row-level security and encrypted secrets, on a dedicated Kubernetes cluster if you need one.

Use Case

For Agencies

Anythink gives agencies a project per client, a branded dashboard to hand over, and a CLI that copies your template project into each new client project.