Custom Domain Configuration via Akash Console

Draft

Motivation

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

Summary

Users of Akash Console will have the option of choosing their DNS provider of choice from a set of available options and then configuring custom domain. Console would take care of authenticating the user (via the API credentials for the speicifc DNS provider) and settin the configuration.

Estimated completion: 1/15/2026

Created: 12/1/2024

Last Updated: 7/7/2025

Category: Interface

Status: Draft

Authors:

Anil Murty

View next aep

Estimated Completion: 1/30/2026

Currently, hardware provided by a provider is verified using a decentralized network of Auditors on Akash. While this approach is practical for a limited set of providers, the manual verification is proving challenging at scale, even more critical when incentives go onchain and are distributed without a human in the loop. Hardware Verification using Trusted Execution minimizes trust required to verify the accuracy of hardware provided by the providers on Akash network and serves as a fundamental building block for enabling Confidential Computing capabilities, as detailed in AEP-65.

Experience the Supercloud.