# Hibira

> Hibira is a hosted realtime WebSocket service that speaks the Pusher Channels protocol. You keep pusher-js, Laravel Echo and the Pusher server SDKs and only change the host.

Hibira uses the same protocol and SDKs but runs in Hong Kong, works in seven languages and counts only the events you publish as messages; deliveries come from a separate monthly allowance.
Hibira is free up to 100 peak connections and 200,000 messages a day. Paid plans cost US$19 to US$699 a month, for up to 72,000 peak connections; Enterprise starts at US$2,500.

Website: https://hibira.io/ (also in Traditional Chinese, Simplified Chinese, Japanese, Korean, Thai and Vietnamese: start the path with /zh-tw, /zh-cn, /ja, /ko, /th or /vi). Sales: sales@hibira.io.

The comparisons, topics, use cases, blog posts, the Pusher protocol page and the integration guides for pusher-js, Laravel and the other libraries are also served as Markdown, in every language: add .md to the page’s URL (for example https://hibira.io/compare/pusher.md or https://hibira.io/ja/guides/laravel.md).

## Plans

| Plan | Price per month | Peak connections | Messages per day | Apps |
| --- | --- | --- | --- | --- |
| Free | US$0 | 100 | 200K | 1 |
| Hobby | US$19 | 1K | 1M | 100 |
| Starter | US$39 | 3.5K | 2M | 100 |
| Pro | US$89 | 8.5K | 6M | 100 |
| Advanced | US$169 | 16.5K | 12M | 100 |
| Business | US$279 | 28K | 20M | 100 |
| Scale | US$699 | 72K | 90M | 100 |
| Enterprise | from US$2,500 | 100K+ | 200M+ | 100 |

Limits are per account: connections and messages are counted across all of the account’s apps. Paid plans allow 10 concurrent channels per peak connection, also across the account’s apps.
Hobby and higher plans do not count broadcast deliveries: a broadcast counts once however many subscribers receive it. Daily messages, peak connections and direct data per month are still capped on every plan.

- Free: messages up to 4 KB, up to 200 channels per app, browser origins must be listed (no "*").
- Hobby: messages up to 10 KB.
- Starter: messages up to 10 KB.
- Pro: messages up to 32 KB.
- Advanced: messages up to 32 KB.
- Business: messages up to 64 KB.
- Scale: messages up to 64 KB.
- Enterprise: messages up to 64 KB.

## Common questions

- **Can I use pusher-js with Hibira?** Yes. pusher-js connects to Hibira over WebSockets with the same API: set wsHost to your Hibira host and keep your channels, events and auth endpoints. Laravel Echo, PusherSwift and the other Pusher client libraries work the same way.
- **What is a hosted WebSocket service?** A hosted WebSocket service keeps realtime connections open to your users’ browsers and apps, so your backend can push events to them instantly without running WebSocket servers. Your server publishes over a simple HTTP API; Hibira handles connections, scaling, presence and private channels.
- **Do I need to change my code?** No. Point your Pusher host settings at us and use the key and secret from your dashboard. Your channels, events and authorization endpoints stay the same.
- **What counts as a message?** Each event you publish to a channel through the HTTP API, and each client event, counts once. Deliveries to subscribers and presence updates use the plan’s monthly deliveries, one for each 1 KB.
- **Which deliveries are not counted on Hobby and up?** Broadcasts delivered through edge nodes. On Hobby and up, the portal gives each app the host ws-edge.hibira.io. With the app’s default Auto setting, its new connections move to the edge on days with heavy traffic (5 GB in a day) or once the account has used 80% of its monthly data; Always edge sends them there from the start. Each broadcast then counts once per edge node instead of once per subscriber. Connections that go straight to Hong Kong, including every connection to ws.hibira.io, count toward the monthly direct data as usual.
- **Are limits per app or per account?** Per account. Peak connections, daily messages and push subscribers are counted across all of your apps, the same way Pusher Channels counts them. You can enable 1 app on the Free plan and up to 100 on every paid plan.
- **What happens when I reach a limit?** We email you when usage reaches your alert level (80% unless you change it) and at 100%. Past the connection limit, new connections are refused with Pusher error 4004; past the daily message limit, publishing returns HTTP 429 until 00:00 UTC; when the monthly outbound data is used up, publishing returns HTTP 429 until the 1st of next month; a subscription that would open a channel past the plan’s concurrent channel limit gets pusher:subscription_error with status 429. Nothing is billed after the fact: upgrade any time.
- **Do you offer an SLA?** Yes, on Enterprise plans: 99.9% monthly uptime, with service credits of 10% of the monthly fee below 99.9%, 25% below 99.5% and 50% below 99%. Other plans have no uptime commitment; incidents are published on our status page.
- **Which payment methods do you accept?** Cards and the local payment methods Stripe supports in your country.
- **Is there a free trial?** Hobby, Starter and Pro come with a free trial; its length is shown on the plan and at checkout. A card is required, and you are charged when the trial ends unless you cancel before then. Each account and card gets one trial, and moving to a plan without a trial during it ends the trial.
- **Can I cancel any time?** Yes. Cancel from the billing portal; your plan stays active until the end of the paid period, then the account moves to the Free plan and keeps one app enabled. Moving to a cheaper plan or from yearly to monthly billing also takes effect at the end of the paid period; an upgrade applies at once and the difference is charged right away.
- **Can I get a refund?** Yes, once per account: email support@hibira.io within 14 days of your first payment for a monthly or yearly plan, and we refund it in full and end the subscription. Other payments and prepaid credits are not refunded.

## Servers and latency

Hibira’s servers are in Hong Kong (AWS ap-east-1). Network round trips to them, measured from data centres on 25 October 2026, were about 25 ms from Manila and Hanoi, 30 ms from Taipei, 35 ms from Singapore, 45 ms from Kuala Lumpur, 50 ms from Jakarta, 55 ms from Tokyo and Osaka, 60 ms from Seoul and 80 ms from Bangkok.

How these were measured: TCP connects to port 443 of the AWS Hong Kong region from 2 to 7 data-centre probes per city (Globalping), the median of the probes’ averages, rounded to 5 ms. Users on home or mobile networks add their own access latency. Each app runs on one cluster: Hong Kong (hkg) today, with Tokyo (tyo) and Singapore (sin) planned.

## Docs

- [Integration guides](https://hibira.io/guides): Connect to Hibira with pusher-js, Laravel, PHP, Node.js, Python, Go, Ruby, Java, .NET, Swift, Kotlin or Flutter, or with our packages for React, Vue, Nuxt, Rails, Filament, Godot, Unity, n8n and Terraform.
- [HTML](https://hibira.io/guides/html): Add one script tag to any web page: a connected client plus a live online counter, feed and toasts, with no build step.
- [JavaScript](https://hibira.io/guides/javascript): Browsers, React, Vue and React Native with the official pusher-js library.
- [Laravel](https://hibira.io/guides/laravel): Laravel Broadcasting on the server and Laravel Echo in the browser, with no code changes.
- [PHP](https://hibira.io/guides/php): Publish from any PHP application with the official server library.
- [Node.js](https://hibira.io/guides/node): Publish events and authorize channels from Node.js, Next.js API routes or serverless functions.
- [Python](https://hibira.io/guides/python): Publish from Django, Flask, FastAPI or any Python service.
- [Go](https://hibira.io/guides/go): Publish from Go services with the official HTTP library.
- [Ruby](https://hibira.io/guides/ruby): Publish from Rails or any Ruby application.
- [Java](https://hibira.io/guides/java): Publish from Spring Boot or any JVM service.
- [.NET](https://hibira.io/guides/dotnet): Publish from ASP.NET Core and other .NET applications.
- [iOS (Swift)](https://hibira.io/guides/swift): Native iOS and macOS apps with the official Swift library.
- [Android (Kotlin)](https://hibira.io/guides/android): Native Android apps in Kotlin or Java.
- [Flutter](https://hibira.io/guides/flutter): Flutter and Dart apps on iOS, Android and the web.
- [Push notifications](https://hibira.io/guides/push-notifications): Add push notifications with a Beams-compatible API: APNs and FCM credentials, the web, Android and iOS SDKs, publishing from Node.js, PHP, Laravel, Python, Go or curl, and troubleshooting.
- [React (official package)](https://hibira.io/guides/react): Hooks for events, presence, client events and connection state, with one shared connection for the whole app. Works with Next.js and Remix, and streams LLM output to every open tab.
- [Vue (official package)](https://hibira.io/guides/vue): Composables for events, presence, client events and connection state on Vue 3 and Vue 2.7. Channel names can be refs, and subscriptions follow them.
- [Nuxt (official package)](https://hibira.io/guides/nuxt): A module for Nuxt 4, 3 and 2: auto-imported composables in components, and a server client plus an auth route helper in server routes.
- [Svelte (official package)](https://hibira.io/guides/svelte): Stores for events, presence, client events and connection state on Svelte 5 and Svelte 4, made for SvelteKit. Use them with $store in any component.
- [Angular (official package)](https://hibira.io/guides/angular): Events, presence members, client events and connection state as signals, with one connection for the whole app. For Angular 17 and later, standalone or NgModule, with or without zone.js.
- [React Native (official package)](https://hibira.io/guides/react-native): The hooks of the React package on React Native and Expo, a connection that closes in the background and opens again when the app returns, payloads of any size, and push notifications through Hibira Push.
- [Rails (official package)](https://hibira.io/guides/rails): Every Turbo Stream broadcast your Rails app already makes goes through Hibira, with no Action Cable server, Redis or Solid Cable to run. Models and views stay as they are.
- [Django (official package)](https://hibira.io/guides/django): Your WSGI Django app renders HTML fragments as it already does and broadcasts them: every open page appends, replaces or removes them as they happen. No Django Channels, ASGI server or Redis to run.
- [NestJS (official package)](https://hibira.io/guides/nestjs): A global module that publishes events, authorizes private and presence channels with decorated provider methods, and receives signed webhooks. pusher-js, Laravel Echo and the mobile Pusher SDKs connect unchanged.
- [ASP.NET Core (official package)](https://hibira.io/guides/aspnetcore): Write hubs with the SignalR API you already know: Clients.All, groups, users, typed hubs and IHubContext. Your server keeps handling hub calls, and no WebSocket server, backplane or Azure SignalR Service is needed.
- [htmx (official package)](https://hibira.io/guides/htmx): Your server renders an HTML fragment and publishes it; every open page swaps it in with hx-ext="hibira". No WebSocket server, Channels or Redis to run, from any backend.
- [Filament (official package)](https://hibira.io/guides/filament): A Filament 3, 4 and 5 plugin: the notification bell updates at once, and panels get who’s-here avatars, edit locks, live tables, import progress and team chat. Nothing to build with npm.
- [Filament AI approvals (official package)](https://hibira.io/guides/filament-approvals): When a Laravel AI SDK agent wants to run a tool that needs a person’s OK, such as a large refund, the request appears in your Filament panel at once. Approve, reject with a reason or edit the arguments, and the agent carries on.
- [Filament AI live chat (official package)](https://hibira.io/guides/filament-support): A chat widget for any website and a live support inbox in your Filament panel. An AI answers first with your own API key, and hands the chat to your team when it is not sure or the visitor asks for a person.
- [Filament collaborative editor (official package)](https://hibira.io/guides/filament-collab): A rich text field that several people type in at the same time, like Google Docs: changes merge on their own, with live cursors and the avatars of who is editing. Its state is HTML like RichEditor, and the record saves with your Save button as usual.
- [WordPress (official package)](https://hibira.io/guides/wordpress): A WordPress plugin with no build step: approved comments appear for every reader, readers get a Reload button when a post is updated, posts show how many people are reading, and WooCommerce order pages follow status changes.
- [Payload (official package)](https://hibira.io/guides/payload): A Payload 3 plugin that sends an event when editors publish, update or delete, and <LiveRefresh> for Next.js, which refreshes the page’s server components when its content changes. Pages stay static or cached, and it runs on Vercel.
- [Godot (official package)](https://hibira.io/guides/godot): A GDScript addon for Godot 4.3 and later that runs on every platform Godot exports to, the web included. HibiraSync keeps a node’s position in step on every screen, and HibiraRoom adds rooms with seats, a host and chat.
- [Unity (official package)](https://hibira.io/guides/unity): A plain C# client for Unity 2021.3 and later, in the Editor, on desktop, Android, iOS and WebGL. Events arrive on the main thread, and HibiraRoom adds rooms with seats, a host and chat.
- [Cocos Creator (official package)](https://hibira.io/guides/cocos): A client with no dependencies for Cocos Creator 3.x on web, native and mini-game builds, a HibiraConnection component that keeps the connection across scenes, and rooms with seats, a host, ready flags and chat.
- [RPG Maker MZ (official package)](https://hibira.io/guides/rpgmaker-mz): A plugin for RPG Maker MZ: players in the same room see each other walk around the map, chat, share the switches and variables you choose, and send each other events. No game server, in playtests, desktop builds and web builds.
- [Phaser (official package)](https://hibira.io/guides/phaser): A complete Phaser 4 example: a room list, seats for four, a host, ready flags, chat with typing indicators and a reaction game, all drawn in a canvas. Phaser, browser and Godot players can play in the same room.
- [Vercel AI SDK (official package)](https://hibira.io/guides/ai-sdk): A transport for useChat(): answers stream over a channel, so they survive dropped connections, resume after a reload and reach every tab and device. Works with AI SDK 5, 6 and 7.
- [AI approvals (official package)](https://hibira.io/guides/approvals): When an agent wants to run a tool that needs a person’s OK, the call waits in a live inbox. Reviewers approve, edit or reject it, see who else is looking, and the agent carries on where it stopped.
- [Lobby (official package)](https://hibira.io/guides/lobby): Rooms on presence channels: seats in join order, a host who hands over when they leave, ready flags, settings, kick, start and room chat. The server half signs seats and lists open rooms.
- [Spaces (official package)](https://hibira.io/guides/spaces): Collaboration on presence channels: who is here and where, live cursors, component locks so two people don’t edit the same field, and follow mode for presenting.
- [Large presence (official package)](https://hibira.io/guides/large-presence): Online counts and member lists for live audiences: the client gets a sample of members and batched join and leave counts instead of every member, and pages through the rest when it needs them.
- [n8n (official package)](https://hibira.io/guides/n8n): Publish events, read channels and presence, and send push notifications from any n8n workflow. The Hibira Trigger starts a workflow when a channel fills or empties, a user joins, or a client sends an event.
- [Make (official package)](https://hibira.io/guides/make): A Make custom app: send events to up to 100 channels from any scenario, read channels and presence members, and start scenarios when a channel fills or empties, a user joins, or a client sends an event.
- [Node-RED (official package)](https://hibira.io/guides/node-red): Send sensor readings, order updates or alerts from a flow to every open browser, dashboard and app at once, react in Node-RED to events your web pages send, and send push notifications to iOS, Android and the web.
- [Activepieces (official package)](https://hibira.io/guides/activepieces): Publish events to up to 100 channels, read channels and presence members, disconnect users and send push notifications from any Activepieces flow. The New Channel Event trigger starts a flow when a channel fills or empties, a user joins, or a client sends an event.
- [Supabase (official package)](https://hibira.io/guides/supabase): Send Supabase table changes to browsers and apps as Hibira events: a Database Webhook calls an Edge Function that publishes them.
- [Terraform (official package)](https://hibira.io/guides/terraform): Manage apps, webhooks and push notification credentials as code: allowed origins, client events, history, IP allowlists and secret rotation, reviewed in a plan like the rest of your infrastructure.
- [Migrating from Pusher](https://hibira.io/migrate): Move a Pusher Channels app to Hibira: keep pusher-js and your server SDKs, change the host, recreate webhooks and switch over without downtime. Includes a feature comparison.
- [Pusher protocol](https://hibira.io/pusher-protocol): How the Pusher Channels protocol (version 7) works: WebSocket handshake, message format, channel types and signatures, client events, error codes, HTTP API and webhooks.
- [MCP server for AI agents](https://hibira.io/mcp-server): Connect Claude Code, Cursor, VS Code, Claude or ChatGPT to Hibira over MCP: your agent creates apps, fills in your .env, checks usage and watches the debug console. Server URL: https://hibira.io/mcp
- [Add Hibira to Claude and ChatGPT: custom connector setup](https://hibira.io/mcp-connectors): Step by step, with screenshots: add the Hibira MCP server to Claude or ChatGPT as a custom connector, approve it, then create apps and check usage from a chat.
- [Changelog](https://hibira.io/changelog): New features, improvements and fixes in each Hibira release: Pusher-compatible channels, webhooks, push notifications, SDKs and the portal.
- [Open-source SDKs](https://github.com/hibira-io): @hibira-io/push-web, hibira-push-android and hibira-push-ios (push notifications), @hibira-io/large-presence (presence channels with up to 100,000 members), @hibira-io/lobby (game rooms and lobbies), @hibira-io/spaces (who is online, live cursors, component locks and follow mode) and the hibira-io/laravel Composer package (Laravel broadcasting, push and webhooks); npm packages under https://www.npmjs.com/org/hibira-io.

## Use cases

- [Use cases](https://hibira.io/use-cases): Scenarios with code: live notifications, chat and typing indicators, live dashboards, collaboration, order tracking, live auctions, job progress and push notifications that bring users back.
- [Live in-app notifications](https://hibira.io/use-cases/in-app-notifications): Show replies, mentions and approvals the moment they happen in every open tab, and fall back to a push notification when the user is offline.
- [Chat with typing indicators and online status](https://hibira.io/use-cases/chat-typing-indicators): Support chat, marketplace messaging and team rooms: messages that arrive at once, “typing…” hints between browsers, and an online list that stays correct.
- [Live dashboards and metrics](https://hibira.io/use-cases/live-dashboards): Charts and counters that update themselves, with the latest value shown the moment the page opens, and no polling from every open dashboard.
- [Collaboration: who is here, live cursors and edit locks](https://hibira.io/use-cases/collaboration-presence): Show the avatars of everyone viewing a document or ticket, share cursors and focus, and broadcast saved changes so nobody overwrites anyone else.
- [Order and delivery tracking](https://hibira.io/use-cases/order-tracking): A status page that updates itself and a courier who moves on the map, sent only while the customer is watching, with a push at the steps that matter.
- [Live auctions, scores and big audiences](https://hibira.io/use-cases/live-audiences): Push the current bid or score to thousands of viewers at once, give newcomers the latest state instantly, and show a real “watching now” count.
- [Progress for long jobs and streaming AI answers](https://hibira.io/use-cases/job-progress): Exports, imports, encoding and AI tasks: a progress bar that follows the real work, the result the moment it is ready, and answers that appear as they are written.
- [Stream AI answers to every screen](https://hibira.io/use-cases/ai-streaming): Chatbots, copilots and AI agents: answers that appear as they are written, reach every tab and device, and pick up after a reload.
- [AI agents: live steps, approvals and alerts](https://hibira.io/use-cases/ai-agents): Show each step an agent takes as it works, hold risky tool calls in a live inbox until a person approves them, and send results to browsers and phones from agents, MCP clients and no-code flows.
- [Push notifications that bring users back](https://hibira.io/use-cases/push-re-engagement): Back-in-stock alerts, reminders and replies on iOS, Android and the web from one Beams-compatible API, with interests users choose and deep links.
- [Multiplayer game rooms and lobbies](https://hibira.io/use-cases/game-lobbies): Party, quiz, board and card games: rooms with a code, seats, a host, ready flags and chat, built on presence channels and client events with no game server.
- [Online user and viewer counts](https://hibira.io/use-cases/online-user-counts): Show how many people are online or watching, count unique users with presence, and read every room’s count from your server with the HTTP API and webhooks.
- [Laravel Echo without running Reverb](https://hibira.io/use-cases/laravel-echo): Change a few .env values; events, channels, whispers and toOthers() keep working.
- [Next.js on Vercel and serverless](https://hibira.io/use-cases/nextjs): Publish from server actions, subscribe in client components, keep sockets out of your functions.
- [Flutter on iOS, Android and the web](https://hibira.io/use-cases/flutter): One Dart client: private channels, reconnects, and push when the app is closed.
- [Unity lobbies, matchmaking and leaderboards](https://hibira.io/use-cases/unity): Presence lobbies, “match found” and cached leaderboards with PusherClient for .NET.

## Comparisons

- [Compare Hibira with Pusher, Ably, PubNub, Reverb and Soketi](https://hibira.io/compare): How Hibira compares with other realtime services and self-hosted servers: pricing, how messages are counted, regions and when each one is the better fit.
- [Hibira vs Pusher Channels](https://hibira.io/compare/pusher): Same protocol and SDKs, so moving is a configuration change. The difference is how messages are counted, where the servers are and what each plan includes.
- [Hibira vs Pusher Beams](https://hibira.io/compare/pusher-beams): A push notification service that speaks the Beams API: keep your server code, change the endpoint, and get realtime channels in the same plan.
- [Hibira vs Ably](https://hibira.io/compare/ably): Ably bills a base fee plus messages, connection minutes and channel minutes; Hibira has fixed monthly plans where only published messages count toward the daily limit.
- [Hibira vs PubNub](https://hibira.io/compare/pubnub): PubNub prices by monthly active users and uses its own SDKs; Hibira prices by connections and messages and keeps the Pusher protocol.
- [Hibira vs Laravel Reverb](https://hibira.io/compare/laravel-reverb): Reverb is the WebSocket server you run yourself; Hibira is the hosted option for the same Laravel Echo code. When each one fits.
- [Hibira vs Soketi](https://hibira.io/compare/soketi): Soketi is an open-source, self-hosted Pusher-protocol server. What you take on by running it, and what a hosted service does instead.
- [Hibira vs Firebase Realtime Database](https://hibira.io/compare/firebase): Firebase Realtime Database syncs a shared database to clients and bills by GB stored and downloaded; Hibira publishes events from your server on fixed monthly plans.
- [Hibira vs Supabase Realtime](https://hibira.io/compare/supabase-realtime): Supabase counts a message for every client that receives it; Hibira counts only what you publish and keeps the Pusher protocol and SDKs.
- [Hibira vs Vask](https://hibira.io/compare/vask): Vask and Hibira both host the Pusher protocol. Vask costs less per connection; Hibira plans include 4 to 15 times as many messages, plus push notifications.
- [Hibira vs Socketo](https://hibira.io/compare/socketo): Socketo and Hibira both host the Pusher protocol and count a broadcast once. Socketo costs less per connection; Hibira includes more broadcasts, push notifications and presence channels for up to 100,000 members.
- [Hibira vs Soketify](https://hibira.io/compare/soketify): Soketify and Hibira both host the Pusher protocol. Soketify costs less per connection and runs in the US and Europe; Hibira runs in Hong Kong and includes push notifications.

## Pricing, hosting and alternatives

- [Realtime pricing, hosting and alternatives](https://hibira.io/topics): What realtime services cost, where to host a Pusher-protocol server, and which alternatives fit which apps, with figures from each provider’s own site.
- [Pusher pricing explained: plans, limits and how messages are counted](https://hibira.io/topics/pusher-pricing): Every Pusher Channels plan with its connections and daily messages, why one event to 50 subscribers counts as 51, and what happens when you reach a limit.
- [Pusher limits: message size, presence members and client events](https://hibira.io/topics/pusher-limits): Pusher Channels’ fixed limits, from the 10 KB event size and 100 presence members to 10 client events a second, why they exist and how to work within them.
- [Pusher alternatives: hosted and self-hosted options compared](https://hibira.io/topics/pusher-alternatives): Ably, PubNub, Laravel Reverb, Soketi, Socket.IO, Centrifugo, Supabase, Firebase and Hibira side by side: who runs the server, how it is priced and which keep pusher-js working.
- [Soketi alternatives: where to move a Pusher-protocol server](https://hibira.io/topics/soketi-alternatives): Soketi’s last release was in March 2024. The Pusher-compatible options to move to, what changes in your configuration, and how to switch without downtime.
- [Laravel Reverb hosting: Laravel Cloud, your own server or a hosted service](https://hibira.io/topics/laravel-reverb-hosting): Where a Laravel app’s WebSockets can run: managed Reverb on Laravel Cloud, Reverb on a Forge or Docker server, or a hosted Pusher-compatible service. Prices and the work each one leaves you.
- [Realtime WebSockets in Asia: latency, regions and where data is processed](https://hibira.io/topics/realtime-websockets-asia): Measured round trips from Asian cities to Hong Kong, which realtime services have servers in Asia, and what to check when your users are in Taiwan, Japan, Korea or Southeast Asia.
- [Photon PUN alternatives for turn-based and casual games](https://hibira.io/topics/photon-pun-alternative): PUN 2 is in maintenance mode. Which games need Fusion or a game server, which fit a hosted WebSocket service with rooms and matchmaking, and what each costs.

## Free tools

- [Free tools](https://hibira.io/tools): Compare the monthly price of your traffic on Pusher Channels, Ably and Hibira. Test a Pusher-compatible app or any WebSocket URL from your browser.
- [Realtime cost calculator: Pusher, Ably and Hibira](https://hibira.io/tools/cost-calculator): Compare the monthly price of your traffic on Pusher Channels, Ably and Hibira.
- [WebSocket tester](https://hibira.io/tools/websocket-tester): Test a Pusher-compatible app or any WebSocket URL from your browser.

## Blog

- [Blog](https://hibira.io/blog): Guides and field notes on WebSockets, Pusher-compatible APIs and building realtime features for users in Asia.
- [Realtime in Asia: where your WebSocket server is matters](https://hibira.io/blog/realtime-latency-in-asia): Why distance sets a floor under realtime latency, what that floor is from Hong Kong to the rest of Asia, and how to measure your own users’ round trip.
- [Why we stopped running our own WebSocket servers](https://hibira.io/blog/hosted-vs-self-hosted-realtime): Our own realtime server jammed when messages spiked, and we chased patches for vulnerabilities like PHP2Shell ourselves. What we ran into, the ongoing work a self-hosted server needs, and what a hosted service takes on.
- [Add realtime WebSockets with Claude Code in ten minutes](https://hibira.io/blog/websockets-with-claude-code-mcp): Connect Claude Code to the Hibira MCP server and let it create an app, fill in your .env, wire up pusher-js and prove the first event arrives.

## Pricing

- [Pricing](https://hibira.io/pricing): Hosted WebSocket pricing: free up to 100 peak connections; paid plans from US$19 to US$699 a month. Publishes count per day, deliveries per month.
- [Contact sales](https://hibira.io/contact-sales): Talk to the Hibira team about larger deployments: dedicated nodes in your region, custom limits, SLAs and invoicing. We aim to reply within one business day.

## Legal

- [Terms of Service](https://hibira.io/legal/terms): The agreement for using Hibira: accounts, plans and fees in US dollars, acceptable use, liability and termination.
- [Privacy Policy](https://hibira.io/legal/privacy): What personal data Hibira collects and why, how long it is kept, who receives it, and your rights in each country.
- [Data Processing Agreement](https://hibira.io/legal/dpa): How Hibira processes personal data in your messages as your processor: security, sub-processors, transfers and breach notice.
- [Sub-processors](https://hibira.io/legal/subprocessors): The service providers that may process Customer Data for Hibira, and where they are.
- [Commercial Transactions Act notice](https://hibira.io/legal/tokushoho): The seller, prices, payment, cancellation and refunds for Hibira, as Japan’s Specified Commercial Transactions Act requires.

## Optional

- [Full text](https://hibira.io/llms-full.txt): plans, FAQ and every integration guide with code in one file.