Erbil'Kurdistan 40m, Bakhtiyari, Star Towers
Inverge That Ensures Your IT Runs Seamlessly, Anytime and Every Time

Inverge WebSocket APIs provide a scalable, low-latency platform for building real-time applications that require persistent, bidirectional communication between clients and servers. Our pricing model is designed to be flexible and cost-effective, allowing you to pay only for the resources you consume.
The service is built on top of the industry-leading WebSocket protocol, which provides a reliable, low-latency connection between clients and servers. Inverge WebSocket APIs are designed to be simple to use and integrate with existing applications.
Every account includes a monthly allocation suitable for development, staging, and small production workloads:
50K connection-minutes: Support ~1,700 continuous connections or 50K brief sessions
1 GB data egress: Outbound message payload transfer
1M messages: Sufficient for low-frequency notifications or moderate interaction
Fair-use soft caps apply; excess usage automatically transitions to pay-as-you-go rates
10,000 average daily active users, moderate engagement
| Active Users | Price/1K mins | Free tier/month | Calculation (users * days * 1hour = x mins) |
|---|---|---|---|
| 10K | $0.00025 | 50K connections | 10K * 30d * 1h = 300K mins Cost: (300K − 50K free) * $0.00025 = $62.50 |
Billing Calculation: Each established WebSocket connection accrues one minute of usage per wall-clock minute, regardless of message activity. Partial minutes are rounded up.
| Messages | Price (per million) | Free tier/month | Calculation ((messages - free) * price) |
|---|---|---|---|
| 2 million | $0.000025 | 1 million | (2M − 1M free) * $0.000025 = $25.00 |
Billing Calculation: Each message delivered to a recipient socket counts as one billable unit. Room broadcasts are metered per recipient (100 recipients = 100 messages).
| GB | Price (per GB) | Free tier | Calculation ((GB - free) * price) |
|---|---|---|---|
| 3GB | $0.06 | 1GB | (3GB − 1GB free) * $0.06 = $0.12 |
Billing Calculation: Outbound payload bytes transmitted from platform to clients. Ingress (client-to-server) is not charged. Payload size is rounded to 4 KB blocks for billing purposes.
Server-initiated messages delivered to client sockets
Broadcast/multicast fan-out (counted per recipient)
Application-layer messages across rooms or direct channels
WebSocket control frames (ping/pong keep-alives)
Connection handshake and authentication overhead
Platform-initiated retries due to infrastructure failures


Get answers to the most common questions
about our products,
services, and policies.
Our default model is consumption-based to ensure cost alignment with business value. However, committed-use contracts with volume discounts and rate locks are available for predictable workloads. Contact our solutions team for custom pricing.
Each message delivered to a recipient socket counts as one billable message. Broadcasting to a room with 500 members generates 500 message charges. Egress is calculated based on total payload bytes transmitted.
Soft limits trigger adaptive throttling with exponential backoff rather than hard rejections. This preserves service availability during traffic spikes while protecting platform stability. Sustained usage above limits should trigger a capacity planning conversation.
Infrastructure-level failures and platform-initiated retries are not billed. However, application-layer acknowledgment failures or client-initiated duplicate sends are counted as separate messages.
Yes. Enterprise agreements offer committed-use discounts (20-40% off standard rates), dedicated infrastructure, custom SLAs, and reserved capacity. Minimum annual commitment typically starts at $50,000.
Native SDKs for JavaScript/Node.js, Laravel, and Flutter. REST API for connection management and message injection. Comprehensive documentation, sample applications, and integration consulting available.
Client SDKs automatically reconnect to healthy endpoints with exponential backoff. Session state can be restored via optional persistence layer. Active-active topology ensures sub-second failover for any issues.