Akash Network (@akashnet): Console Air: Self-Host, Self-Custody Akash

Console Air: Self-Host, Self-Custody Akash TL;DR: Akash Console is splitting into two products: the managed-wallet Console at console.akash.network (credit card, no-wallet users), and Console Air, an open-source, self-hostable console for self-custody users with Keplr wallet, custom RPC nodes, and full transaction signing. We’ve split 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 (air.akash.network). 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 or use https://air.akash.network If you’re a managed-wallet user (you signed in with email or social login, and the console handles signing for you), stay on console.akash.network. 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 Console Air, 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.