Based on 5 reviews
azphalt is an open standard for portable digital-art, motion-graphics, and video extensions packaged in a host-agnostic .azp format. It supports brushes, LUTs, shaders, models, video, audio, fonts, and sandboxed code extensions. The project provides a normative Repository API for browsing, searching, and downloading these packages. It operates a companion marketplace at azphalt.store where creators can publish free or paid extensions.
Creators can publish free packages in an open registry lane or consign paid ones to receive revenue through Stripe Connect. The fee applies only to paid listings and never leaks into the open registry. Publishers can list free packages without a fee, while paid listings incur a fee that covers the listing itself. The standard is designed to be neutral and self-hostable with a refereed specification.
The marketplace allows any app to consume the .azp packages and any creator to publish to it. Apps can browse, search, and download .azp packages with one small client using the Repository API. There is no need for store-specific code to integrate the marketplace into an application. The format supports a wide variety of digital assets including shaders and sandboxed code.
Free packages are open and accessible to everyone without restrictions. Paid packages unlock with a signed, offline-verifiable entitlement token. This token ensures that only authorized users can access the premium content. The system uses capability-gated construction so an extension reaches exactly what it declares and nothing else.
The standard is open and the Repository API is self-hostable, meaning azphalt.store is one repository rather than a single gatekeeper. Organizations can run their own catalog from the reference server or use the npm create azphalt command to set up a Repository Server. The same client works against any self-hosted instance of the repository. This ensures neutrality and flexibility for different deployment environments.
The production catalog is deployed from a git-backed registry through a centralized workflow controller. Deployment verifies the exported catalog and proves the live Repository API exposes known app-scoped workflow/role packages. This process prevents silently shipping an empty store and ensures the live API is correct. The system is designed for verified production operations and reliability.
Some reviewers praise the open standard and the ability to bundle sandboxed code extensions or asset packs into a single .azp file. The capability-gated construction is noted as a key feature that ensures extensions reach exactly what they declare. Users appreciate the neutral marketplace that allows any app to consume the packages without proprietary lock-in.
The business operates at azphalt.org and provides a companion marketplace at azphalt.store. The project is focused on computer software, internet services, and media production industries. It serves creators who need to publish extensions and developers who want to consume them in their applications. The standard is intended to be universal and applicable across different hosts.
The official website of azphalt is azphalt.org.
On Trustburn, azphalt has a rating of 3.6 out of 5 based on 5 reviews.
AI-generated from reviews on this page. Verify anything important with the company directly.
Azphalt positions itself as a neutral marketplace, which is nice. However, comparing it to other existing stores, the unique selling point seems to be the open standard format. It is not entirely clear if this offers enough advantage over established platforms to warrant the switch.
While the concept of an open registry lane is intriguing, the financial model lacks transparency in critical areas. The text states that fees live only on listings and never leak into the open registry, yet it does not explicitly define what constitutes a listing fee versus other potential costs. For creators, the distinction between the open lane and the paid lane managed via Stripe Connect is noted, but the exact split percentages are not clearly detailed in the provided information. The phrase 'free packages are open' suggests no cost, but it is unclear if there are hidden infrastructure costs for consuming packages through the client. Furthermore, the self-hostable aspect requires running a specific server, which introduces operational complexity and potential costs not accounted for in the standard description. Until the fee structure is explicitly spelled out with concrete numbers, potential publishers may find it difficult to calculate true profitability. The lack of clarity on whether the open registry is truly free beyond the listing fee is a significant concern for small-scale creators who rely on predictable overheads. Additionally, the requirement for a signed entitlement token adds a layer of dependency that might not be immediately obvious to all users. Without explicit pricing details, the promise of a neutral marketplace remains somewhat theoretical.
Reading through the specifications, the concept of a neutral marketplace seems sound, though the full implications of the Repository API are not entirely clear yet. The idea that any app can consume these packages is appealing, but one must verify the actual client implementation details. The entitlement token system for paid content offers a layer of security, yet the offline verification process remains a point of interest. It is a promising framework, but users should carefully review the specs before committing to the ecosystem, as the self-hostable nature implies a degree of technical responsibility.
The support for varied asset types within one package format is impressive. Being able to include brushes, models, and code together provides great flexibility for creators.
Azphalt offers a practical solution for managing portable extensions across various host applications. The ability to bundle diverse assets like shaders, audio, and code into a single package simplifies distribution significantly. The open standard appears robust for developers seeking a unified approach to content delivery without vendor lock-in.
No news yet. This is where the business shares its own updates and press.
No photos yet. Photos shared by reviewers will show up here.
azphalt describes itself as an open standard for portable digital-art, motion-graphics, and video extensions, packaged in a host-agnostic .azp format that supports brushes, LUTs, shaders, models, video, audio, fonts, and sandboxed code extensions. The project provides a normative Repository API for browsing, searching, and downloading these packages, and it operates a companion marketplace at azphalt.store where creators can publish free or paid extensions. Publishers can list free packages in an open registry lane or consign paid ones and receive revenue through Stripe Connect, with the fee applying only to paid listings. The standard is designed to be neutral and self-hostable, with reference server software and client libraries that allow other applications to run their own compatible catalogs.