All systems operational

Media delivery built for the edge.

Fenmax stores, transforms and streams images and video from a single endpoint. Origin pulls, on-the-fly resizing and adaptive bitrate — without running your own pipeline.

Read the docs Endpoint reference
38
Edge locations
14 ms
Median TTFB
99.98%
Delivery uptime
4.2 PB
Served this month

Platform

One endpoint, the whole pipeline

Point your origin at Fenmax and request any derivative through URL parameters. Transformations are cached at the edge on first request and served from memory afterwards.

Image transforms

Resize, crop, rotate and re-encode on request. AVIF and WebP negotiated per client, with JPEG fallback.

Adaptive streaming

Uploads are packaged into HLS and DASH renditions automatically. Players get the ladder that fits the link.

Anycast edge

Requests land on the nearest node. Origin shielding keeps your storage from seeing repeat traffic.

API

Predictable, boring, documented

A REST interface over HTTPS with bearer tokens. No SDK required — every operation is a single request.

  • Signed URLs with configurable expiry
  • Chunked and resumable uploads
  • Webhooks on transcode completion
  • Purge by path, prefix or tag
curlnodepython
# upload an asset
curl -X POST https://fnmx.rex-fast-tomato.xyz/v1/assets \
  -H "Authorization: Bearer $FENMAX_TOKEN" \
  -F "file=@poster.jpg" \
  -F "tags=campaign,autumn"

# => 201 Created
{
  "id": "as_7Kq2mVx9",
  "bytes": 482113,
  "status": "ready"
}

# request a derivative
GET /v1/i/as_7Kq2mVx9?w=960&fit=cover&fmt=auto

Reference

Endpoints

Base URL is your delivery hostname. All responses are JSON unless the route serves binary media.

MethodPathDescription
POST/v1/assetsUpload a new image or video asset
GET/v1/assets/:idRetrieve asset metadata and rendition list
GET/v1/i/:idServe a transformed image derivative
GET/v1/v/:id/master.m3u8HLS master playlist for an encoded video
POST/v1/purgeInvalidate cached objects by path or tag
GET/v1/usageBandwidth and storage for the current period