Transparent Pricing

Predictable Plans for Engineering Teams

Priced simply on monthly stream volume and retention. No opaque ingress surcharges, unexpected query penalties, or complex seat taxes.

Developer
€29 / month

Ideal for internal tools, staging clusters, and small microservice footprints.

  • 3M (3 Million) events / month stream volume
  • 7-day searchable retention
  • HTTPS batch publishing (up to 256 KiB)
  • 1 concurrent subscriber stream
  • Direct Europe and CIS regional endpoints
  • Standard email support
Select Developer
Most Popular
Growth
€99 / month

Designed for scaling Series A+ SaaS platforms with production telemetry.

  • 25M (25 Million) events / month stream volume
  • 30-day searchable retention
  • HTTPS batch publishing (up to 512 KiB)
  • 5 concurrent subscriber streams
  • Direct Europe and CIS regional endpoints
  • Frankfurt storage archive
  • Priority engineering support
Select Growth
Enterprise
€490 / month

Tailored high-volume clusters with dedicated routing and custom retention.

  • 100M+ (100 Million+) events / month stream volume
  • 90-day+ retention or direct S3 export
  • HTTPS batch publishing (up to 512 KiB)
  • Unlimited concurrent subscriber streams
  • Direct Europe and CIS regional endpoints
  • 99.95% Availability SLA contract
  • Signed Data Processing Agreement (DPA)
Contact Sales
Frequently Asked Questions

Common Questions Regarding Billing & Usage

What is counted towards monthly stream volume?

Stream volume is calculated as the total sum of events ingested from publishers plus events delivered to active subscriber streams within a calendar month.

What happens if an account reaches its stream volume allocation?

To safeguard teams from unpredictable, runaway cloud bills, our edge gateway returns an HTTP 429 Too Many Requests response when an account exhausts its monthly event allocation:

{"error":"quota_exceeded","code":429,"message":"Monthly event synchronization quota exceeded. Bandwidth suspended."}

Responses include a Retry-After: 86400 header. Delivery resumes automatically on the first day of the next billing cycle, or you can contact our team to upgrade your tier.

Where is event data stored and processed?

All event data is processed and stored within our primary facility in Frankfurt, Germany. Storage is secured with AES-256 encryption at rest.

Which regional API host should our applications connect to?

Clients in Europe connect to https://api.axisforge.tech directly to our Frankfurt origin cluster. Clients located in CIS regions (including Kazakhstan, Armenia, Georgia, and Uzbekistan) use https://cis.axisforge.tech. In several CIS regions, direct routing paths to Frankfurt are unstable or subject to intermediate filtering, so our regional edge partner improves reachability and latency stability. Both hosts share the exact same path, JSON schema, and API key.

What is the maximum payload size for individual batches?

The edge ingestion gateway allows individual HTTP POST requests up to 512 KiB (256 KiB under the Developer tier). For optimal throughput and minimal latency overhead, we recommend batching events in chunks of 50 to 500 records (approx. 50–250 KiB).

What payment methods and support languages are supported?

We accept standard corporate credit cards (Visa, Mastercard, American Express) as well as automated SEPA Direct Debit and electronic bank transfer invoicing for European business entities. Support is available in English, German, and Russian.