Your own Pusher-like WebSocket hub.
RealtimeHub gives your team a self-hosted realtime control plane for apps, channels, event publishing, frontend subscriptions, and debugging — without external message-day pricing.
Frontend
<script src="https://realtime.company.com/sdk/realtime.js"></script>
<script>
const realtime = RealtimeHub.init({
key: "app_key",
host: "realtime.company.com"
});
realtime.channel("orders")
.listen("OrderUpdated", (data) => {
console.log(data);
});
</script>Backend
Http::withHeaders([
'X-App-Key' => env('REALTIME_APP_KEY'),
'X-App-Secret' => env('REALTIME_APP_SECRET'),
])->post('/api/events', [
'channel' => 'orders',
'event' => 'OrderUpdated',
'data' => [
'order_id' => 1024,
'status' => 'paid',
],
]);What is RealtimeHub?
A simple realtime layer your developers will actually use.
Instead of setting up Pusher, managing limits, sharing keys manually, or debugging websocket behavior project by project, your team gets one internal place to create realtime apps and publish events.
Create apps
Generate app keys for each project, staging app, production app, or internal tool.
Publish events
Send backend events to subscribed browser clients through clean API endpoints.
Inspect logs
See event payloads, channels, timestamps, app usage, and delivery history.
Use simple SDK
Frontend developers connect with one script and listen to channels like Pusher.
How to use
From zero to realtime in minutes.
The flow is intentionally close to Pusher: create an app, use the generated key, subscribe on the frontend, and publish events from the backend.
Create realtime app
Create one app for each project or environment, like Project Staging or FirstCare Production.
Copy app keys
Use the generated key and secret in the frontend and backend integrations.
Subscribe to channel
Add the script to your page and listen for events on public or private channels.
Publish event
Trigger websocket events from Laravel, Node, PHP, mobile backend, or any HTTP client.
Why it was created
Built for teams tired of paying for basic realtime plumbing.
Many internal products only need predictable realtime features: notifications, progress updates, live dashboard refresh, chat events, payment status changes, and admin alerts. RealtimeHub gives your company a reusable websocket layer that can be used across projects without recreating the same setup again and again.
No vendor message-day limits
Usage depends on your server capacity, not a third-party pricing tier.
Simple developer onboarding
Copy a script, use a key, subscribe to a channel, and start listening.
Centralized control
Manage apps, secrets, origins, events, and logs from one Laravel dashboard.
Advantages
Designed for daily development, not forced documentation.
Fast testing
Test chat, notifications, live status, and progress bars without setting up a new websocket service every time.
Reusable across projects
One internal realtime service can support Laravel, Vue, React, mobile apps, admin panels, and backend jobs.
Controlled infrastructure
Keep keys, logs, event payloads, and websocket traffic inside your company-managed environment.
Pusher-style usage
Developers already understand the pattern: channels, events, app keys, and frontend listeners.
Better debugging
Event logs make it easier to see what was published, when it happened, and which channel was used.
Laravel-first foundation
Built on Laravel, Reverb, Blade, Tailwind, and clean boilerplate structure for future expansion.
Use cases
Useful wherever the UI must update instantly.
RealtimeHub is ideal for internal tools, client projects, admin panels, operational dashboards, marketplace flows, healthcare status tracking, auction-style features, and support workflows.