azphaltThe open standard for portable extensions.

One host-agnostic package format for brushes, LUTs, shaders, models, video, audio, and code — plus a neutral marketplace at azphalt.store that any app can consume and any creator can publish to.

Use the Store in Your App

Build & Publish an Extension

Browse azphalt.store ↗

Consume the marketplace

azphalt.store implements the normative Repository API, so your app browses, searches, and downloads .azp packages with one small client — no store-specific code. Free packages are open; paid ones unlock with a signed, offline-verifiable entitlement token.

Consume a repository

Build once, run everywhere

Bundle a sandboxed code extension (JS/WASM) or an asset pack (brushes, LUTs, shaders, meshes, video, audio, fonts) into a single .azp. Capability-gated by construction — an extension reaches exactly what it declares and nothing else.

Get started

Publish — free or paid

Ship to the open registry lane for reach without a fee, or consign onto the paid lane and keep your split via Stripe Connect. The fee lives only on listings; it never leaks into the open registry.

Publish & sell

Neutral & self-hostable

The standard is open and the Repository API is self-hostable — azphalt.store is one repository, not a gatekeeper. Run your own catalog from the reference server (`apps/repository-server` in the repo, or `npm create azphalt` → Repository Server) and the same client works against it.

Read the spec

Verified production catalog

azphalt.store is deployed from the git-backed registry through the centralized workflow controller. Deployment verifies the exported catalog and then proves the live Repository API exposes known app-scoped workflow/role packages instead of silently shipping an empty store.

Production operations