Zipoly Server Team Edition
What It Is in One Line
It turns the compression power of the Zipoly desktop app into a web service that runs on your own server, callable via API or operated from a browser.
Who Is It For?
| You are... | Is the desktop app enough? | Do you need Server? |
|---|---|---|
| 3D artist / designer | ✅ Yes | No |
| Individual developer | ✅ Yes | No |
| Team (3+ people sharing) | ❌ Installing per person is a hassle | Yes |
| CI/CD automation pipeline | ❌ Can't be automated | Yes |
| Data must not leave the intranet | ❌ Desktop runs on personal PCs | Yes |
| Need automated server-side batch processing | ❌ Desktop batching runs manually on your machine | Yes |
What Can It Do?
| Feature | Description |
|---|---|
| Model compression | Draco / Meshopt dual engines, 60%–90% GLB size reduction |
| Format conversion | Convert between 7 formats: GLB, glTF, FBX, OBJ, STL, DAE, PLY |
| Texture optimization | JPEG / WebP / PNG compression + KTX2 (Basis Universal) encoding |
| Model repair | Auto-remove empty nodes, fix normals, merge duplicate vertices, drop degenerate faces |
| Health check | Detailed reports: vertex count, face count, texture info, issue list |
| Batch processing | Submit dozens of files at once — auto-queued and processed concurrently |
Differences from the Desktop App
Desktop: open the app → drag in a file → click a button → download the result
Server: deploy to a server → call the API → processed automatically → download the resultThree core differences:
- No GUI (but a web admin console shows status)
- Runs on a server, not on your machine
- Called via API, so it can integrate with any system
How to Deploy?
All you need is a server that can run Docker. Three steps to get started:
- Load the image: unpack the release bundle and import the image tar
- Start the container: one
docker runcommand with your API Key and a data volume - Verify: hit the health endpoint — a normal response means the service is up
# 1. Load the image
docker load -i zipoly-server-v2.1.0-image.tar
# 2. Start it (one command)
docker run -d --name zipoly-server \
-p 8080:80 -v zipoly-data:/app/zipoly-data \
-e ZIPOLY__SERVER__API_KEY=your-key-here \
zipoly-server:2.1.0
# 3. Verify in the browser
curl http://localhost:8080/api/v1/healthFor detailed steps, see Docker Deployment.
Documentation Map
| I want to... | Read this |
|---|---|
| Deploy the service | Docker Deployment — from zero to running in 5 minutes |
| Call the API | API Reference — all endpoints, parameters, sample code |
| Tune the config | Configuration — concurrency, storage, logging, etc. |
| See the pricing | Server Licensing — plans & purchase |
Technical Architecture (for ops)
┌─────────────────────────────────────┐
│ Docker container │
│ │
│ ┌──────────┐ ┌───────────────┐ │
│ │ Nginx │───▶│ Zipoly Core │ │
│ │ :80 │ │ (Rust/Axum) │ │
│ └──────────┘ └───────┬───────┘ │
│ │ │
│ ┌──────▼───────┐ │
│ │ SQLite │ │
│ │ + file store│ │
│ │ (/app/zipoly-data) │ │
│ └──────────────┘ │
└─────────────────────────────────────┘
▲
│ mapped :8080
your serverOnly one port needs to be exposed (default 8080); data is persisted in the /app/zipoly-data volume.
FAQ
Does the Team edition upload models to your cloud?
No. The Team edition is self-hosted: the entire service runs on your own server/intranet and model data never leaves it — suitable for confidential workloads.
Can I run it without a License Key?
Yes. Without a License Key the server runs in trial mode (feature-limited). After purchasing, write the key into the environment variable and restart the container to unlock instantly — see Licensing & Pricing.
Is the license shared with the desktop edition?
No, they are independent: the desktop edition is licensed per device (GUI), the Team edition per seat (private API). A common setup: artists on desktop licenses, CI/CD and business systems on the Team API.
How is the Team edition priced?
Seat-tiered: ≤3 seats ¥299/year, ≤10 seats ¥599/year, unlimited seats capped at ¥999/year — invoices and contracts supported. See Licensing & Pricing.