Core concepts

These docs use a small set of terms. Each section below defines one and links to the guide with more detail.

Organization

An organization is the account boundary for projects, render capacity, credits, billing settings, and collaborators. Check the active organization before buying credits or submitting work.

Project

A project groups related render jobs and supplies the isolated remote file area used by PROJECT uploads. When you reuse a project, later submissions skip files that did not change.

Organization is not a project

The organization owns the balance and capacity. A project organizes production data and jobs inside that organization.

Submission and job

A submission is the preparation work that runs on your computer: trace dependencies, package files or compare them with earlier uploads, upload data, and register a render job. It runs in its own terminal window. The job becomes visible only after those steps succeed.

A render job records the scene settings and frame work sent to Superluminal. It can be queued, running, blocked for funds, paused, errored, or finished. A job contains one or more frame tasks.

Frame task

Each requested frame is a task. Frames can progress independently across render machines. The web job page combines task state with previews, render layers, logs, machine assignment, and timing data.

Upload mode

ZIP

Creates a self-contained archive for the submission. It is the default and the safest choice for a first render, assets outside a clean project root, or files spread across drives. The add-on uploads the complete archive again for each new submission.

PROJECT

Uses a project root and uploads files individually. Later jobs can reuse unchanged remote files. All dependencies must map beneath the project root. The trace can exclude absolute or cross-drive paths.

Render output and previews

The web app shows optimized previews for fast review. Previews are not substitutes for the full-quality files. You download final output through the add-on's Manage & Download section, and the farm keeps render objects for seven days.

Credits and capacity

Credits pay for render compute. Render capacity controls how much work can run in parallel. Billing charges for successful render work at the pricing shown in the app. Keep the balance positive: when it reaches zero, the farm can stop machines that are still rendering.

• Projects: Create, rename, open, and delete project containers.
• Upload settings: Pick a packaging model that matches the scene's file layout.
• Job details: Read frame, preview, machine, timing, chart, and log panels.
• Billing: Add credits and configure organization-scoped billing.