A multimodal line for short dramas going global

Novels in, episodes out

Compute, models and the editor share one system. One account calls 100+ models, and rendering sits next to the audience you publish to — no stack to assemble yourself.

100+
models behind one API
4
compute regions being rolled out
L1–L3
compute, models, apps we run
  • 01

    Rewrite the script

  • 02

    Break into shots

  • 03

    Lock cast and sets

  • 04

    Render a rough cut

  • ENJAID
    05

    Voice and lip-sync

How an episode is made01–05

Three layers we own, so issues never get bounced

One team wires the data hall to the canvas, so a fault is not passed between vendors.

L3

Cirrus TV

SaaS

Where the work happens: an infinite canvas that wires image, text, audio and video nodes into a flow you can run again.

Infinite canvas
Heterogeneous nodes connect directly, with agents arranged across the graph.
Private asset library
Boards, scripts, characters and cuts are archived in full, becoming an IP stock you keep using.
Side-by-side compare
Run several models on one prompt, and stay in sync across devices.
L2

Token Factory

MaaS / PaaS

Major closed and open models sit behind one interface, so routing, billing and unit cost settle in one place.

100+ models, one API
Integrate once and call leading closed and open models through the same fields.
One account, one bill
All model spend lands on a single account, with multi-currency line-level invoices.
Cheaper inference
Prefill/decode split and KV-cache management bring the cost of each token down.
POST /router/v1/models/invokeSame endpoint — change the model field, not your code

Pick a model

Loading available models

The request this sends

{
  "model": "model-name",
  "input": {
    "prompt": "Rewrite this passage as the opening dialogue of a 30-second episode, and mark the shot changes."
  }
}
Opens the playground for this model; you sign in before it runs.
L1

Global compute base

IaaS

Owned clusters plus managed nodes, placed around the markets short dramas release into, so video jobs are not waiting for cards.

Render nodes near the market
North America, Japan and Korea, and Southeast Asia — local rendering, low-latency delivery.
Flagship compute pool
Self-built clusters plus NCP-managed nodes, with the B300 / GB300 pool still growing.
Elastic at peak
Interconnect tuned for video and multimodal loads, scaling in milliseconds when a batch lands.

Every gate an episode has to pass

Five steps in production order. What one step hands off is what the next one consumes — nothing is exported and brought back.

  1. 01

    Script and shots

    A web novel is rewritten as a script, then broken into shots with camera, mood and lighting notes.

  2. 02

    Characters and sets aligned

    Turnarounds and cinematic environments render in seconds on the canvas, with local repaints for detail.

  3. 03

    Render the cut

    Stills plus motion instructions come out as HD clips in batches, assembled into an automatic rough cut.

  4. 04

    Voice and mouths

    Dialogue is performed, then dubbed into English, Japanese, Indonesian and more, with mouths that keep time.

  5. 05

    Private stock

    Character libraries, art presets and past footage stay in your space and are reused across concurrent shows.

All five steps share the same assets. Change a character once, and every later shot follows.

Who this line is laid for

Teams whose output is paced by a slate or an ad calendar feel the difference first.

  • 01

    Short-drama platforms

    High-frequency slates that cannot run dry.

  • 02

    Mid to large sellers

    Batches of multimodal ads built to be clicked.

  • 03

    Art outsourcing studios

    Industrial volumes of assets, with characters and sets that stay true.

Compute stays with the audience

Render nodes sit against the markets short dramas are watched in, so producing and delivering a cut never takes the long way. A fourth region is still being built.

North America

The largest overseas audience

Southeast Asia

The fastest-growing market

Japan and Korea

High spend, heavy localisation

Flagship compute pool
Self-built clusters plus NCP-managed nodes, with the B300 / GB300 pool still growing.
Elastic at peak
Network tuned for video and multimodal loads, scaling in milliseconds.
Fourth region in build-out
Customers already on the platform hear about a new node before it opens, so slates can plan for it.

Why this line holds

01

Assets live in your own library

Characters, art presets and past footage stay in private space and carry across projects, so nothing is rebuilt from scratch.

02

One account reaches 100+ models

One interface and one bill, instead of an account and a reconciliation cycle per vendor.

03

Four regions, rendering nearby

Compute is placed around the markets you release into, so rendering and delivery both happen near the audience.

04

We shoot on it ourselves

Our in-house short-drama work runs on the same line, so problems surface here first and get fixed here first.