What changes when the model runs locally
An app that runs a model on the user’s own machine costs you nothing per request. That removes the reason to check the license on your server, which is the central design of AI apps with a backend. Here the app is closer to any desktop program with a very large resource file. Three things set it apart.
The buyers value offline. People choose a local model for privacy, for use on a plane and to avoid a subscription to a hosted service. An app that phones home often, or stops working after a short offline stretch, undercuts the reason they bought it. Clavem’s signed token fits: the app verifies it with a public key and no network. The cost is the 14-day refresh_by, so you must decide what happens after it.
The files are huge. Weights range from a few hundred megabytes to tens of gigabytes. That matters for Clavem’s file limits and for download time.
The models have licenses of their own. You are selling an app, and the models inside it have terms that are not yours to change.
Choose a policy for long offline periods
Anyone using a local app on a laptop in the field, on a research cruise or in an air-gapped lab can be offline for longer than 14 days. After refresh_by, the app has to choose:
| Policy | What the app does | Good for | Cost to you |
|---|---|---|---|
| Strict | After 14 days offline, ask to connect once | Subscriptions, where a lapsed payment should stop access | Annoys travelers; produces support mail |
| Grace | Keep working for a fixed extra period, such as 30 days, with a banner | Most paid apps | A few extra days of use after a refund |
| Signature only | Accept any validly signed, unexpired token forever | Perpetual licenses sold to privacy-focused users | A revoked key keeps working offline |
A token carries exp for licenses that expire, so a subscription still ends: the app checks exp even when it ignores refresh_by. A perpetual license has no exp. The offline page shows the checks. Say your policy on the product page; buyers of local software read it.
Model files and Clavem’s limits
Clavem hosts release files for gated download. Each file can be up to 5 GiB, and each plan includes storage: 1 GB on Free, 10 GB on Indie, 50 GB on Studio and 250 GB on Scale. Downloads are not metered.
As an example, a 4-bit quantized model of 7 billion parameters is roughly 4 GB. An app that ships three such models and a 200 MB installer needs about 12 GB for one version. That does not fit Indie’s 10 GB and does fit Studio’s 50 GB, with room for two versions. Weights over 5 GiB must be split into shards, which your app reassembles.
Three layouts work:
- Models are downloaded from their publisher. The app fetches open weights from where they are hosted, at first run. Clavem hosts only the app. This is the cheapest, and it keeps you out of redistributing weights.
- Your own fine-tuned model is the product. Upload it to Clavem as shards. The buyer’s key gates the signed link, so only paying customers download it. Links last an hour; request one when the user clicks.
- Both. Public weights from their publisher, and your proprietary add-ons from Clavem.
Verify downloads in the app with a checksum you publish, because a 6 GB download that is interrupted and resumed must be correct. Clavem’s downloads support byte ranges, so resuming works; see releases and downloads.
Model licenses
Open-weight models come under very different licenses. Some permit commercial use freely, some set conditions or size thresholds, and some forbid commercial use. Before you charge for an app that bundles or downloads a model:
- Read the model’s license, not a summary of it.
- Check whether you may redistribute the weights, or must send users to the publisher.
- Check attribution and naming requirements.
- Keep a record of which license applied to which version you shipped.
This is general information, not legal advice. If the terms are unclear and money is at stake, ask a lawyer. A license key for your app controls access to your app only.
Devices and hardware
The same machine can look different to your app after a GPU change, a driver update or a switch between integrated and discrete graphics. Do not build a fingerprint from GPU details. A hash of a stable machine identifier, or a random id stored in the app’s data folder, is safer. Activating again with the same fingerprint returns the same seat, so a stable one keeps reinstalls free.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Perpetual, or a subscription if you ship new models | Perpetual suits an offline tool; subscriptions fit ongoing model releases |
| Device limit | 2 or 3 | Desktop and laptop; local models need strong hardware, so few machines |
| Trial | 7 to 14 days, or a free tier with a small model | Let people test on their own hardware |
Policy after refresh_by |
Grace period of 30 days, stated on the product page | Respects offline users while still ending access eventually |
Doing this with Clavem
Create a product, connect Stripe, map the price. A buyer gets a key and an order page with the installer. In the app, activate once, store the token, and verify it at launch with no network; validate online when a connection exists. The Rust and Swift guides, Rust and Swift, show verification with native Ed25519 libraries. For a Python-based app, the Python guide does the same.
Guides to follow
- Offline license verification in Rust
- Offline license verification in Python
- Device activation in Swift
- Software updates in Rust
Questions
Can I sell an app that runs open-weight models?
It depends on each model's license. Some allow commercial use freely, some add conditions or limits, and some forbid it. Read the license of every model you bundle or download, and get legal advice if the terms are unclear. A license key for your app does not change what a model's license permits.
How big can a downloadable model file be on Clavem?
Each release file can be up to 5 GiB, and plans have a storage total of 1, 10, 50 or 250 GB. Larger weights should be split into parts of 5 GiB or less, or hosted elsewhere, with Clavem used for keys and for gating the app download.