ChatGPT is the interface
Users operate their AVM through the ChatGPT web and mobile app. The dashboard only handles account, billing, AVMs, and routing state.
bapX sells managed AVMs with Codex, Docker, project contracts, MCP routing, live previews, domains, and billing in one ChatGPT-native control layer.
Provider cost + fixed $5 bapX margin. Provisioning starts only after webhook verification.
bapX is the missing utility layer around ChatGPT and Codex: compute, routing, project contracts, payments, domains, and a thin MCP bridge.
Users operate their AVM through the ChatGPT web and mobile app. The dashboard only handles account, billing, AVMs, and routing state.
Codex CLI, MCP installs, browser use, tools, skills, shell, and project files already solve the agent layer. bapX exposes and orchestrates them.
The selected AVM opens the bapXvm panel for auth, database, storage, functions, sites, logs, and analytics. This repo stays the outer account layer.
The customer journey is deliberately narrow. Buy an AVM, connect ChatGPT, create a project contract, and deploy through the selected runtime.
Google OAuth creates the bapX account and profile state.
Checkout records the subscription before infrastructure exists.
Hetzner creates Ubuntu with Docker, Codex, Node, Git, and bapX bridge.
bapX MCP exposes the selected AVM, routes, previews, tools, and contracts.
App builders publish pages. Hosting panels sell VPS controls. MCP monitors watch servers. bapX ties all three into one ChatGPT-native AVM product.
ChatGPT builds in conversation, hosting lives elsewhere, domains are manual, and project context disappears unless the user explains everything again.
ChatGPT can see the selected AVM, installed tools, project contract, Docker status, preview URL, billing state, and routed domains through one MCP.
Each plan is a separate Hetzner instance, dedicated IPv4, and a fixed bapX margin. No instance before payment.
Starter project runtime with Codex and Docker.
Final price follows provider cost + IPv4 + $5 bapX margin.
Review AVM1Default solo-builder AVM for web apps, automations, and small SaaS products.
Review AVM2More room for multiple projects, heavier Docker services, and staged previews.
Storage add-ons use provider volume cost plus margin.
Review AVM3