Skip to content

Last updated:

Licensing & Pricing ​

Zipoly Server licensing uses a two-layer model: the API Key governs interface access (who may call it), the License Key governs feature entitlement (how much you can use). Priced by team seat tiers, privately deployed, with invoices and contracts available.

Two-Layer License Model ​

The Team edition has two credentials with different responsibilities:

CredentialRoleHow to configure
API KeyInterface access — decides who can call, supports rate limitingZIPOLY__SERVER__API_KEY (set by you)
License KeyFeature entitlement — decides how much you can use, bound to a device fingerprintZIPOLY__LICENSE__KEY (obtained by purchase)

Without a License Key, the service runs in trial mode (feature-limited); it unlocks as soon as a key is configured. See Configuration for the trial mode switch.

Team Pricing (tiered by seats) ​

TierPriceSeatsPer seat / year
Small Team¥299 / year≤ 3 seats¥100
Standard ⭐Recommended¥599 / year≤ 10 seats¥60
Enterprise¥999 / year (cap)Unlimited (single deployment site)—
  • Every tier has identical features — only team size differs; add-on seats ¥99 / seat / year;
  • The ¥999 cap means even large teams pay at most ¥100 / seat / year — no price increase as you grow;
  • Renewal is 10% off; expiry does not affect data of a deployed service — it only restores trial mode limits;
  • All tiers come with invoices and contracts; Enterprise adds remote support with priority response; multi-site / group deployments — contact us for a custom quote.

How to Purchase ​

  1. Follow the WeChat Official Account RayChart and send zipoly telling us you need the Team Edition
  2. Mention your team size and chosen tier, then complete the payment (invoices and contracts available; keys are issued per seat manually)
  3. Once you receive the License Key, set it as an environment variable and restart the container:
bash
docker stop zipoly-server && docker rm zipoly-server
docker run -d --name zipoly-server \
  -p 8080:80 -v zipoly-data:/app/zipoly-data \
  -e ZIPOLY__SERVER__API_KEY=your-secure-api-key \
  -e ZIPOLY__LICENSE__KEY=your-license-key \
  zipoly-server:2.1.0
  1. Verify the license status:
bash
curl -H "X-API-Key: your-secure-api-key" http://localhost:8080/api/v1/license/info

Other Services ​

Compression-as-a-Service: don't want to deploy it yourself or compress it yourself? Send us your models — ¥50 per model, with before/after comparison data. Contact QQ 2162788746.

Desktop vs Server Licensing ​

Desktop (GUI)Server Team (API)
Licensed targetThe desktop app on one deviceA privately deployed HTTP service
PricingTrial ¥15 / Yearly ¥79 / Lifetime ¥199+Per-seat yearly from ¥299
ActivationPaste the key on the Account pageEnv var ZIPOLY__LICENSE__KEY
Best forIndividual developers, 3D artistsShared teams, CI/CD, intranet-only data

The two licenses are independent and not interchangeable; desktop pricing is covered in Licensing & Pricing. A common combo: artists on desktop licenses, business systems on the Team API.

FAQ ​

What's the difference between the API Key and the License Key? ​

The API Key is an access credential — it protects your API from unauthorized callers and is set by you. The License Key is a feature entitlement — it lifts the trial-mode limits and comes from purchase. Both are configured via environment variables (except in trial mode).

How are seats counted? What if the team grows? ​

Seats follow team headcount tiers (≤3 / ≤10 / unlimited) — concurrency and file counts don't matter. For temporary growth, add seats (¥99/seat/year) or upgrade a tier — under 10 people, moving up a tier usually beats buying seats one by one.

What happens when the license expires? ​

Nothing is deleted: the service falls back to trial-mode limits while your data stays intact. Renewal is 10% off; configure the new License Key and you're back at full capacity.

Can we evaluate before buying? ​

Yes. Deploy without a License Key and the server runs in trial mode — verify compression quality and API integration first, then purchase once it fits.

Built for Web3D developers