Minify
Front-end optimization on the same spine
JS and CSS jobs with the same tenancy, audit, and quota as image and video — built for multi-brand themes and release gates, not one-off CI scripts. Flows orchestration for minify steps is not the first vertical; call the Minify API directly today.
What you get
JS & CSS as platform jobs
Minify, mangle, and compress with checksummed outputs and optional sourcemaps — idempotent and evented.
Release-gate telemetry
Size deltas and job events your CI can block or approve on before publish.
Multi-brand isolation
Per-project theme assets never mix. Same org → workspace → project model as media.
API-first today
Wire minify from CI or portal jobs. Shared Flow steps for minify are not shipped yet.
Differentiation
Minify platform depth
- JS minify with mangle and compress options
- CSS minify and size reporting
- Content-hash output names
- CI/CD gate events
- Workspace retention policies
- Tenant quota on job compute
- Same auth and audit model as Image / Video
- Flows step for minify — not in the first vertical
Example
Same auth and tenancy headers as the rest of the API. Where a capability plugs into Flows today, that is called out on the product page — we do not imply every media type shares one live pipeline yet.
POST /v1/minify/jobs
{
"sources": [
{ "object_id": "obj_app_js" },
{ "object_id": "obj_theme_css" }
],
"options": {
"js": { "mangle": true, "sourcemap": false },
"css": { "level": 2 }
},
"quota_account": "ws_acme_eu"
}Ship with Minify
Open the portal, follow the docs, or talk to us about rollout for your agency or commerce stack.