One click deployment of CI/CD workflows on to decentralised cloud infrastructure. Deploy on cheaper, permissionless and decentralised cloud instead of on AWS/GCP
Our project is a developer tool that allows you to deploy your CI/CD Github Action workflows to decentralized cloud infrastructure like Akash Network, Openmesh etc.
We have developed a github OAuth app and a slickCI website using node.js and react.js. The user gives our github OAuth app access to their repo via our website. They then just have to change 1 line in the actions .yml file to start using our runners rather than default github runners.
We deploy GitHub runners on servers rented on Akash Network. Our runners are 4x cheaper than Github's default runners.
We deployed GitHub runners on servers rented on Akash Network. Our runners are 4x cheaper than Github's default runners. Our backend stack consists of two components:
SlickCI Engine is responsible for receiving webhook events when the users sign up at SlickCI. The webhook event contains all the essential information including the repository name, owner as well as other details to connect each new repository with it's dedicated runner hosted on Akash. The Engine sends all required shell commands to SlickCI Runner to set up the integration with Github via the typescript framework tRPC, then SlickCI Runner will be assigned to the correct repository. Due to the time limitation, SlickCI only supports Github Action at the moment.
For the front end we used the Next.Js library and integrated AA wallets using social media sign in and used Unlimit API to pay for a seamless experience. We also launched our Mantle token on the testnet as we have future utilitarian road map for it.
Our project is a developer tool that allows you to deploy your CI/CD Github Action workflows to decentralized cloud infrastructure like Akash Network, Openmesh etc.
We have developed a github OAuth app and a slickCI website using node.js and react.js. The user gives our github OAuth app access to their repo via our website. They then just have to change 1 line in the actions .yml file to start using our runners rather than default github runners.