Scroll

Generative AI, on your shots

Image, video and 3D generation, handed to your artists as tools they can actually use: a few fields to fill in, and the frame comes back.

A module of the GT platform, by Gear Productions.

Every frame generated on your own machines

An open stack, self-hosted end to end. No external API, no third-party service, no plate leaving your network confidentiality is a property of the install, not a clause in a contract.

The same plate before and after a Workflow Studio pass: the car repainted from grey to yellow

One engine, three ways to drive it

The same workflows, reached three ways: fill in a form, just ask, or build your own chain. Take whichever suits the shot.

FILL IN THE FORM

Generate your images with full control, in full privacy

Every workflow opens as a plain form: the settings that matter, laid out clearly, and nothing else.

Drop in your image, adjust what you want, press generate. Nothing leaves your building: your shots stay on your own machines, start to finish.

A paint-transfer workflow in Workflow Studio: its form on the left, the generated car on the right
A workflow being configured and run in Workflow Studio

Built for production

Long runs, heavy binaries and closed networks are the normal case here, not the edge case.

  1. Image editing in the flow

    01

    Crop, adjust brightness, saturation and contrast, draw or retouch masks: five independent tools sharing one work plane, without leaving the workflow.

  2. Preview while it generates

    02

    Images appear step by step instead of only at the end. 3D models rotate, pan and zoom in place; video and stills get a proper viewer.

  3. Distributed execution

    03

    Jobs queue on BullMQ with state in Redis, a 30 s heartbeat, per-workflow timeouts, exponential backoff and SSE streaming. Load spreads across every configured compute server.

  4. History you can walk back

    04

    Inputs, generations and workflow edits are all kept, timestamped, diffed field by field, and restorable to an earlier version. Client cache means browsing it costs nothing.

  5. On-premise and offline

    05

    Our custom ComfyUI package can run on both Windows or inside a container (Podman, Docker, ...). Our custom nodes are embedded directly inside the package and we provide the models so you can run fully offline, without any external dependency on non-European cloud services.

  6. Train your own models

    06

    A guided two-step LoRA trainer: build the image set with a trigger word and auto-generated captions, pick a base model and launch. Training distributes across remote servers and resumes after a failure.

A backend that survives the browser tab

Long treatments carry on server-side. Close the window, come back later, the result is waiting.

  1. Service isolation

    01

    A standalone backend service with its own GraphQL API, talking to the rest of the platform over Redis Pub/Sub. It holds no direct database access of its own.

    GraphQL · Redis Pub/Sub
  2. GPU stays remote

    02

    No GPU runtime in the service itself. Execution is delegated to remote ComfyUI containers over the API, so the backend deploys on any machine.

    node:20-alpine · multi-stage build
  3. Pluggable engines

    03

    Independent engines you switch on or off per deployment: ComfyUI for generation, Deadline for rendering, Captions for automatic subtitles.

    ComfyUI · Deadline · Captions

Bring generative AI onto your own pipeline

Deployed on your infrastructure, in a closed network if that is what the project requires.

Currently used by