One system.
Three ways to pay.
The result is the same — background, plate, shadow, about 600 frames an hour. What differs is where the system runs and who maintains it.
01 · API
API by the token
Priced to your volumepay per photo
- REST and a queue, 2048 px results
- Make, model and dimensions in the response
- Background library + your own backgrounds
- Volume packages from 1,000 photos cost less
- You pay only for successful photos
- Never used for training, stored encrypted
02 · Dashboard
Manager dashboard
Priced to your volumeper seat per month + photos at API rates
- Batch uploads, no integration needed
- Manager picks the background and plate
- Never used for training, stored encrypted
03 · On-premise
Install on your own hardware
Pricing on requestlicense + rollout + support
- Everything on your own network, nothing leaves
- Runs on your own servers — about 600 frames an hour
- We hide the plate, blur it, or swap in yours
- License, rollout and support
30 framesfree pilot on your own photos
~600frames an hour
2048 pxresult, 4:3, plate composited in
No redrawcolor, chips and scuffs stay as shot
What runs where
| Question | API | Dashboard | On-premise |
|---|---|---|---|
| Where photos are processed | Our cloud | Our cloud | Your servers |
| Who maintains the servers | We do | We do | You, with our support |
| Integration | Your developers | Not needed | Our rollout team |
| Your own backgrounds and plates | Yes | Yes | Yes |
| Billing | Per photo | Seat + photos | License |