Maestro End Developer API as Cardano Integrations dey Plan Migration

Maestro announce on September 19, 2026, say im Developer API don reach end of service. The decision affect wallets, decentralized applications and other Cardano integrations wey dey rely directly on Maestro endpoints for blockchain data.

Maestro End Im Hosted Cardano API

Maestro develop one platform wey dey provide structured blockchain data for applications wey build on UTxO networks. Im Cardano API allow development teams access network information without to maintain their own Cardano node and indexing system.

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

This infrastructure connect Cardano applications with the underlying blockchain. Instead make developers process raw network data by themselves, dem fit send requests go Maestro endpoints and receive responses wey don already format to work inside application interfaces and backend systems.

For im final announcement, Maestro thank the developers wey don use the platform and confirm say the company now dey focus only on Maestro Institutional. Im current product offering target institutional markets with services wey include BTC denominated yield products, mining related credit and treasury management infrastructure.

Maestro official GitHub organization still reflect this transition. Cardano SDK repositories for TypeScript, Rust, Haskell and Go don archive, together with API specifications and related development tools. The repositories still dey publicly accessible, but dem no dey maintain am again as active clients for the hosted service wey dem don discontinue.

Apps Weh Dey Use Maestro Must Replace Their Data Layer

The shutdown affect the infrastructure wey connect applications to Cardano blockchain data. E no change the Cardano protocol, smart contracts or assets wey the network don record. But e fit interrupt applications wey their interfaces or backend services still dey send requests go Maestro endpoints.

Blockchain data providers dey support functions wey users dey meet across decentralized applications. These include to show wallet balances, locate spendable UTxOs, construct transactions, track native tokens and evaluate Plutus scripts before submission.

Projects wey dey use Maestro must now connect these functions to another managed API or replace the external service with infrastructure wey dem run by themselves. Migration fit require endpoint changes, adjustments to data models, new authentication systems and testing across application components.

The number of projects wey e affect no dey publicly known. Maestro no release list of applications wey dey use im Cardano API or provide traffic data for individual endpoints. The practical impact therefore depend on whether development teams don already migrate, maintain support for multiple providers or still remain dependent on Maestro.

The archived SDKs still fit make people review, download and adapt am. Dem fit help developers understand previous integrations or reuse parts of the client code. But make we note say as SDK don archive no mean say the hosted service still dey behind am. Applications wey configure with Maestro API keys and endpoints still need new data source.

Open Source Cardano Indexer Still Dey Available

Before dem end the hosted API, Maestro release the software stack wey power im Cardano data platform. The Maestro Cardano Indexer dey available under the Apache 2.0 license for developers wey wan operate their own indexing infrastructure.

The indexer design be distributed production system wey cover every Cardano era from Byron reach Conway. E dey process blockchain activity and provide documented REST API for addresses, transactions, UTxOs, native assets, datums and scripts.

Im architecture dey use standard cardano node as the blockchain source. Processed data dey store through TiKV, while Redis dey coordinate indexer instances and processing positions. Bigger deployments fit integrate cardano db sync and Ogmios to provide account information, stake pool data, epochs, protocol parameters, cost models and Plutus script evaluation.

The code wey dem release give Cardano developers self hosting option, but e no be direct replacement for the previous managed service. To operate the stack require Cardano node, database infrastructure, synchronization management, monitoring and ongoing maintenance.

Development teams wey previously rely on Maestro therefore get two operational paths. Dem fit migrate go another managed Cardano data provider or deploy and maintain their own indexer and API infrastructure. Maestro don end the hosted service, but e leave the underlying Cardano indexing software available to teams wey get the technical capacity to operate am.