Transloadit

What is a Workspace?

A Workspace is an isolated organizational unit in Transloadit for managing file-processing operations. It has its own Collaborators, Templates, Assemblies, Plan and billing information, and API credentials. Collaborators can belong to multiple Workspaces and switch between them to manage separate projects or clients.

Request + files
Processing platform
Results + status
A processing platform accepts an authenticated request, executes a workflow, and returns observable results. This diagram shows platform workflows broadly, not specifically Workspaces.

How Workspaces work

Within Transloadit, a Workspace forms the administrative and operational boundary around a project’s media-processing resources. API credentials select that boundary for application calls, while Templates define reusable processing logic and Assemblies record executions within it. Collaborator access, subscription choices, and billing are managed in the same scope, letting organizations separate clients or environments without requiring each person to maintain an unrelated account.

Key facts

  1. A Collaborator can belong to several Workspaces and switch among them, but each Workspace keeps its own Templates, Assembly history, credentials, and billing configuration; membership never merges these across Workspaces.
  2. API credentials are Workspace-specific. Using credentials from another Workspace sends the operation into that separate scope, even if the surrounding application code is identical.
  3. Plans and billing information belong to the Workspace rather than to an individual Template or Assembly, so project separation also establishes a distinct commercial boundary.

When Workspaces matter

Separate Workspaces can isolate projects or clients while allowing Collaborators to belong to and switch among several of them. Credentials and billing settings must be selected for the intended Workspace to avoid cross-project mistakes.

Common use cases for platform workflows

These examples cover platform workflows broadly, not specifically Workspaces.

  • Running repeatable upload, import, processing, AI, storage, and notification pipelines.
  • Tracking long-running media work independently from an application request.
  • Referencing centrally stored credentials by name instead of sending storage secrets with each request.

Working with platform workflows

This guidance covers platform workflows broadly, not just Workspaces.

A client authenticates and submits files or references together with workflow instructions. The platform validates the request, schedules dependent operations, records state transitions, and exposes results through a response, polling endpoint, or notification.

Platform concepts become reliable only when their lifecycle is explicit. Authentication, idempotency, retries, timeouts, observability, quotas, and terminal states should be designed together rather than added after failures occur.

What you gain

  • Reusable workflows separate application intent from processing infrastructure.
  • Stable job identifiers and lifecycle events improve observability and recovery.
  • Managed queues and workers let products scale without embedding every media tool.

What it costs

  • Synchronous responses are simple but keep connections open while long work executes.
  • Aggressive retries improve recovery from transient faults but can duplicate work or overload a dependency.
  • Higher concurrency reduces queue time until resource contention or a downstream limit becomes the bottleneck.

Before production

  1. Define authentication, authorization, idempotency, retries, and terminal error behavior.
  2. Observe queue time, execution time, callbacks, and partial results with stable identifiers.
  3. Exercise malformed, duplicate, interrupted, and unauthorized requests before launch.

Turn media knowledge into a working pipeline

Connect uploads, processing, AI, storage, and delivery through one declarative API — with the encoding stack, scaling, and format churn handled for you.

Try Transloadit for free