Pricing

How did we do?

HiveMP Sessions Pricing

When you use HiveMP Sessions, you'll be billed for either session minutes or per operation, depending on whether the session is metered. You configure whether or not a session is metered when you send the authentication request to HiveMP.

User session minutes are measured as the number of minutes between a session's creation and it's deletion, either by API call or automatic expiry.

Successful authentication requests are measured by the number of successful authentication requests (those that result in a session being created) made with a public API key.

The following pricing applies directly to HiveMP Sessions:

HiveMP Sessions
ItemMetered Pricing Unmetered Pricing
User session minutes$0.02 USD per 1,000 session minutes
Free
Successful authentication requestsFree
To be announced

Pricing of Other Services

When you use API keys provided in a session with another HiveMP service, whether or not the session is metered can impact the billing model for that other service. Refer to the product's specific pricing page for details as to how the items in the following tables are measured by HiveMP.

HiveMP Presence
ItemMetered Pricing Unmetered Pricing
Connected minutes
Measured as the total number of minutes that clients are connected to a HiveMP Presence socket.
Free
To be announced
HiveMP Chat
ItemMetered Pricing Unmetered Pricing
Messages sentFree
To be announced
Messages receivedFree
To be announced
HiveMP NAT Punchthrough
ItemMetered Pricing Unmetered Pricing
NAT punchthrough requestsFree
To be announced
HiveMP Attributes
ItemMetered Pricing Unmetered Pricing
Attribute operationsFree
To be announced
Attribute storage For both metered and unmetered sessions:To be announced
HiveMP Lobbies
ItemMetered Pricing Unmetered Pricing
Lobby operations
Measured as the number of create, update, delete, join and leave requests against game lobbies.
Free
To be announced
HiveMP Event Tracking
ItemMetered and Unmetered Pricing
Events ingested$0.01 USD per 100 MB ingested (the size of each event is rounded up to the nearest KB)
Event storageTo be announced