Skip to main content

​
Studio Workspace Overview

Redbit AI is a creative production workspace for turning prompts, source media, and reusable assets into image, video, speech, audio, and project outputs. The core workspace is built around independent task cards, an Asset Dock, a Creative Workshop, a guarded Agent layer, and explicit model/provider configuration. Product map of Redbit AI showing inputs, workspace modules, execution layer, and reusable outputs.

​
Who Should Read This

​
Before You Read

If the product terms are unfamiliar, skim Concepts and Glossary first. Redbit coordinates workflows around configured providers; it does not guarantee provider quota, latency, uptime, policy, or output quality. Reading map showing the recommended product documentation path from overview through evaluation, quickstart, first project, decision matrix, workflows, modules, provider configuration, security, Agent, Seedance, troubleshooting, and FAQ. Read these pages in order when onboarding a user, customer, or teammate:
  1. Studio Workspace Overview
  2. Evaluation Guide
  3. Quickstart
  4. First Project Walkthrough
  5. Decision Matrix
  6. Core Workflows
  7. Feature Modules
  8. Models and Provider Configuration
  9. Security and Credentials
  10. Agent Workflows
  11. Seedance Video Workflows
  12. Troubleshooting Playbook

​
Product Positioning

Redbit is not only a chat interface and not only a model API wrapper. It is a workflow layer that keeps creative work visible and reusable:
  • prompts and generated media live in cards instead of disappearing into one transcript;
  • assets can move between cards, Asset Dock, SmartPicker, and Workshop projects;
  • model routing is configured through Settings and the model registry instead of hard-coded per button;
  • the Agent can inspect workspace state and call bounded tools for cards, assets, Workshop projects, settings, search, and local integrations.

​
Main Areas

1

Canvas

The /dashboard workspace shows cards for image, video, speech, describe, and audio tasks. A card keeps its own prompt, model, variant, ratio, references, generation status, and results.
2

Asset Dock

Asset Dock stores reusable image, video, audio, and text assets. Items can be pinned, searched, compared, and selected through SmartPicker as references for later work.
3

Creative Workshop

/workshop manages project-level creative production: script, storyboard scenes, image generation, video generation, voiceover, music, rhythm video, consistency references, and export packages.
4

Settings and model registry

Settings control model defaults, provider credentials, relay behavior, custom model endpoints, Agent runtime mode, and capability testing. The catalog defines supported model families, variants, ratios, and input requirements.
5

Agent panel

The Agent reads a structured workspace snapshot and calls registered tools. Destructive operations and external effects are bounded by tool metadata, result normalization, and explicit target checks.

​
Module Summary

​
Product Boundaries

Redbit uses local browser storage heavily, but some workflows necessarily call external model providers, relay services, local-core endpoints, or user-approved integrations. Treat provider configuration as BYOK: Redbit coordinates requests, but model cost, model availability, provider policy, and output quality depend on the configured provider. Capabilities that are present in architecture notes but feature-flagged, optional, or dependent on local services are described as such in these docs. Claims that cannot be verified in the repository should be treated as planned rather than current product behavior.

​
Next Step

Continue to Evaluation Guide if you are deciding whether Redbit fits a team workflow, or Quickstart if you are ready to configure a minimal provider route and run the first card safely. Use Security and Credentials before sending confidential media.