1. First & Last Name: (optional) Mitrasish Mukherjee
2. Email Address: email@example.com
3. Akash Wallet Address: akash1g8ftppuqwcgzsr5hzj8awl0n9wrugex856x03c
4. Akashian URI:
5. Time Zone: UTC+05:30
6. Language: en
7. Discord Username: rekpero#3898
8. Discourse Username: rekpero
9. Github: rekpero (Mitrasish Mukherjee) · GitHub
10. Twitter: https://twitter.com/rekpero
14. Are you a developer or software engineer?
I’m Co-Founder & CTO of ArGoApp Protocol
15. Are you currently involved in Akash’s Discord developer community channel? (discord.akash.network)
16. Have you deployed on Akash’s Mainnet or Testnet? (docs.akash.network)
17. Do you have other team members?
18. Are you looking for additional team members?
19. Are you interested in working on Akash full-time? Akash is hiring engineers and contractors. Learn more here: Careers | Akash Network
20. What Cloud hosting services do you currently use? (Amazon/Google/Microsoft)
21. How much do you pay per month for Cloud services / hosting?
22. How did you hear about this program?
23. What is your project?
ArGoApp Protocol is a deployment aggregator platform working toward mass adoption of dWeb Infrastructure.
24. What is the problem you will solve?
ArGoApp Protocol is a deployment aggregator platform working toward mass adoption of dWeb Infrastructure. We have already integrated Arweave & Skynet to provide static site deployment for the users. We offer better tooling than what is already present in their ecosystem to deploy websites on these protocols.
The same abstraction layer we want to build around Akash for devs interested in executing their ideas faster instead of learning the tech stack.
25. What are your goals?
We will be building a Heroku-like abstraction layer where users of ArGoApp will be able to deploy their full-stack app in a few steps. We will be exclusively working on Akash Network to build this feature into our platform.
- A user would be able to log in with Identity Providers to our platform.
- They can choose which protocol they want to deploy their web services.
- Pass the container registry name or connect our GitHub app with their org and choose a repo.
- If the user has chosen to go with GitHub repo deployment, our deployer task will clone the repo and build a docker image out of it and push it to our (ArGoApp’s) public registries.
- Users can then select how much compute power they need for that service.
- We will abstract out the actual compute details rather users can choose how many Argon they require.
- Users will provide port details and add port policies to their web services.
- Users will select the region.
- Users can pass all the environment variables required for the service.
- That’s all, users can click on the deploy button, and the platform will handle everything from the backend side.
- Later we will add advanced parameters for deployment that can get customized based on user requirements. (Not in the initial Alpha release)
We will be managing user deployment using our wallet, which always will be prefilled with AKTs, and users can pay the platform in terms of $ARGO tokens.
ArGoApp users can view their deployed service, logs, edit deployed services, stop service, DNS configurations, and billing details in one place.
Team and ArGoApp community will get incentivized to build tooling likes notification services, automation tools, etc.
Even we can create many templates and create a marketplace where users can use Akash in few clicks. Templates of WordPress, Validator Nodes, Web scrappers, Discourse App, etc.
Templates getting listed in the marketplace can be done by the team in the early phase and later can be done on a proposal basis.
A user can check out any template from our marketplace and directly deploy them on Akash with a single click.
*Argon - A term used in our system/platform to indicate how much computing power requires for deployment. If the user choose more than 1 Argons, it will get multiplied as such
- 1 Argon = 1 CPU, 0.5Gi RAM, 0.5Gi Disk or Storage
*Port Policy - It is defined by the platform to denote which port they want to connect to their service port.
- Service port will be tunneled through port 80 if the user chooses HTTP
- If users choose HTTPS, then their service port will be tunneled through port 443.
26. What impact will this project have on the Akash developer community?
The impact will be huge as developers will get a simpler interface to deploy and manage their web services on Akash. The deployment experience is still a barrier for average developers. This will allow developers to focus more on developing cool products rather than thinking about how to host them on Akash Network.
27. Who will use your project when it’s complete?
Developers & Enterprises
28. Will you monetize your project?
We will be introducing the Pay as you go model or deposit and deploy model with our $ARGO tokens. Users will be paying ArGoApp Protocol in our own utility token $ARGO for the equivalent amount for AKT fees.
29. Will you open source your project?
Nope for now, but will open it up once we are sure there are no security issues in the system.
30. Tell us about yourself, your passion, your values
I like working in cloud-native systems and open source projects. I love to chat about interesting ideas revolving around Web3.0 as an ecosystem.
31. What’s your aspiration for blockchain technology?
I onboarded into something that will change how the world works in the next decades. I wanted to be a part of that future and support it in any way possible.
32. If you had $1 million in grant funding what would you do?
- Hire more developers to work delicately on Akash integration.
- Add more support for new use cases on the computing layer and incentivize developers to build an ecosystem around web3 hosting.
- Add more marketing on hosting and compete with big players in web2.0 space like Heroku, digital ocean, etc
- We would also like to stake some funds in AKT, ATOM, DVPN, and other Cosmos Based Tokens, to help secure the networks and to get more funds to continue hosting on Akash and for other operational expenses.
33. Who will benefit most from your project?
Developers and Enterprises as well as Web3 Projects
34. How will you help grow the Akash community?
By bringing more developers to the Akash network from our existing userbase of 2000 devs as well as onboarding more web2 & web3 developers.
35. How will you make Akash approachable to developers?
By building a simplified version of the deployment process on Akash Network. There is a lot of under the hood work for any developer to deploy a simple server on Akash which can be abstracted to make it more approachable.
36. How do you think Akash should improve?
Akash should the library tooling required for deployment and interaction with the deployment and providers. It will open up a lot of scope for new use cases and fine-grain access over deployments.
37. How would you utilize the grant funding?
- Development & Operation Cost: 60%
- Marketing: 20%
- Platform Usage and Reserve: 20%
38. Have you already started this work?
40. How will this task be accomplished?
We have backend dev, front-end dev & designer in our team who are highly talented in their own domains. We are able to ship lots of new features to the platform without much hassle. So in my opinion, there is nothing that we can build at this moment.
41. How would you break this work up into 3 or 4 phases / milestones?
Development can be broken into 4 milestones:
- Deployer task implementation complete
- API development
- UI development
- Marketplace development
42. How many months of work will this project require?
We will be releasing our 1st MVP (or Alpha) by November Start. Further development milestones will be coming up as we integrate Akash Network.
43. What’s the expected amount of funding required for your project?
We are looking for a $10k Grant from Akash Network for starters. The usage will be only toward the development and marketing for Akash Network. We will be exclusively working on Akash Network to build the Heroku-like feature into our platform. The breakup is as follows:
- Development & Operation Cost: 60%
- Marketing: 20%
- Platform Usage and Reserve: 20%
44. Will you open source your project?
Not at this moment but will open it up once we are sure there are no security issues in the system.
45. How do you plan to share your work with the community once complete?
We believe in involving our community during final product announcements and engaging them from the early stage of development.
With this said, we have a total of community members of 26K plus both on the product and social media. We will announce our development and release alpha version to early members to use and get incentivized. We will onboard more existing users to test and deploy the apps on Akash via the ArGoApp platform in the beta version.
Apart from it, we will also open a support channel for members using Akash for the deployment.
46. Will you report your progress to the community every month?
We are flexible with anything, we can share our development reports on the forum thread as well as weekly calls.
47. Do you have any screenshots, videos, or other context you can share?
We were able to build our deployer task script to deploy containers on Akash. We are using the Akash CLI internally to deploy and manage deployments. Testing has been successful. The only thing left is our APIs and UI. Everything is closed source right now.
48. Are you associated with any accelerators, incubators, venture capital firms, or startup funds?
49. Are you associated with any startup communities?
50. Are you associated with the Cloud Native Computing Foundation (CNCF)?
51. Are you associated with any open source projects?
52. Are you associated with any of the Akash Network core team members?
53. Are you a resident of, citizen, or located in a geographic area that is subject to UN, US, EU, Swiss or any other sovereign country sanctions or embargoes?
54. Are you over the age of 18?