We’re splitting Akash Console into two products.
The console you know at console.akash.network is becoming more focused: managed wallets, credit-card billing, and the shortest possible path from “I have a Docker image” to “it’s running on Akash.” Everything that supports that goal stays. Everything that doesn’t is moving.
The self-custody features (connecting your own Keplr wallet, signing your own transactions, running the console against your own nodes) are not going away. They’re moving to a new home: Console Air. Console Air is open source, self-hostable, and preserves the full self-custodial experience for the users who want it.
This split is formalized in AEP-84, the Akash Enhancement Proposal that outlines the rationale, scope, and migration path.
Why split the product?
Akash Console has been trying to be two things at once:
- The fastest on-ramp to decentralized compute, for people who don’t already hold ACT, don’t run a Cosmos wallet, and just want to deploy something. For these users, every wallet pop-up, every “go fund this address,” every “sign this transaction” is a paper cut.
- A first-class self-custody UI, for the developers, builders, and providers who already live in the Cosmos ecosystem, hold ACT, and want full control over keys, RPC nodes, and signing.
Optimizing for both at the same time means doing neither of them as well as we could. Every product decision was a compromise: do we surface the credit-card flow, or the Keplr flow? Do we hide gas details, or expose them? Do we route through our managed signer, or your local one?
By splitting, we can stop compromising:
- Akash Console becomes the cleanest possible managed-wallet experience. No mnemonic prompts. No chain switching. No “what’s a gas adjustment?” Just deploy.
- Console Air becomes a serious tool for self-custodial users. Run it locally or self-host it. Use your own nodes. Sign your own transactions. Own the entire stack end-to-end.
Both consoles point at the same Akash Network: the same providers, the same deployments, the same chain. You can use either, or both.
What’s moving to Console Air
If you’re a self-custody user today, here’s what to expect on Console Air:
- Connect your own Keplr wallet
- Sign every transaction yourself
- Configure custom RPC and API endpoints
- Manage your own deployment certificates
- Self-host the entire UI behind your own domain if you want to
If you’re a managed-wallet user (you signed in with email or social login, and the console handles signing for you), nothing changes. Stay on console.akash.network.
Migrating: Export your local data
If you’ve been using self-custody on Akash Console, your local data (saved deployments, certificates, network preferences, favorites) lives in your browser. We’ve made it easy to bring it with you.
In Akash Console → App Settings → General, click Export Local Data. You’ll get a JSON file containing your settings, certificates, and deployment metadata.
In Console Air, go to the same settings page and click Import Local Data. Pick the file you exported. Done. Your deployments and certificates are right where you left them.
This works because Console Air is the same codebase, minus the managed-wallet flows. Local storage formats are identical, so the export/import is a straight one-to-one transfer. The export is a full snapshot of everything Console stores in your browser, so nothing is left behind.
For the full step-by-step walkthrough, see the migration guide.
Timeline
Console Air is the new home for self-custody. Self-custody flows will be removed from console.akash.network on May 18, 2026 (00:00 UTC). Until then, deprecation notices will appear in-app and the export tool will keep working so you always have a clean migration path.
You’ll start seeing an in-app banner pointing here and to Console Air in the lead-up to the cutoff. Once you’ve migrated (or confirmed you don’t need to), dismiss the banner and it stays dismissed.
What happens after May 18, 2026
- Existing deployments keep running on-chain. The split is a UI change, not a chain change. Your leases, providers, and escrow accounts are unaffected.
- You won’t be able to manage self-custody deployments from console.akash.network anymore. Close, update, redeploy, and certificate management for self-custody wallets move to Console Air.
- Managed-wallet users are not affected. If you signed in with email or social login, nothing about your experience changes.
If you have a self-custody deployment you want to keep managing through a UI, export your local data and import it into Console Air before May 18.
Try Console Air
The repository is at github.com/akash-network/console-air. Clone it, run it locally, or deploy your own instance. The README walks through both. Issues, PRs, and feedback welcome.
If you have questions about the split or the migration, find us in the Akash Discord or open an issue on the Console Air repo. This is the start of a more focused product on both sides, and we want to hear how it lands.
