Offchain Compute Inventory

Draft

Motivation

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.

Summary

This would require gathering inventory from existing providers of compute that hasn’t yet been brought on to Akash. The inventory should ideally be updated through an API but could potentially be done manually by the providers as well.

Estimated completion: 8/31/2026

Created: 12/1/2024

Last Updated: 12/1/2024

Category: Interface

Status: Draft

Authors:

Anil Murty

View next aep

Estimated Completion: 9/30/2026

This AEP proposes **replacing the current "Build & Deploy" feature in Akash Console with a Cloud Native Buildpacks** (buildpacks.io) pipeline. The existing flow — referenced via `CI_CD_TEMPLATE_ID` in `apps/deploy-web/src/config/remote-deploy.config.ts` — is in a broken state, hard-coded to a small set of JavaScript web frameworks, and relies on language detection that only reads `package.json`. Anyone deploying a Python, Go, Ruby, Java, Rust, .NET, or PHP application currently has to abandon the flow and produce a Dockerfile manually.

Experience the Supercloud.