I built Shorlabs out of personal frustration. Frontend deployment with Vercel felt effortless, but deploying and managing backend infrastructure was consistently painful. I wanted the same experience for backend services: connect a GitHub repository and have everything else handled automatically.

Shorlabs is a backend PaaS for Python and Node.js applications. It deploys, manages, and scales backend services on top of AWS Lambda, so developers don’t have to provision or maintain servers. The workflow is simple: connect GitHub, import a repository, configure, and deploy.

Most backend PaaS platforms assume that non-trivial applications require long-running servers or containers, treating Function-as-a-Service as suitable mainly for simple workloads. I think that assumption is increasingly outdated.

With modern cloud primitives, it’s now possible to run more sophisticated backend services on FaaS with strong reliability guarantees. The economic upside is significant: scale-to-zero, no idle cost, and far less operational overhead.

My goal is to make serverless a default choice for small teams, not a special case. I’d love feedback, especially from people who’ve hit limits with existing backend PaaS tools.