A SaaS platform that runs development pipelines in the cloud with a web interface for remote control, state persistence, and built-in security.

Repository: shipshitdev/shipcode Author: VincentShipsIt Description: Run shipcode in Docker on EC2 with a web UI at shipcode.shipshit.dev so pipeline jobs no longer require a running desktop. Today shipcode only runs while the user's local machine is on. This PRD turns shipcode into a cloud-resident app: a Docker container on a self-hosted EC2 instance, fronted by a web UI at shipcode.shipshit.dev, with SSH for ops only and no SaaS dependencies. Pipeline jobs survive the user closing their laptop. Problem: The Electron desktop app is the control plane and the worker. If the laptop sleeps or is offline, pipeline threads pause. There is currently no way to start a pipeline from one machine and check on it from another. For long-running multi-issue runs, this is a dominant operational pain. Goals: A single Docker image that runs the shipcode pipeline backend headlessly on EC2, a web UI serving the existing renderer, pipeline state persistence on EBS, auth gate to prevent anonymous triggers, and SSH access for logs/debugging. Non-goals: No multi-tenant SaaS, no replacing the Electron app, no auto-scaling. User stories include starting pipeline runs from laptop that continue on EC2, one-command deploy updates, authenticated HTTP traffic, and restricted SSH access. Functional requirements include exposing ShipCodeAPI over HTTP+WebSocket, persisting SQLite DB, spawning subprocesses with env credentials, etc.