Maestro Ends Developer API as Cardano Integrations Face Migration

Maestro announced on September 19, 2026, that its Developer API had reached the end of service. The decision affects wallets, decentralized applications and other Cardano integrations that relied directly on Maestro endpoints for blockchain data.

Maestro Ends Its Hosted Cardano API

Maestro developed a platform that provided structured blockchain data for applications built on UTxO networks. Its Cardano API allowed development teams to access network information without maintaining their own Cardano node and indexing system.

Developers could retrieve addresses, ADA balances, transactions, unspent transaction outputs, native assets, datums and scripts. Additional services provided stake pool information, epoch data, protocol parameters and Plutus script evaluation.

This infrastructure connected Cardano applications with the underlying blockchain. Instead of processing raw network data internally, developers could send requests to Maestro endpoints and receive responses formatted for use in application interfaces and backend systems.

In its final announcement, Maestro thanked the developers who had used the platform and confirmed that the company is now focused exclusively on Maestro Institutional. Its current product offering targets institutional markets with services that include BTC denominated yield products, mining related credit and treasury management infrastructure.

Maestro’s official GitHub organization also reflects this transition. Cardano SDK repositories for TypeScript, Rust, Haskell and Go have been archived, together with API specifications and related development tools. The repositories remain publicly accessible, but they are no longer maintained as active clients for the discontinued hosted service.

Apps Using Maestro Must Replace Their Data Layer

The shutdown affects the infrastructure connecting applications to Cardano blockchain data. It does not change the Cardano protocol, smart contracts or assets recorded on the network. However, it can interrupt applications whose interfaces or backend services continue to send requests to Maestro endpoints.

Blockchain data providers support functions that users encounter throughout decentralized applications. These include displaying wallet balances, locating spendable UTxOs, constructing transactions, tracking native tokens and evaluating Plutus scripts before submission.

Projects using Maestro must now connect these functions to another managed API or replace the external service with infrastructure they operate themselves. Migration can require endpoint changes, adjustments to data models, new authentication systems and testing across application components.

The number of affected projects is not publicly known. Maestro did not release a list of applications using its Cardano API or provide traffic data for individual endpoints. The practical impact therefore depends on whether development teams had already migrated, maintained support for multiple providers or remained dependent on Maestro.

The archived SDKs can still be reviewed, downloaded and adapted. They may help developers understand previous integrations or reuse parts of the client code. However, the availability of an archived SDK does not preserve the hosted service behind it. Applications configured with Maestro API keys and endpoints still require a new data source.

Open Source Cardano Indexer Remains Available

Before ending the hosted API, Maestro released the software stack that powered its Cardano data platform. The Maestro Cardano Indexer is available under the Apache 2.0 license for developers that want to operate their own indexing infrastructure.

The indexer is designed as a distributed production system covering every Cardano era from Byron through Conway. It processes blockchain activity and provides a documented REST API for addresses, transactions, UTxOs, native assets, datums and scripts.

Its architecture uses a standard cardano node as the blockchain source. Processed data is stored through TiKV, while Redis coordinates indexer instances and processing positions. More extensive deployments can integrate cardano db sync and Ogmios to provide account information, stake pool data, epochs, protocol parameters, cost models and Plutus script evaluation.

The released code gives Cardano developers a self hosting option, but it is not a direct replacement for the previous managed service. Operating the stack requires a Cardano node, database infrastructure, synchronization management, monitoring and ongoing maintenance.

Development teams that previously relied on Maestro therefore have two operational paths. They can migrate to another managed Cardano data provider or deploy and maintain their own indexer and API infrastructure. Maestro has ended the hosted service, while leaving the underlying Cardano indexing software available to teams with the technical capacity to operate it.