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 to batch-process hundreds of models	❌ Desktop has batch limits	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 result

Three core differences:

1. No GUI (but a web admin console shows status)
2. Runs on a server, not on your machine
3. 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:

# 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/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/health

For 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/data) │  │
│                   └──────────────┘  │
└─────────────────────────────────────┘
         ▲
         │ mapped :8080
    your server

Only one port needs to be exposed (default 8080); data is persisted in the /app/data volume.