Skip to main content

Product Map

Fibe is a Docker-based development environment platform. Users connect compute hosts, connect source repositories, define reusable environment templates, launch isolated Playgrounds, and work with AI Genies inside or beside those environments.

Mental model​

Player
  owns Marquees                 # places where environments run
  owns Props                    # source repositories
  owns Templates                # reusable environment definitions
  owns Agents                   # AI Genie configurations
  owns Secrets, API Keys, Webhooks, Job ENV entries

Template Version + launch values + Marquee
  becomes a Playspec
    becomes a Playground
      exposes services, logs, terminals, URLs, lifecycle controls

Job-mode Template
  launches a Trick
    runs watched services to completion, records result, then cleans up

Core resources​

ResourceUser-facing meaning
PlayerA Fibe account. Owns resources, sessions, profile, plan access, and personal integrations.
MarqueeA Docker host where Playgrounds and Genie chats run. Can be user-managed or platform-managed for tutorials.
PropA connected Git repository. Props provide branches, source code, Compose files, build inputs, webhooks, and code-change history.
TemplateA reusable environment definition. It is versioned, forkable, publishable, launchable, and may be linked to a source file in a Prop.
Template VersionAn immutable snapshot of a Template's YAML and metadata. Launches bind to a specific version for reproducibility.
PlayspecA launch blueprint created from a Template version, variable values, service configuration, mounted files, and a target Marquee.
PlaygroundA running environment created from a Playspec. It has services, URLs, logs, terminal access, lifecycle actions, expiration, and optional Genie attachment.
TrickA job-mode Playground. It runs watched services until they exit, records pass/fail results, and cleans itself up.
Agent / GenieA persistent AI assistant configuration. It can run standalone chat sessions or attach to Playgrounds.
SecretEncrypted user-owned key/value data for credentials that should not live in source code or template YAML.
Job ENV entryEnvironment data injected into job-mode runs globally or for one Prop.
API KeyScoped programmatic access for API, CLI, MCP, and agent workflows.
WebhookOutbound event delivery to external systems when Fibe resources change.
Audit LogRead-only history of important actions and resource changes.

Normal user journey​

  1. Create an account and complete onboarding.
  2. Add a Marquee or use a platform-managed tutorial Marquee.
  3. Connect or create a Prop for source code.
  4. Import, write, fork, or discover a Template.
  5. Choose launch variables, branch, service settings, and target Marquee.
  6. Launch a Playground or Trick.
  7. Use service URLs, logs, debug terminal, rollout, hard restart, stop, retry, or expiration controls.
  8. Attach an Agent, start Bridge chat, upload mounted files, produce artefacts, or record progress.
  9. Publish or fork Templates and automate jobs with schedules or VCS triggers.

Hints​

  • Templates are reusable; Playgrounds are running instances.
  • Template Versions are immutable; changes create a new version.
  • Playspecs "remember" the Template Version and launch values they came from.
  • Marquees are the execution target; a Playground runs on exactly one Marquee.
  • Props are source repositories; dynamic services point at Props or repository URLs.
  • Long-running Playgrounds are for services that should stay up.
  • Tricks are for tasks that should finish.
  • Public service access is configured through Fibe routing, not host port publishing.
  • Internal routes require Fibe-mediated access; external routes are public.
  • Durable data belongs in named volumes or external services, not disposable container filesystems.
  • Sensitive credentials belong in Secret Vault, Job ENV, or launch-time secret variables depending on who needs them and when.