Documentation

Explore CrowdCAD through Lite Mode guidance, self-hosting responsibilities, privacy and data considerations, and frequently asked questions.

Browse guides

Getting Started

Use a quick decision guide to pick Lite Mode, self-hosting, privacy review, and FAQ pathways.

Open Getting Started

Lite Mode

Understand browser-local evaluation workflows, practical fit, and limits.

Open Lite Mode guidance

Self-hosting

Review organizational ownership, deployment responsibilities, and operational fit.

Open self-hosting guidance

Privacy and data considerations

Read a careful overview of deployment-model tradeoffs and internal review questions.

Open privacy guidance

FAQ

Get concise answers to common adoption, deployment, and contributor questions.

Open FAQ

Choose a deployment path

Both options cover the core CrowdCAD workflow. Lite Mode lowers the barrier to getting started, while self-hosted deployments add shared operations, customization, and organization-managed administration.

Lite Mode

Lite Mode gives teams access to the core CrowdCAD workflow with a faster start and lower technical overhead.

  • Available on crowdcad.org: Yes
  • Requires your own deployment: No
  • Core dispatch workflow: Included
  • CrowdCAD server-side storage: Not used for Lite sessions
  • Shared events: Not included
  • Multiple dispatchers: Not included
  • Venue maps: Not included
  • Custom venues: Not included
  • Interface customization: Not included
  • Administrative control: Limited
  • Best fit: Teams that want a faster starting point with lower setup overhead, or that want to try out the workflow before managing their own deployment
  • Technical overhead: Lower

Self-Hosted

Self-hosting includes the full CrowdCAD workflow with support for shared operations, advanced configuration, and organization-managed administration.

  • Available on crowdcad.org: No
  • Requires your own deployment: Yes
  • Core dispatch workflow: Included
  • CrowdCAD server-side storage: Organization-managed
  • Shared events: Included
  • Multiple dispatchers: Included
  • Venue maps: Included
  • Custom venues: Included
  • Interface customization: Included
  • Administrative control: Organization-managed
  • Best fit: Teams that need shared operations, deeper customization, and centralized administration
  • Technical overhead: Higher

Important note

Organizations are responsible for evaluating legal, privacy, security, and clinical documentation obligations for their own operating context. CrowdCAD documentation is informational and does not replace local legal, regulatory, or policy review.

This public site is a demo, marketing, and documentation environment and should not be treated as a production deployment for real patient data.

Documentation source note

Release history and selected project documentation are sourced from the public CrowdCAD repository submodule when available.

  • • Submodule root: core
  • • Docs directory: core/docs
  • • Changelog path: core/CHANGELOG.md
  • Lite Mode: Local-only workflow guidance sourced from the project user guide. Source (updated 2026-04-10)
  • Self-Hosting: This guide helps organizations deploy CrowdCAD into their own Firebase/GCP project so they retain full control of data (recommended for HIPAA). Source (updated 2026-04-10)
  • Privacy and Data Considerations: This document is a short, user-focused guide to the primary workflows in CrowdCAD. Refer to the web feature pages and project UI for detailed, contextual help: https://crowdcad.org/features Source (updated 2026-04-10)
  • FAQ: ![CI](https://github.com/evanqua/crowdcad/actions/workflows/ci.yml) Source (updated 2026-04-10)