Danvas
Danvas
DashboardSupportWelcome

👤 USER DOCS

User Guides

Getting Started

Getting StartedDashboard & OnboardingApp Settings

Tutorials

Tutorial: Setting Up Shift Tasks & ClosersTutorial: Managing Incidents in the InboxTutorial: Tracking Compliance & Sync StatusTutorial: Operational Workflows with the AI AssistantTutorial: Building & Deploying Custom Checklists

Daily Operations (Staff)

Shift Workspace & TasksService Day SetupDaily Line-UpStaff Service Day ReportsForms

Communication & Chat

Messages & AnnouncementsUnified Operations InboxAI Assistant

Manager & Admin Guides

Daily Line-Up SetupStaff SchedulingManaging LocationsNPS and Guest FeedbackCouponsContacts and Guest HistoryManager CloseoutsDaily Line-Up & ComplianceAnalyticsIncident ReportingWhistleblower Concerns & FeedbackAdmin Tools

⚙️ DEVELOPER DOCS

Getting Started

Getting StartedDevelopmentDeployment Guide

Architecture

Architecture OverviewExplanation: AI Integration & Tenant SecurityExplanation: Dynamic Forms Engine DesignExplanation: Compliance Ledger DesignExplanation: Live Sync & Data FreshnessData FlowArchitecture Decision Records

Core Domain

Core DomainDatabase ReferenceLocations DomainAuth & RBACScheduling DomainReports DomainIncidents DomainUnified Operations InboxLive Sync Data FreshnessToast Sync PipelineNotifications DomainCoupons and Guest NPSAudit Log & Compliance ArchitectureDesign Audit FindingsAI Chat IntegrationAnalytics & Tips Integration

Frontend

Frontend ArchitectureFormsLoading SkeletonsComponentsPWA & Offline ShellScreenshots

API Reference

API Reference

Endpoints

POS Sales APIOptimization Data APISchedule Shifts APIEmployee Export APIReports APIIncidents APIAI Chat APIPush Notifications APIWebhooks APICron API

Contributing

ContributingCode Examples

Security

Security & Compliance

Release Notes

What's New

Deployment Guide

How Danvas is deployed to production

Danvas uses six independent Vercel projects plus protected Dagster and database workflows. The repository registry in scripts/app-targets.ts is the source of truth for expected application targets.

Applications

AppVercel projectDirectoryBuild filter
Main appcanvas-forge-appapps/appapp
APIcanvas-forge-apiapps/apiapi
Docscanvas-forge-docsapps/docsdocs
Guestcanvas-forge-guestapps/guestguest
Slack botcanvas-forge-slack-botapps/slack-botslack-bot
Analytics MCPcanvas-forge-analytics-mcpapps/analytics-mcpanalytics-mcp

Vercel's native Git integration deploys previews and production commits. Each project runs bash ../../scripts/should-build.sh as its Ignored Build Step so unaffected projects skip their build.

Dagster and database production changes

Production database mutation and Dagster cutover are distinct, approval-gated workflows:

  1. Dispatch dagster-deploy.yml for an exact current-main SHA and approved rehearsal reference. Its managed-CI job builds and attests the candidate images, then the protected deployment waits for approval.
  2. Copy the user image digest from the build summary and dispatch production-migrate.yml with the same SHA and rehearsal reference.
  3. Approve and complete the migration.
  4. Only after migration evidence succeeds, approve the waiting Dagster cutover.

The protected cutover verifies image attestations, migration evidence, activation identity, rollback admission, Podman acceptance, and Dagster GraphQL health.

Do not run production migration or Dagster deployment scripts directly. Do not approve Dagster cutover before the matching migration workflow succeeds.

Preview deployment

Package commands remain preview-only:

bun run vercel:deploy
bun run vercel:deploy --all

cd apps/app
bun run deploy

Never link the monorepo root or run a bare vercel deploy --prod from apps/<app>.

Local build contract

bun install --frozen-lockfile
bun run build:ci
bun run check
bun run test

Build-time public values (NEXT_PUBLIC_APP_URL, NEXT_PUBLIC_WEB_URL, and other NEXT_PUBLIC_* keys) are classified in the environment-variables.md. Never copy CI placeholder values or production secrets into a local file.

See DEPLOYMENT_GUIDE.md and docs/agents/workflows/vercel-deploy.md for operator details.

Development

Local development guide for Danvas

Architecture Overview

High-level architecture of the Danvas platform

On this page

ApplicationsDagster and database production changesPreview deploymentLocal build contract