Community Spotlight: One-Click Deployments

The Problem

Before the one-click deploy feature, publishing a piece required cloning a repository, writing a Dockerfile, setting up CI/CD, configuring a reverse proxy, and monitoring the deployment. This process took experienced teams hours.

The Solution

The community proposed a simpler model: every piece is a Deno HTTP service. Deno scripts can be executed directly — no Dockerfile, no build step, no configuration.

The platform wraps each piece in a sandboxed Deno process, manages the HTTP endpoint, handles TLS termination, and provides logs out of the box.

The Result

A piece goes from code to production in under three seconds. The developer writes the handler, clicks publish, and the AI deploys it.

Community Impact

Since launch, the one-click deploy feature has:

• Increased piece submissions by 340%
• Reduced average deployment time from 47 minutes to 2.3 seconds
• Enabled non-ops developers to publish production services

How It Works Under the Hood

The platform spawns a Deno process per piece with strict permissions:

--allow-net=api.stripe.com,api.github.com
--allow-env=STRIPE_KEY,GITHUB_TOKEN
--deny-read=/
--deny-write=/

Network access is restricted to only the APIs the piece declares. Environment variables are scoped. The filesystem is locked down. Each piece runs in its own process namespace.

What's Next

The community is working on hot-reloading for pieces — push code updates without any downtime. The sandbox model makes this surprisingly straightforward.