Build from the live product
Each update extends an existing surface, a testable backend path, or a measurable production signal.
Roadmap / launch to v1
From verified jobs to a real compute network.
AlpenGlow moves in visible stages: strengthen the live proof surface, give developers a clean path into the network, then open the rails for agent payments and consumer demand.
01Live baseline
02Proof surface
03Developer v0
04Compatibility alpha
[ What changes next ]
From live foundation to v1.
The next updates build on what is already live: clearer receipts, public-safe activity, developer quickstarts, and one narrow compatibility path before larger x402, Chat, Create, and confidential-compute releases.
Compute demand first
The roadmap centers on jobs, receipts, providers, and developer usage before heavier token or enterprise claims.
Keep updates precise
Future x402, confidential compute, and consumer apps stay framed as staged work until each path is ready.
Current foundation
01
Live now
Live
Live launch baseline
The live dashboard, provider capacity, job posting, receipts, and production smoke checks form the current public baseline.
- Production web and API on mainnet configuration
- Provider capacity and public-safe activity signals
- Copyable launch contract section when final CA is set
Proof surface
02
Next update
Next
Receipts become the product moment
Bring completed work, verification state, and provider availability forward so visitors can understand what happened at a glance.
- Richer verified-job cards and receipt details
- Recent activity feed without sensitive identifiers
- Job/model catalog backed by supported templates
Developer v0
03
Near-term
Next
A real integration path before the full gateway
Document the current API clearly: create a job, confirm payment, poll status, and retrieve a receipt.
- Current API quickstart with curl, Node, and Python examples
- Usage and receipt examples that match production responses
- Cleaner API-key and environment guidance
Compatibility alpha
04
Alpha path
Planned
OpenAI-shaped inference, one narrow path first
Start the larger expansion promise with a small compatibility layer that is tested, observable, and honest about limits.
- One OpenAI-shaped text route for an allowlisted profile
- Compatibility tests for request, auth, errors, and response shape
- Provider assignment metadata for future served-by-node proof
Agent payments
05
Planned path
Planned
USDC and x402 in a controlled test path
Prototype agent-funded calls without putting production funds or custody assumptions ahead of review.
- USDC asset abstraction behind configuration
- x402 challenge-response in dev/test mode
- Reconciliation tests for mint, recipient, amount, and duplicates
Consumer demand
06
Later-stage
Later
Chat/Create only when the rails are real
Turn the API into visible demand with bounded consumer demos once routing, receipts, pricing, and observability are stable.
- Limited Chat demo backed by real provider assignment
- Create/image generation after a safe worker path exists
- Confidential compute and bandwidth earning remain later-stage work
[ Release posture ]
The next update should make AlpenGlow feel less theoretical.
That means fewer future-tense claims and more proof in the interface: verified receipts, live capacity, real usage, and a developer path that can be tried today.
Short cadence
Small updates that can ship and be checked.
Developer bridge
Docs and examples before a larger SDK promise.
Visible demand
Activity and receipts before consumer demos.