Skip to content

SialFlow · Secure delivery service

Secure delivery for images, video and documents.

Every request is checked against policy and tenant quota before work runs. Images are transformed at request time and delivered through signed URLs. Heavier video and document work runs as durable jobs, and the status, retries and output of each run stay on record.

CheckPolicy & quota before work
TransformImage, video, documents
DeliverSigned URLs at the edge
RecordJob history & retries

What SialFlow is

One controlled path from storage to the person or system that receives the asset.

Image manipulation, video processing and document extraction run against a shared API and job model, behind one policy layer. A request is authenticated, scoped to a project, checked against policy and tenant quota, and only then processed and delivered.

The platform is shaped by media and delivery systems we have had to run and protect ourselves.

  • Bearer auth and project scope on every request
  • Policy and quota checks before work runs
  • Signed delivery URLs
  • Durable jobs with retries and history
  • Storage connectors that keep your objects yours
  • Webhook events on completion
SialFlow media workflow platform
api.sialflow.com · background remove
POST /v1/images/{id}/bg-remove
{ "format": "png" }

→ 202 job kind=bg_remove
   poll GET /v1/images/jobs/{id}

Capabilities

Image, video and documents.

One job model, one policy layer and one set of events. Different workers underneath.

Image

Smart crop, background remove, responsive variants, bulk jobs and versioned transform profiles at catalogue scale.

Video

VOD encoding, batch processing, thumbnails and clip workflows on the same job and telemetry model.

Document

OCR, conversion, structured extraction and review states, run as workflows rather than one-off scripts.

Moderation & enrichment

Background remove is live. Broader enrichment and moderation queues are in development on the same job model.

Execution

Example image pipeline

From ingest to delivered variants, each step recorded as a durable job.

  1. 01

    Ingest

    Object upload completes; the asset enters the workflow.

  2. 02

    Validate & policy

    MIME inspection, policy and tenant quota checks before any expensive work runs. A request that fails here produces no output.

  3. 03

    Transform

    Background remove, smart crop and named transform profiles run as durable jobs.

  4. 04

    Deliver

    Variants are served through signed delivery URLs, with the job history attached to the run so what was produced can be inspected later.

On-demand manipulation

On-demand and background jobs

Fast image operations can run through the delivery URL. Compute-heavy work becomes a durable asynchronous job with status, retries and history.

On-the-fly image transforms

Resize, crop, change format, apply overlays and generate responsive variants through a compact URL grammar, without preparing every derivative in advance.

Smart manipulation

Entropy-aware smart crop and background removal help turn one master image into channel-ready outputs. Alpha PNG and WebP delivery can be requested synchronously where supported.

Heavy work as durable jobs

Bulk image processing, VOD encoding, thumbnails, OCR and document extraction run asynchronously so clients do not have to hold open fragile requests.

Inspectable history

Input, transform profile, workflow version, retries and output stay attached to the run, so a team can see what produced a given asset.

delivery path · responsive image
GET /i/{org}/{image}/w800-h600-fit-cover-g-auto-f-webp/product.webp

→ resize · smart crop · WebP · delivered at the edge

Architecture

Platform architecture

Requests are authenticated, checked against policy and tenant quota, queued, processed by the relevant worker pool, then closed out with an event. The client never decides what it is allowed to receive.

request path
Client
  ↓
SialFlow API        (bearer auth, project scope)
  ↓
Policy & quota      (tenant concurrency limits)
  ↓
Job queue
  ├─ image workers
  ├─ video workers
  └─ document workers
  ↓
Object storage      (yours or ours)
  ↓
Events / webhooks
  • Durable job execution
  • Tenant quota & concurrency
  • Fair scheduling & retries
  • Provider-neutral workers
  • Outbox events
  • Versioned transform profiles

Solutions

Use cases

Three common shapes: e-commerce, agencies and publishers.

E-commerce

Catalog & campaign assets

Ingest → moderate → transform → variants → deliver. PDP-ready outputs with auditable preparation jobs.

Agencies

Multi-client delivery

Templates, brand policy gates and bulk runs in client-scoped workspaces.

Publishers

Editorial across media

Image, video and document work in one place, from ingest to publish-ready.

Status

Product status

Available now

  • Request-time image transforms through the delivery URL
  • Background remove and smart crop
  • Bulk image jobs with status and retries
  • Video encoding and thumbnail jobs
  • Document OCR and extraction
  • Webhook events on job completion

In development

  • Broader AI enrichment
  • Moderation queues

Security boundaries

  • Org, workspace and project context scopes work and credentials
  • Delivery URLs are signed; policy and quota are evaluated on the server
  • Worker pools are interchangeable execution capacity, not a fixed provider
  • Storage connectors keep object ownership on your side of the boundary
  • Jobs and events form the operational record; there is no separate audit product

FAQ

FAQ

What is live today?

Image pipelines, background remove, video encoding and document extraction are live. Broader AI enrichment and moderation queues are in development.

Which operations can run on the fly?

Image delivery supports request-time transforms such as resize, crop, format conversion, overlays and responsive variants. Heavy work such as bulk processing, encoding or extraction runs as asynchronous jobs with status and retries.

Do image, video and documents share the same API model?

Yes. Bearer auth, project scope, async jobs and outbox events follow the same model across capabilities.

How do we start?

Tell us the first workflow: an image pipeline, a video job or a document flow. We can point you at portal access and documentation.

Next step

Start with one delivery path.

An image catalogue, a video job or a document flow is enough. Full API detail is on sialflow.com.