AxonIQ pricing

Developer
Professional
Enterprise
Zero-configuration monitoring
Advanced Axon Framework metrics
Visualization of message flow
Axon Framework monitoring
Axon Server monitoring
Metrics retention
30 Days
30 Days
Custom
Location transparency with Axon Server
Message routing
High-performance event store
Persistent Streams

More information can be found in this blog.

Tiered storage
Disaster recovery and high availability
Clustering
Maximum node count
1
3
Custom
Geographical awareness
Axon Framework control
Processor management
Dead-Letter Queue insight & actions
Event processor auto-scaling & loadbalancing
Integration with existing tools
Slack integration
PagerDuty integration
Webhooks (coming soon)
Email notifications
Enterprise-ready
Support
Community
Billing
Incidents
Node types
Primary
Primary
Primary, Backup, Messaging only
Authentication
Users and apps
Users and apps
0Auth and LDAP
Extensions
Data Protection
Cloud
Google Cloud Marketplace
Connections
Maximum connections
10
5-100
Unlimited
AxonIQ Console connection
Mandatory
Mandatory
Optional
Monthly price
Free
1-5 Connections$40
6-10 Connections$12 each
11+ Connections$20 each
Yearly contract
What is a connection?

A connection refers to a single active link between an application instance and Axon Server. Each application requires at least one connection, the one for its default context. Without configuring additional contexts in your application, only one connection per application instance will be used. However, an application opens an additional connection for each configured context besides the default one, and each of these connections are counted separately.

When you run multiple instances of the same application, each instance will open its own connection. Therefore, two instances of an application that use two connections will count as four connected applications, total.

In the example below, the order application connects only to its default context, “order,” and thus uses one connection. The Warehouse application, however, listens to the events from the “order” context to process orders. Furthermore, it has its own context to store events. Therefore, it uses two connections per application instance.