Samosa

Inspiration

We watched classmates spend hours wrestling with deployment configs instead of building. Getting a project live on Render meant bouncing between GitHub, the Render dashboard and a wall of documentation. Time that should go toward actual development. We wanted to fix that.

What it does

Samosa is a VS Code extension that deploys any project to Render with a single click. It auto-detects your stack, scaffolds the necessary config files, pushes your code to GitHub and triggers the deployment automatically. No tabs, no manual setup, no friction.

How we built it

We built Samosa in TypeScript using the VS Code extension API, Octokit for GitHub integration and the Render API for deployments.

Challenges we ran into

Supporting multiple stacks cleanly was the hardest part. Each framework has different build commands, entry points and config requirements. We built a detection layer that handles Static / Vanilla, Node, Python, Go and React. We kept scope tight intentionally as Samosa works best with simple, common stacks rather than trying to cover every edge case.

Accomplishments that we're proud of

Samosa works. A brand new project folder goes from zero to a live URL in under a minute with no manual configuration. We are proud of the stack detection layer, the pre-flight checker that catches common issues before they cause a failed deploy and the fact that the entire flow lives inside the VS Code sidebar without a single popup.

What we learned

Good developer tooling is about removing decisions, not adding features. We also learned that scoping early saves time. Trying to support every possible stack would have sunk the project, thus we focused on the most common ones and built them well.

What's next for Samosa

Broader stack support is the most requested addition. We also want to add deploy history, one-click rollback and support for environment-specific configs. Longer term, we would like to support other hosting platforms beyond Render. Then developers can choose where their project lives without changing their workflow.

Another major goal is to support deployments to multiple cloud providers beyond Render. In the future, we would like Samosa to be able to deploy applications to platforms such as AWS, Azure, and Google Cloud. This could be implemented by adding provider-specific deployment modules that translate Samosa’s detected project configuration into the appropriate infrastructure and build settings for each platform.

For example, Samosa could generate deployment configurations for services such as AWS Elastic Beanstalk, Azure App Service, or Google Cloud Run, and use their respective APIs to automate repository setup, builds, and deployments.

Other potential improvements include: