The public cloud world is becoming more complex every day. An example is AWS (Amazon Web Service), which went online in 2006. In 2006, AWS only had a few services available on their cloud platform - you could count them on one hand. Now there are over 200 services [2].
In addition, the cloud market is not only shared by one public cloud provider. Several (more than 15) large companies share the market. Examples are Google Cloud Platform (GCP), Microsoft Azure, Oracle Cloud, and Hetzner Cloud.
Here is where we at DeployStack come in.
We want to simplify the deployment of open-source software in the public cloud.
So what do we do?
We read the docker-compose file from your repository and transform it into Infrastructure as Code templates. This gives you the advantage that it will make deployment much easier for your users. Anyone can deploy your open source project within a few minutes without manual interaction.
You will also get a code snippet that allows you to add the IaC templates to your README.md. This will enable the One-Click Deploy button feature for any cloud provider listed on deploystack.
Deploy faster
A better workflow
Got a cool open-source project with a docker-compose file? We'll turn it into ready-to-deploy templates so anyone can launch your project on AWS, DigitalOcean, or Render.com with just one click. No more manual config needed - just code, share, and let people deploy wherever they want.
Your open source project can be deployed on (almost) any cloud platform.
Deploy your app from GitHub with just one click
All IaC artifacts and our module are open source.
Your challenges at a glance:
- There are too many public cloud providers. Therefore, offering a 1-Click deploy button in your repository is rather impossible. You have to choose a provider.
- You don't have the time to familiarize yourself with all the resources or technologies of all (or most) cloud providers. Cloud is not easy! Cloud is difficult because of its complexity.
- You have to know exactly your customer group in order to grow. Who can use your open source application? Are these individual developers or DevOps teams in large companies? This is an important question because if these are individual developers, Render with `Web Services` is probably sufficient as a runtime. If, on the other hand, these are large DevOps teams, then they choose, for example, AWS with the service Fargate + Application Load Balancer + WAF etc...
- There are too many Infrastructure as Code languages. The problem is that everyone and every company has established a different language. Some use AWS CDK with TypeScript, some use Terraform and some developers use Render Blueprints. That's all fine - but the landscape of IaC languages is not getting smaller.
The problem with IaC and open-source deployment
An open-source project can only be successful if a large community supports it. Building the community is a big challenge. Your open-source project needs to be known, and you need to make many things as simple as possible. One of the things is using the open-source project - the so-called deployment. There are many cloud providers and many IaC languages/frameworks. However, you can only manage the deployment for some providers. Users have their preferences when it comes to choosing the cloud platform. Some use Azure, and some use AWS or Render.
The IaC gap we want to fill
We want to make the distribution of open-source projects accessible to everyone. That means making the deployment process as simple as possible. Your task is to host our deployment specification in your GitHub repository, and we will translate it to all potential and currently supported cloud platforms. It may sound simple, but the translation process is very complex as each cloud provider has their own API and cloud resource specification.