Architecture overview
Pindeck splits what you click (React on Vercel) from what runs in the background (self-hosted Convex, Trigger workers, RustFS media). Backend URLs are env-configured (.env.local), not documented here.
Deep ops detail lives in the GitHub repo: platform topology and Trigger orchestration.
Production map
After an image arrives
Every path ends in the same library image row, but entry differs:Decks need boards. Board → storyboard → Convert to Deck copies image references into slides. Skipping the board step leaves nothing for the deck strip to show.
Backend pipeline (one new image)
What happens while you wait for an upload or ingest to appear in Gallery:AI variation (optional branch)
Watch Work in the top bar for run progress. Children stay linked to the parent for Lineage in the drawer.External ingest (Discord / Pinterest)
See Discord bot and Uploading.Related
- Product workflow — numbered steps in the UI
- Uploading — tabs, fields, storage paths
- AI generation — variation modes and env keys
- Development — local build and deploy