Skip to content

Start typing to search the documentation.

Ecosystem

AI-generated, awaiting review View as Markdown

The Flue ecosystem connects deployable applications to hosting environments and sandbox providers. Start with Develop & Build to develop locally and create build output, then use this section for a specific deployment destination or sandbox integration.

Deployment environments

Flue builds application artifacts for Node.js and Cloudflare. Deployment pages document how those artifacts fit a particular host or execution environment.

DestinationUse it forContinue to…
Node.jsAn ordinary long-running Node server or container.Deploy on Node.js
CloudflareA Worker with generated Durable Object-backed runtime integration.Deploy on Cloudflare
RenderA managed Node web service with optional managed persistence.Deploy on Render
GitHub ActionsOne-shot Node workflow execution in CI.Use GitHub Actions
GitLab CI/CDOne-shot Node workflow execution in CI.Use GitLab CI/CD

For local development and build output, see Develop & Build.

Sandbox connectors

A sandbox connector adapts an application-owned compute or workspace environment into the Flue sandbox contract. A connector controls files and commands available to the agent; it is separate from session conversation storage and workflow run history.

The connector catalog includes remote Linux environments, platform-owned workspaces and containers, and local VM integrations. Choose a provider from the Sandboxes navigation group.

Core guides

  • Sandboxes explains how to choose a filesystem and execution boundary.
  • Agents explains continuing session persistence versus workspace durability.
  • Routing explains which deployed application surfaces are public.