Realtime sizes, pricing & limits
Realtime servers are pay as you go and billed hourly, with the same formula as Managed Databases: compute and storage at dedicated Cell rates, plus a management fee while the server runs. There is no per-message or per-connection charge.
Sizes and capacity
The size sets how many clients can connect and how fast messages flow. Prices assume the default 1 GiB of storage and 730 hours per month.
| Size | vCPU / memory | Connections | Deliveries/s | API publishes/s | Max message | Bandwidth | History up to | ≈ per month |
|---|---|---|---|---|---|---|---|---|
nano | 0.25 / 512 MiB | 2,500 | 8,000 | 200 | 32 KiB | 25 Mb/s | 10 min | $1.92 |
small | 0.5 / 1 GiB | 7,500 | 20,000 | 500 | 64 KiB | 50 Mb/s | 1 hour | $3.82 |
medium | 1 / 2 GiB | 20,000 | 50,000 | 1,500 | 128 KiB | 150 Mb/s | 6 hours | $7.61 |
large | 2 / 4 GiB | 50,000 | 100,000 | 4,000 | 256 KiB | 300 Mb/s | 24 hours | $15.21 |
xlarge | 4 / 8 GiB | 100,000 | 200,000 | 8,000 | 256 KiB | 600 Mb/s | 24 hours | $30.39 |
Capacity figures are estimates
- Custom sizes. 0.25 to 8 vCPU in steps of 0.25 and 512 MiB to 32 GiB of memory in steps of 256 MiB; capacity scales with the size, and the Dashboard shows the estimate before you confirm.
- Resizing CPU and memory applies live, without a restart.
- Storage holds channel history and webhook queues: 1 GiB by default, up to 500 GiB. It can grow but never shrink.
- App settings can lower these limits per app, never raise them.
How the price is calculated
| Part | Rate | Charged |
|---|---|---|
| Compute | $0.004 per vCPU-hour and $0.002 per GiB of memory per hour, plus the server's 1 GiB system disk at the storage rate | While the server runs |
| Storage | $0.00001536 per GiB-hour, about $0.011 per GiB per month | Always, including while the server is stopped |
| Management fee | 30% of the CPU and memory cost | While the server runs |
For example, a Nano server (0.25 vCPU, 512 MiB) with 1 GiB of storage:
- Compute: 0.25 × $0.004 + 0.5 × $0.002 = $0.002 per hour, plus $0.00001536 for the system disk.
- Management fee: 30% × $0.002 = $0.0006 per hour.
- Storage: 1 × $0.00001536 = $0.00001536 per hour.
- Total: $0.00263072 per hour, about $1.92 per month. Stopped, it costs about $0.01 per month.
Bandwidth is shaped per size and counted per app (see hubfly realtime usage), but it is not billed.
The quote you see is the price you get
hubfly realtime create show a quote before you create or resize a server, and that quote is authoritative. If prices changed in between, Hubfly space refuses the request (MANAGED_PRICE_CHANGED) and you get a fresh quote.Billing and your balance
Realtime servers are billed from your account balance like other dedicated resources. If the balance runs out, Hubfly space stops them the same way it stops paid containers. Read Billing & Free Tier for how balances and usage work.
Limits
| Item | Limit |
|---|---|
| Server name | 3–48 lowercase letters, numbers and hyphens, starting with a letter. It becomes part of the hostname. |
| Servers per account | A per-account limit applies to live realtime servers. |
| Apps per server | 100. App names are 1–64 printable characters. |
| Keys per app | 10 |
| Webhooks per app | 10, each with a backlog of up to 100,000 events |
| Allowed origins per app | 50 |
| Server API allowlist | 64 IPv4 or IPv6 addresses or CIDR ranges |
| Channel names | 1–200 characters from a-z A-Z 0-9 - _ = @ , . ; |
| Event names | 1–200 characters. The pusher:, pusher_internal: and hubfly: prefixes are reserved. |
| User ids | 1–128 characters, same set as channel names |
| Channels per connection | 100 by default, up to 1,000 |
| Presence members per channel | 100 by default, up to 1,000. User info up to 1 KiB. |
| Client events | 10 per second per connection by default, up to 100 |
| Publish and send | Up to 100 channels per publish, 100 events per batch, 100 targets per send |
| Channel history | Up to 1,000 messages per channel, for at most the size's history time |
| Sessions | A dropped Hubfly space client is kept for up to 300 seconds (60 by default), with up to 100 buffered messages or 256 KiB |
| Offline queue | 1 minute to 24 hours, up to 1,000 messages per user |
| Receipts and message ids | Receipts are kept for 1 hour; message ids deduplicate for 5 minutes |
| Topology | One server per instance in one location chosen by Hubfly space. No replicas or high availability. |
Not available yet
HTTP or SockJS fallback transports, WebSocket compression, binary frames, Pusher watchlists, custom domains and database change streams are not part of the current version.