Aerospike unveils AI-native developer tools for database

Aerospike has introduced a new AI-native developer experience for teams building applications on its NoSQL database. The release combines a visual workspace, an embedded server for AI agents and updated software development kits.

The package includes Aerospike Voyager, an embedded MCP server and revised Java and Python SDKs for developers working alongside AI coding tools. It is designed to support both human engineers and AI agents as they prototype, integrate, deploy and troubleshoot applications on Aerospike's real-time database.

Voyager is a visual developer workspace available as a desktop application for macOS, Windows and Linux. It offers one-click cluster connection, sample data libraries, a hierarchical data browser for visual data exploration and server-side filtering controls.

In early testing, developers using Voyager went from connecting to a first cluster to running a first filtered query in as little as five minutes. Aerospike positioned that as a way to reduce the time needed to begin working with data stored in its environments.

The embedded MCP server is designed to enable AI coding agents to interact directly with Aerospike clusters from within development tools. Developers and agents can inspect data, query records, explore schemas, and access documentation within tools, including Claude Code, Codex, Cursor, and Gemini CLI.

That reflects a broader shift in software development, as engineering teams increasingly use large language model-based assistants to generate code and accelerate early application work. For database suppliers, the challenge is making those tools useful in production settings, where developers still need visibility into data, code behaviour and system configuration.

The updated Java and Python SDKs were written to make database operations more readable and to separate application logic from infrastructure settings. In practice, that means developers can write feature code while database administrators and site reliability engineers handle timeouts, retry policies and cluster configuration separately.

The revised syntax and related documentation are also structured to make it easier for both people and AI agents to write Aerospike code correctly on a first attempt. That focus on coding assistants comes as software providers adapt developer tooling to workflows in which AI systems now generate, review and refine significant amounts of code.

Developer tools

Aerospike has long focused on workloads that require fast access to large volumes of data, including fraud detection, profile stores, recommendation engines and bidding systems. By adding more visual tools and direct support for AI coding assistants, it is seeking to make its database easier to adopt earlier in the development process, not just in large-scale production deployments.

The release also addresses a practical issue for engineering teams experimenting with AI-generated code. While code assistants can help teams move quickly from concept to prototype, they do not remove the need to inspect live data, understand how generated code behaves and diagnose faults when systems do not work as intended.

In that context, Aerospike is trying to reduce the need for context switching between database consoles, documentation pages, command-line interfaces and coding environments. Embedding the MCP server in Voyager gives developers a single download and setup step to connect coding agents to Aerospike clusters.

The latest changes come as infrastructure and database vendors compete to make their products more accessible to a broader range of developers, including those without specialist database expertise. For suppliers, that means simplifying onboarding without weakening the controls that operations teams need to manage live systems.

Aerospike says its approach is intended to serve developers with different levels of experience. New users can explore data visually and interact with the system through conversational prompts in AI tools, while experienced teams can use the same environment for debugging, query work and code generation.

Voyager is available in preview, with the MCP server included. The updated developer SDKs cover Java and Python, two languages widely used in back-end systems and data-intensive application development.

Srini V. Srinivasan, founder and chief technology officer of Aerospike, said the different parts of the release serve distinct needs across coding and debugging workflows: "The new Developer SDK makes Aerospike code easier to read and reason about. Voyager simplifies access to data for debugging and query exploration. And the MCP server enables developers to analyze data using the tools and environments they already prefer."