NVIDIA B200/300 are coming to Akash - Get Early Access
Get Involved
Product Strategy
Roadmap
Current Groups
Funding Programs
Akash's roadmap outlines the high-level goals and priorities for the Akash Network.
aep-57
Completion Date: 1/30/2025
Akash users would like to have the option of having their escrow account automatically topped up from their wallets or accounts (in case of credit cards) so that it doesn't run out of funds and close their deployments.
aep-32
Completion Date: 2/18/2025
Make Akash Provider set up and management easy, with the goal of onboarding 100s of new providers.
aep-61
Completion Date: 3/12/2025
Improve the read performance of the blockchain API by optimizing prefixes in `x/stores` based on object states.
aep-62
Completion Date: 4/17/2025
Akash providers frequently start out with a small cluster (with 1 or 2 nodes) and then expand over time.
aep-63
Completion Date: 5/28/2025
The number of Managed Wallet (Credit Card) users in Akash Console has grown significantly since launch. As these users and customers look to scale their applications they need a programmatic way to deploy and manage the lifecycle of their workloads on Akash so that they can scale up/ down in response to demand for their applications.
aep-33
Completion Date: 6/30/2025
One of the primary issues users face with Akash is the unexpected termination of leases due to depleted escrow funds. Implementing an alerting and notification system for this problem gives users the tools to monitor and take actions to alleviate the problem and associated frustration.
aep-71
Completion Date: 7/17/2025
A users deployment can close becaause of reasons besides running out of funds (which is addressed as part of aep-33). This second type of Alert and Notification lets the user know immediately when a deployment is closed for any reason.
aep-69
Completion Date: 7/25/2025
GPU providers using provider Console need to pull data into their own dashboards for financial and other reporting
aep-68
Completion Date: 7/31/2025
As number of credit card users in Akash Console grows, a common request we here is being able to view usage and billing info
aep-34
Estimated Completion: 8/15/2025
Customers need to be able to debug issues that occur with their deployments. In the absense of log forwarding, customers can only view limited logs in Console and the logs are lost when the lease closes
aep-64
This AEP proposes implementing JWT (JSON Web Token) authentication for the Akash Provider API. This enhancement aims to improve the reliability of client API communication with leases during blockchain maintenance periods and provide more granular access control capabilities.
aep-59
Estimated Completion: 8/30/2025
Akash users would like to be notified when a provider intends to go offline for maintenance or has an outage.
aep-67
Users often see plenty of available GPUs on the pricing page but fail to receive any bids for their deployment. This causes users to think that the service is broken and likely give up on investigating further. Providing users guidance on why this is may be happening will go a long way in improving adoption.
aep-70
Accessing the API requires creating a certificate and working with mTLS. JWT eliminates the need for these.
aep-72
Akash Console is the primary way that new users discover the magic of Akash Network and as such it is very important that the UX for getting them started be streamlined for maximum success along with somewhat generous trial credits comparable to other clouds (CSPs) in the industry.
aep-75
This AEP proposes enhancement of the `x/escrow` module with support of multiple funds depositors, enabling flexible fund management and improved automation workflows for deployment operations.
aep-30
Estimated Completion: 8/31/2025
Akash Network has been live for almost 4 years, and we have made incredible strides in decentralizing development, coordination, and funding.
aep-73
Informing Akash users and customers about what new products & features have been introduced will go a long way in driving retention. This is particularly important now as the Akash Core team and community have been rapidly adding new functionality to the products and platform this year.
aep-29
Estimated Completion: 9/15/2025
Hardware Verification is an important aspect of improving the credibility of a decentralized platform like Akash and is a key component to achieving support for Confidential Computing as outlined in AEP-65
aep-37
This proposal aims to implement a lease control API using Protocol Buffers (protobuf) and gRPC. The new API will enhance performance, efficiency, and maintainability by leveraging gRPC's advanced features.
aep-56
Integrations are a key part of Akash's ecosystem growth strategy. In order for integrations to happen quicker Akash needs a feature rich and easy to use library for both blockchain nodes and provider nodes.
aep-12
Estimated Completion: 9/30/2025
Trusted Execution Environment (TEE) guarantees code and data loaded inside to be protected with respect to confidentiality and integrity that is enforced at the processor level.
aep-35
New users (unfamiliar with Akash) often struggle to find provider pricing within Console and don't realize that they need to create a deployment to see it.
aep-74
Making it easier for existing paying users to keep their deployments running without needing to manually intervene on the payment side, improves user experience and drives utilization higher
aep-41
Estimated Completion: 10/30/2025
Consistent provider attributes let clients and users be able to query and filter on them.
aep-43
Estimated Completion: 11/15/2025
Tenants/ users of Akash expect to be able to see what amount of allocated resources are being used by their workloads so that they can better manage peak load and also optimize cost/ spend
aep-45
Estimated Completion: 11/30/2025
Show users what compute inventory could be brought on to the network if there was demand with the intention of attracting larger customers and training workloads who may be turned off by the limited number of available GPUs, particularly as demand increases.
aep-50
Users want to manage secrets for their applications in a secure and easy way.
aep-66
## Abstract
aep-76
AKT is the native cryptocurrency of Akash Network and was initially conceived as the sole payment method. When a lease is established, tenants and providers agree on a price in AKT. These leases are open-ended, continuing until either party terminates them. However, the fluctuating value of AKT presents a challenge. Participants typically anticipate stable pricing equivalent to USD, and AKT's price instability compromises its utility as a payment mechanism.
aep-54
Estimated Completion: 12/15/2025
Akash providers and users would like to be able to provide and user AMD GPUs.
aep-38
Estimated Completion: 12/31/2025
Providers need to protect themselves and their company/ brand from being tarnished
aep-39
Tenants are often confused by why a lease was closed and in most cases they assume it was an issue with the provider while that isn't always the case (can be caused by funds running out or an issue with the tenant container etc)
aep-47
In times of peak demand some users aren't able to get the resources they need and must repeatedly keep trying. Allowing users to have orders that remain until fulfilled (similar to a trading platform) would improve the user experience for such users
aep-60
Enabling the average "home" user to participate in Akash as a provider is critical to both - scaling the supply side of the network as well as positioning the network to lead in the shift away from large data center compute in response to the oncoming energy crisis
aep-65
Public clouds (like AWS, Azure and GCP) support Confindential Computing because some customers request this before they agree to migrate workloads from their own DCs to public cloud infrastructure. While a vast majority of users don't ask the public clouds for this (and just blindly "trust" them) this is likely to become a challenge for Akash's growth particularly because infractstructure on Akash is owned by 10s if not 100s of independent providers.