Hubfly spaceDocs
Console

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.

SizevCPU / memoryConnectionsDeliveries/sAPI publishes/sMax messageBandwidthHistory up to≈ per month
nano0.25 / 512 MiB2,5008,00020032 KiB25 Mb/s10 min$1.92
small0.5 / 1 GiB7,50020,00050064 KiB50 Mb/s1 hour$3.82
medium1 / 2 GiB20,00050,0001,500128 KiB150 Mb/s6 hours$7.61
large2 / 4 GiB50,000100,0004,000256 KiB300 Mb/s24 hours$15.21
xlarge4 / 8 GiB100,000200,0008,000256 KiB600 Mb/s24 hours$30.39

Capacity figures are estimates

Connection and throughput figures are the targets the server enforces for each size. They are estimates until per-size load tests confirm them. Watch Insights and the connection alert, and resize before you reach the limit.
  • 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

PartRateCharged
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 rateWhile the server runs
Storage$0.00001536 per GiB-hour, about $0.011 per GiB per monthAlways, including while the server is stopped
Management fee30% of the CPU and memory costWhile 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

These figures are estimates. The Dashboard and 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

ItemLimit
Server name3–48 lowercase letters, numbers and hyphens, starting with a letter. It becomes part of the hostname.
Servers per accountA per-account limit applies to live realtime servers.
Apps per server100. App names are 1–64 printable characters.
Keys per app10
Webhooks per app10, each with a backlog of up to 100,000 events
Allowed origins per app50
Server API allowlist64 IPv4 or IPv6 addresses or CIDR ranges
Channel names1–200 characters from a-z A-Z 0-9 - _ = @ , . ;
Event names1–200 characters. The pusher:, pusher_internal: and hubfly: prefixes are reserved.
User ids1–128 characters, same set as channel names
Channels per connection100 by default, up to 1,000
Presence members per channel100 by default, up to 1,000. User info up to 1 KiB.
Client events10 per second per connection by default, up to 100
Publish and sendUp to 100 channels per publish, 100 events per batch, 100 targets per send
Channel historyUp to 1,000 messages per channel, for at most the size's history time
SessionsA dropped Hubfly space client is kept for up to 300 seconds (60 by default), with up to 100 buffered messages or 256 KiB
Offline queue1 minute to 24 hours, up to 1,000 messages per user
Receipts and message idsReceipts are kept for 1 hour; message ids deduplicate for 5 minutes
TopologyOne 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.

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top