Migrate from PieSocket to Vask (Laravel). Drop-in host swap.

PieSocket and Vask both speak the Pusher protocol. A Laravel app using the pusher broadcast connection keeps its events, Echo subscriptions, and channel auth logic; only the host and credentials change.

Minimal cutover

Save the current PieSocket values first. Then update the env block. If your app still uses BROADCAST_DRIVER, keep that name and set it to pusher.

BROADCAST_CONNECTION=pusher
-PUSHER_APP_ID=your_piesocket_app_id
-PUSHER_APP_KEY=your_piesocket_key
-PUSHER_APP_SECRET=your_piesocket_secret
-PUSHER_HOST=ws.piesocket.com
+PUSHER_APP_ID=your_vask_key
+PUSHER_APP_KEY=your_vask_key
+PUSHER_APP_SECRET=your_vask_secret
+PUSHER_HOST=wss.vask.dev
 PUSHER_PORT=443
 PUSHER_SCHEME=https
-PUSHER_APP_CLUSTER=v3
+PUSHER_APP_CLUSTER=mt1

 VITE_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
 VITE_PUSHER_HOST="${PUSHER_HOST}"
 VITE_PUSHER_PORT="${PUSHER_PORT}"
 VITE_PUSHER_SCHEME="${PUSHER_SCHEME}"
 VITE_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"

If your SDK asks for an app id, use the Vask app key. Vask does not issue a separate customer-facing app id.

Rollback

Put the saved PieSocket values back, redeploy or rebuild the client bundle if VITE_PUSHER_* values are embedded, and clear config cache. Rollback is only credentials and endpoint state.

Laravel package shortcut

composer require vask/laravel
php artisan vask:install

The installer writes the same Pusher-compatible env values and runs php artisan vask:doctor. Source: github.com/vask-dev/laravel · packagist.

Server publish

Confirm config/broadcasting.php reads host from env:

'pusher' => [
    'driver' => 'pusher',
    'key' => env('PUSHER_APP_KEY'),
    'secret' => env('PUSHER_APP_SECRET'),
    'app_id' => env('PUSHER_APP_ID'),
    'options' => [
        'cluster' => env('PUSHER_APP_CLUSTER'),
        'host' => env('PUSHER_HOST'),
        'port' => env('PUSHER_PORT', 443),
        'scheme' => env('PUSHER_SCHEME', 'https'),
        'encrypted' => true,
        'useTLS' => env('PUSHER_SCHEME', 'https') === 'https',
    ],
],

Replace any hardcoded ws.piesocket.com host with env('PUSHER_HOST').

Client subscribe

Echo should read the same Vite env values:

window.Echo = new Echo({
    broadcaster: 'pusher',
    key: import.meta.env.VITE_PUSHER_APP_KEY,
    cluster: import.meta.env.VITE_PUSHER_APP_CLUSTER,
    wsHost: import.meta.env.VITE_PUSHER_HOST,
    wsPort: import.meta.env.VITE_PUSHER_PORT,
    wssPort: import.meta.env.VITE_PUSHER_PORT,
    forceTLS: (import.meta.env.VITE_PUSHER_SCHEME ?? 'https') === 'https',
    enabledTransports: ['ws', 'wss'],
});

Private and presence channels

Keep routes/channels.php, /broadcasting/auth, and existing private- / presence- channel names. The auth signature stays Pusher-compatible; only the secret used for signing changes.

Verify

1. Deploy the env change to staging.
2. Confirm the browser opens a WebSocket to wss.vask.dev, not PieSocket.
3. Trigger one Broadcast event and verify the client receives it.
4. Verify one private or presence subscription returns 200 from /broadcasting/auth.

Gotchas

• Host and cluster mismatch. PUSHER_APP_CLUSTER=v3 does not route Vask traffic. PUSHER_HOST=wss.vask.dev is the important value.
• Mixed credentials. A Vask key with a PieSocket secret, or the reverse, usually appears as publish failures or private-channel 403s.
• Stale Vite bundle. The browser may keep connecting to PieSocket until the client bundle is rebuilt.
• Auth endpoint assumptions. Custom auth endpoints can stay, but they must sign with the Vask secret after the env swap.

Where to go next

• Read the PieSocket vs Vask comparison for architecture and pricing context.
• Check the Laravel docs for advanced setup.
• Run the fan-out calculator if cost is the migration driver.

Get going

Keep the channel code. Swap host and credentials. Verify authenticated channels before production traffic moves.