NVIDIA Blackwell is coming to Akash. Join the waitlist.
Akash's roadmap outlines the high-level goals and priorities for the Akash Network.
aep-32
Estimated Completion: 1/30/2025
Make Akash Provider set up and management easy, with the goal of onboarding 100s of new providers.
aep-57
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-56
Estimated Completion: 2/15/2025
Integrations are a key part of Akash's growth strategy. In order for integrations to happen quicker Akash needs first class API support, coupled with easy to follow documentation and support for multiple programming languages.
aep-30
Estimated Completion: 2/28/2025
Akash Network has been live for almost 4 years, and we have made incredible strides in decentralizing development, coordination, and funding.
aep-33
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-34
Estimated Completion: 3/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-59
Akash users would like to be notified when a provider intends to go offline for maintenance or has an outage.
aep-35
Estimated Completion: 3/30/2025
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-37
Estimated Completion: 4/30/2025
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-41
Consistent provider attributes let clients and users be able to query and filter on them.
aep-40
Estimated Completion: 5/15/2025
One of the barriers to Akash adoption is giving users confidence that providers on the network can be trusted.
aep-54
Akash providers and users would like to be able to provide and user AMD GPUs.
aep-58
Akash users frequently receive no bids from providers even though there are enough GPUs on the provider because either there aren't enough GPUs on a single node or there are not enough other resources (CPU, Memory, etc.) on a single node.
aep-53
Estimated Completion: 5/30/2025
Users want to be incentivized to provide compute resources to the network.
aep-12
Estimated Completion: 6/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-36
Many users of Akash Console deploy apps and services that need a custom domain. Configuring the mapping from the endpoint (or port mapping) received when the lease is created requires going into a separate UI (like Cloudflare). Allowing this configuration within Console makes UX better
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-43
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-52
Being able to select one or more backup providers and have the deployment be redeployed to them automatically if/ when the primary provider has an issue
aep-55
Credit card transactions in USD are converted to USDC to maintain exact balance equivalence, ensuring a smooth user experience. This approach, however, reduces AKT demand, potentially compromising Akash's security. To mitigate this, a protocol-imposed fee (Take Fee) is applied when using USDC for compute payments. AKT stakers determine this fee through governance proposals.
aep-29
Estimated Completion: 7/1/2025
Verification of resources is critical for on-chain incentivization; hence, we propose a TEE-based verification mechanism detailed below and extend the Trusted providers proposal.
aep-38
Estimated Completion: 7/30/2025
Providers need to protect themselves and their company/ brand from being tarnished
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-42
Estimated Completion: 12/30/2025
Being able to store logs on Akash (or other decentralized storage) reduces cost for customers
aep-47
Estimated Completion: 12/31/2025
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