supapulseGetting startedMoving from Pulsora
Moving from Pulsora
Pulsora is now Supapulse. What changed, what keeps working, and how to update your install.
Pulsora is now called Supapulse, and it lives at supapulse.app. Your account, websites and data are the same. Nothing you already installed stops working.
What keeps working
- The old domain.
pulsora.costill accepts events, API calls, MCP connections and Stripe webhooks, and its pages redirect tosupapulse.app. - The old packages.
@pulsora/core,@pulsora/reactand@pulsora/revenuestay on npm. They're deprecated and won't get new versions. - The old names in the new packages.
window.pulsora,data-pulsora-ignore,PulsoraProvider,usePulsoraand thePulsora*types still work as aliases. - Stripe metadata. Keys starting with
pulsora_andpulsora_<session id>client references are still read.
What to update
Swap the package names:
npm uninstall @pulsora/core @pulsora/react @pulsora/revenue
npm install @supapulse/core @supapulse/react @supapulse/revenueThen update your imports:
| Before | After |
|---|---|
@pulsora/core | @supapulse/core |
PulsoraProvider | SupapulseProvider |
usePulsora() | useSupapulse() |
window.pulsora | window.supapulse |
data-pulsora-ignore | data-supapulse-ignore |
pulsora_session_id in Stripe metadata | supapulse_session_id |
If you use the script tag, change the URL to https://cdn.jsdelivr.net/npm/@supapulse/core@1/dist/browser.js. If you point MCP clients or webhooks at pulsora.co, move them to supapulse.app when it suits you.