Integration guides

Migrating from Pusher

Your Pusher code keeps working. Point the libraries at Hibira, swap the credentials, and move traffic over at your own pace.

1. Create an app

   Sign up, create an app and copy its ID, key and secret. List the domains your site runs on as allowed origins. Start free

2. Point your server library at the new host

   Every official server library takes a host option. In Laravel, set PUSHER_HOST, PUSHER_PORT and PUSHER_SCHEME in .env.

   const Pusher = require('pusher');
   
   const pusher = new Pusher({
     appId: 'YOUR_APP_ID',
     key: 'YOUR_APP_KEY',
     secret: 'YOUR_APP_SECRET',
     host: 'ws.hibira.io',
     port: '443',
     useTLS: true,
   });

3. Point your clients at the new host

   Channel names, events and your authorization endpoint stay the same.

   const pusher = new Pusher('YOUR_APP_KEY', {
     cluster: 'ap',
     wsHost: 'ws.hibira.io',
     wsPort: 443,
     wssPort: 443,
     forceTLS: true,
     enabledTransports: ['ws', 'wss'],
   });

4. Recreate your webhooks

   Add your webhook URL on the app page. Requests carry the same X-Pusher-Key and X-Pusher-Signature headers, so your handler verifies them unchanged.

5. Switch over without downtime

   For a while, publish each event to both services from your server. Release the client change, wait until old clients have updated, then remove the Pusher credentials.

Feature comparison

Missing something you use on Pusher? Contact sales

All integration guides →