Overview

Alluvial offers several ways to deliver content and applications inside a project. The right choice depends on whether you are publishing static information, a browser-only frontend, or an application that needs a server runtime.

This guide helps you choose between:

Quick Comparison

User Pages

Use User Pages when:

  • you want to publish project guidance, documentation, onboarding material, or reference content
  • the content is primarily text, images, links, and diagrams
  • a Markdown-based editor is sufficient
  • you do not need a separate frontend application build or runtime

Static Web Apps

Use Static Web Apps when:

  • the application is a browser-based frontend build
  • no platform-hosted server process is required
  • the application can be delivered entirely as static files
  • the app has already been built outside Alluvial and can be uploaded as a packaged frontend bundle

Containerized Apps

Use Containerized Apps when:

  • the application needs a server runtime
  • backend code must run inside Alluvial
  • startup scripts, background workers, or runtime-managed dependencies are required
  • the application must run as a deployed container rather than as a static file bundle

Key Differences

Editing Model

  • User Pages are authored directly in Alluvial using Markdown.
  • Static Web Apps are built elsewhere and uploaded as packaged frontend assets.
  • Containerized Apps are deployed from container images.

Runtime Model

  • User Pages do not have an application runtime.
  • Static Web Apps are served as deployed static files.
  • Containerized Apps run as applications with a managed runtime environment.

Best Fit

  • User Pages are best for information delivery.
  • Static Web Apps are best for frontend-only interactive experiences.
  • Containerized Apps are best for full applications that need backend execution in the platform.

Common Scenarios

Publish Internal Documentation or Guidance

Choose User Pages.

Examples:

  • onboarding instructions
  • project standards
  • reference material
  • embedded diagrams and process documentation

Publish a Built Frontend Experience

Choose Static Web Apps.

Examples:

  • React or Vue dashboards
  • static documentation sites
  • lightweight browser tools
  • frontend experiences that call external APIs directly from the browser

Run a Runtime-Dependent Application

Choose Containerized Apps.

Examples:

  • Streamlit applications
  • R Shiny applications
  • applications that require server-side packages or startup commands
  • tools that need backend logic running inside Alluvial

Decision Guide

Ask the following questions in order:

  1. Is this primarily content written for users to read? If yes, use User Pages.
  2. Is this a frontend application that can be deployed entirely as static files? If yes, use Static Web Apps.
  3. Does the application require a platform-hosted runtime or backend execution? If yes, use Containerized Apps.