About Conductor Deck

A Stream Deck button can already launch an app or switch a scene. Conductor Deck makes one press run a whole chain: post to Slack, update a Notion page, change a Spotify playlist, run a shell command on your own machine, and branch on the result — built visually on a canvas rather than written as a plugin.

You compose workflows from triggers, actions, conditions, delays, loops, parallel branches, and sub-workflows. Cloud steps reach 3,000+ services through Pipedream Connect, so authorising an app is an OAuth flow rather than a hunt for API keys. Local steps — shell commands, keyboard shortcuts, HTTP requests, OBS control — run on your own computer through the Stream Deck plugin. Assigning a finished workflow to a physical button is one click.

The product exists because the alternatives each miss something. Elgato's built-in actions do not compose into multi-step workflows. General automation tools such as Zapier and Make do not target Stream Deck hardware. Hand-coding a plugin works, but only for people willing to write and maintain one.

Live streamers and podcasters who need a scene change, a chat post, and a status update to happen together. Editors and photographers wiring repetitive application steps to hardware. Developers who want a deploy, a status check, or a standup message on a physical key. Anyone already holding a Stream Deck who has outgrown one-action-per-button.

It is a poor fit for server-side automation with no human at a keyboard — a workflow here is normally started by a person pressing a key, a schedule, or a webhook aimed at one user's account.

The web application is a Next.js app deployed on Vercel. Account data lives in a managed PostgreSQL database with row-level security on every user-scoped table, so one account's rows are never a valid query target for another account's session. Third-party app authorisation is brokered by Pipedream Connect. The Stream Deck plugin runs on your own machine and is what executes local actions.

Uptime and dependency health are published on the status page rather than described in prose. Release notes go to the changelog. Security posture, sub-processors, and the vulnerability disclosure route are on the security page.