---
title: "ARX for ISVs"
description: "How ARX runs your application: package an image, describe it in an app template, ship it through App Market, and use the platform's model, network, and storage integrations"
canonical_url: "https://developer.ardge.com/en/guide/isv/overview"
---
# ARX for ISVs

> How ARX runs your application: package an image, describe it in an app template, ship it through App Market, and use the platform's model, network, and storage integrations

**You Build the AI. We Handle Deployment.**

When GPU servers move on-premises, deployment and operations become the challenge. ARDGE unifies GPU infrastructure, inference runtimes, service delivery, and remote management—helping teams move from validation to production faster.

## What ARX handles

- **The hardware and the system underneath** — the server, its GPU resources, and ARX OS are managed by the platform, not by you or your customer's IT team
- **Installation** — your application appears in App Market and the customer installs it from there
- **Version management and remote updates** — publish a new version and installed sites update in place, which is what makes post-sales maintenance and operations workable at a distance
- **Models** — an app template can declare the models your application recommends, so the customer deploys a matching model instead of guessing at one
- **Networking** — the services and ports your application serves are declared in `arx.yaml`, and the platform provisions them at install time
- **External storage** — mount a NAS shared folder through Storage Manager and assign it to your application, so it reads and writes enterprise data in place

## What you provide

A container image of your application, and three files that tell the platform what to do with it:

<table>
<thead>
  <tr>
    <th>
      File
    </th>
    
    <th>
      What it does
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        manifest.yaml
      </code>
      
       — the app template
    </td>
    
    <td>
      Your application's identity in App Market: name, version, categories, icon and screenshots, the resources it needs, the settings users fill in at install time, the models it recommends, and a pointer to the chart that runs it
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        arx.yaml
      </code>
    </td>
    
    <td>
      What your application asks the platform for — model API access, services and ports, storage slots, and a desktop shortcut. The platform provisions each one and injects its connection details into your pods
    </td>
  </tr>
  
  <tr>
    <td>
      Your Helm chart
    </td>
    
    <td>
      The workload itself. ARX renders it at install time with the values file that ships with the template, and the chart holds up the other end of every binding <code>
        arx.yaml
      </code>
      
       declares
    </td>
  </tr>
</tbody>
</table>

## The path from image to shipped product

Work through these five in order.

<card-group>
<card icon="i-lucide-file-code" title="1. Prepare your app template" to="https://developer.ardge.com/en/guide/isv/prepare-app-template">

Describe your application in the template that puts it in App Market and points at your chart

</card>

<card icon="i-lucide-cable" title="2. Prepare your arx.yaml" to="https://developer.ardge.com/en/guide/isv/prepare-arx-yaml">

Declare how the model API, network, storage, and desktop shortcuts reach your application

</card>

<card icon="i-lucide-box" title="3. Prepare your Helm chart" to="https://developer.ardge.com/en/guide/isv/prepare-helm-chart">

Package the chart ARX installs, and expose the labels and persistence values the platform bindings rely on

</card>

<card icon="i-lucide-upload" title="4. Publish to App Market for testing" to="https://developer.ardge.com/en/guide/isv/publish-to-app-market">

Import the template into an ARX system, install your application, and test it on real hardware

</card>

<card icon="i-lucide-handshake" title="5. Ship through the official channel" to="https://developer.ardge.com/en/guide/isv/shipping-channel">

Move from a test install to shipping your application to customers as an ARDGE partner

</card>
</card-group>

## Reference

<card-group>
<card icon="i-lucide-plug" title="Call on-premises models through the API" to="https://developer.ardge.com/en/guide/isv/api-model-calls">

Get the endpoint, API key, and model ID, then call a model on the system in OpenAI or Claude API format

</card>

<card icon="i-lucide-hard-drive" title="Mount remote storage for an application" to="https://developer.ardge.com/en/guide/isv/mount-remote-storage">

Enable NFS on the NAS, create a mount point in Storage Manager, and assign it to your application

</card>
</card-group>


## Sitemap

See the full [sitemap](https://developer.ardge.com/sitemap.md) for all pages.