Original Summary

Over the last few months I have been noticing this gap more and more. With tools like Cursor, Claude, Lovable, Bolt etc, people can now build pretty decent applications very quickly. But once the app is ready, deployment is still a completely different headache. You suddenly have to figure out AWS or GCP, Docker, SSL, environment variables, domains, monitoring, logs, CI/CD and a bunch of other things. I faced the same problem and that is what made me start building The Deployer. The idea is simple. You connect or give it your GitHub repository. It understands the application, figures out what infrastructure it actually needs, gives you different deployment options with estimated costs, and then deploys it into your own cloud account. Right now I am working with AWS, GCP, Azure and DigitalOcean. One thing I specifically did not want was to build another hosting platform where your application gets stuck inside the platform. The infrastructure stays inside your own cloud account and the goal is that you should always know what is actually running. I am also working on things after deployment like monitoring, logs, SSL, health checks and handling failed deployments. There is a free repository analysis available right now where you can paste a public GitHub repo and see what it understands about the application and how it would deploy it. I am mainly looking for people who already have side projects sitting in GitHub and have gone through this problem. One thing I would genuinely like to understand from developers here: What would you need to see before you would trust a tool to deploy something directly into your AWS or GCP account? Would IAM permissions worry you? Generated infrastructure? Secrets? Cost? Something else? https://thedploy.com   submitted by   /u/New_Band_2635 [link]   [comments]

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/19 18:22:23