Depulso was a team project for publishing prebuilt static sites with a short local workflow. It was named Best Overall Project in the Supabase Launch Week 6 Hackathon. I built the platform architecture, CLI, API, proxy, browser-to-CLI authentication relay, and infrastructure; a teammate built the web frontend and dashboard.
Historical Deploy Flow
The documented workflow installs the CLI, signs in with GitHub, initializes a project, then deploys the build output:
npm install -g depulso
depulso login
cd <project-directory>
depulso init
depulso deployinit detects a framework where possible, asks for the output directory and project name, and writes a small project configuration. deploy uploads the already-built files. Depulso does not build applications on a server.
Hosting model
The original service stored deployed assets in Supabase Storage. A proxy was configured to serve each project through a *.depulso.site address, with static-file routing for index pages and clean URLs. The intended deployment address was https://{project}.depulso.site, with SSL.
Constraints and status
- Static output only. Build the site locally before deploying.
- Documented limits were 10 MB per deployment and three projects per user.
- The CLI package remains published, but the repository is archived and the public site and API were unreachable during the July 2026 audit. Treat Depulso as a historical prototype rather than a currently available hosting service.
The two-minute submission demo preserves the original working product. Supabase’s announcement independently verifies the award.
