Aerospike: database infrastructure, Cloud pricing and support

For financial-services applications, Aerospike positions the database as a data layer for fraud models, rules engines and machine-learning pipelines. Its examples cover payment fraud, identity checks, account takeover and transaction monitoring. This places responsibility for the actual detection rules, model decisions and compliance workflow in the surrounding application; supplying fast access to records does not itself constitute a complete fraud-control service.[2]

Streaming connectors exchange data with Kafka, Pulsar and JMS. Event Stream Processing can turn database change events into downstream actions, including cloud functions. This is a way to connect operational records to an event-driven application, but the message system, function runtime and downstream consumer remain separate components of the deployment.[8]

Query integrations provide a different route. The Spark connector supports reads and writes through Spark workloads and structured streaming; the Trino connector exposes data to an external SQL query engine. Aerospike Graph supplies a Gremlin interface for relationship traversal rather than making the base key-value client a graph-query language.[9][5]

Client compatibility should be checked at feature level. The current 8.2 matrix lists both the newer Java and Python SDKs and established language clients, but the Aerospike Expression Language and query optimizer are available through the new Java/Python SDKs and Rust support shown in that matrix. A client that can connect to the server is therefore not necessarily a client that exposes every newer query feature.[10]

Community Edition is free, with an AGPLv3 server licence, Apache v2 client licensing and published limits of eight nodes and 2.5 TB per cluster. Enterprise production licensing uses unique data volume and active production clusters. Selected features require additional licensing: strong consistency, transactions, rack awareness, LDAP and encryption at rest are included in Enterprise Edition Plus. The published connector list also marks additional licensing. Consequently, an enterprise quote needs to identify both the stored-data basis and the enabled features.[3]

The Master Subscription Agreement separates self-managed software from Aerospike Cloud. For self-managed deployments, the customer provides and operates its servers or cloud infrastructure and contracts for licensed capacity. Exceeding that capacity can produce additional charges. Unless the order says otherwise, subscriptions renew for another year without notice at least 60 days before expiry; fees are generally non-cancellable and non-refundable. These terms make capacity measurement and the renewal calendar part of ongoing administration.[12]

Transaction semantics depend on configuration and application behavior. Aerospike transactions require a strong-consistency namespace. The application must commit or abort its work, and the documentation warns against mixing transactions with active-active cross-datacenter replication when both sides may write the same records. It recommends multi-site clustering for that arrangement. Data replication, local availability and transactional isolation therefore need to be chosen together, rather than inferred from the presence of a transaction API.[11]

Managed Services adds an operational team to the deployment. Both Essentials and Concierge cover monitoring, incident response, backups and critical updates. Non-critical updates are scheduled quarterly under Essentials and monthly under Concierge; Concierge also includes annual rightsizing and business-continuity or disaster-recovery assessment work. The service is scoped at cluster level, so the agreement needs to identify which production and non-production clusters are included.[13]

Professional Services covers migration planning, upgrade sequencing, design reviews, capacity testing and production reviews. The published migration work examines existing stores, applications and data models; capacity testing investigates throughput and node-loss behavior. These services can supply a deployment plan or assessment, while a separate Managed Services arrangement determines who performs ongoing operations. Custom scope is handled through a statement of work.[14]

The support policy calls the response times best-efforts targets. Urgent and High severity apply to production systems, and covered requests must come from designated contacts through the portal in English. Urgent coverage runs continuously; for High severity, Silver specifies four business hours while Gold and Platinum specify four hours around the clock. Customers retain backup responsibilities and should supply only the diagnostic data needed. Starting with Enterprise Edition 8.1, major releases receive 36 months of maintenance from general availability.[16]

The Cloud SLA covers compliant, paid production clusters with at least three nodes, active for at least 24 hours. Its 10% credit band covers 99.00% to below 99.90% monthly uptime for single-zone deployments, or to below 99.99% for multiple zones; below 99% produces a 25% credit. Downtime counts minutes when all continuous connection attempts fail. Exclusions include customer configuration, scheduled maintenance, previews and underlying third-party cloud services. An incident ticket is required within 24 hours, followed by a supported credit request within 30 days after month-end. Credits apply to future fees for the affected cluster, capped at 25% of the affected month’s fees and 10% of annualized current-term fees. They are the SLA’s exclusive financial remedy. The advertised availability figures consequently need to be read with the eligibility, measurement and exclusions.[17]

Aerospike’s Data Processing Addendum distinguishes customer data processed on the customer’s instructions from account and usage information for which Aerospike acts as an independent controller. The customer remains responsible for lawful instructions and the personal data it places in the service. The addendum sets the contractual framework for subprocessors and data handling; it does not transfer an institution’s own fraud, customer-onboarding or financial-services obligations to the database provider.[18]

Access controls and encryption also depend on the edition and licensed features. The edition matrix places TLS and access-control lists in Enterprise Edition, while encryption at rest and LDAP require the applicable additional entitlement or Enterprise Edition Plus. A Community-to-Enterprise migration therefore changes more than support access: it can change which security controls are available to the deployment.[3]

The contracting software and service provider is Aerospike, Inc. Its published US headquarters is in Mountain View, California. The company’s database FAQ records that it and its products previously used the Citrusleaf name, changing to Aerospike in summer 2012. That historical name can appear in older technical and corporate references.[18][20][19]

Operator

Aerospike, Inc.

Service scope

Distributed operational database and managed infrastructure for data-intensive applications.

Customer types

Banks; Payment companies; Fraud and identity platforms; Enterprise application teams

Delivery

On premises; SaaS; Managed service; Hybrid

Pricing publication

Public and quoted pricing

Headquarters

Mountain View, California, United States

Platforms

Aerospike Database; Aerospike Cloud; Aerospike Graph; Aerospike Voyager

Integrations

Kafka; Pulsar; JMS; Spark; Trino; Gremlin; Java SDK; Python SDK

Pricing scope

Free Community Edition; enterprise data-volume and feature licensing; indicative Cloud examples with workload-specific quotations.

Implementation

Client integration, data-model and cluster design; optional migration and operational services.

Support

Silver, Gold and Platinum support, with severity-specific initial-response targets and a separate Cloud SLA.

Permissions and regulatory scope

Database infrastructure for financial and other applications; customer applications determine the regulated workflow.

Provider metadata checked 21 Oct 2026Source 10Source 4Source 20Source 1Source 18Source 3Source 19Source 2Source 5Source 12Source 14Source 9Source 8Source 16Source 6

Voyager brings query editing, data exploration and administration into a desktop interface. Its MCP server can expose tools to an AI agent, including a read-only mode. The product page describes confirmation for destructive operations and guards for expensive work. Those controls belong in the same access review as a human administrator’s permissions, particularly when an agent can make requests against a live database.[6]

The separate Voyager terms provide the tool as-is and allow it to be changed or discontinued. Usage telemetry may be enabled by default and can be disabled in settings. Together with its preview label, those terms distinguish experimentation with the desktop tool from a contracted production database service and its support or availability commitments.[7]