The problem Cloudifyr solves

1. In a centralised PaaS, the platform is controlled and owned by a single entity, such as a corporation. This can raise concerns around data privacy and security, as the entity has complete control over the platform and the data stored on it. The developers are dependent on the provider for the availability and reliability of the platform. A decentralised platform eradicates this dependance on a single body.

2. A Web3 PaaS can provide pre-built tools and services, making it easier and faster to build and deploy dApps, hence reducing the complexity of blockchain infrastructure

Challenges we ran into

1. Poor/ outdated documentation or lack thereof, was a big issue that stalled our progress for quite a while.

2. Implementing new protocols like StackOS and Push protocols was challenging as we had seldom worked with them before. But once we were comfortable with them, we were able to implement them well.

3. There were limitations in the on-chain implementation of Superfluid due to the requirement of prior approvals for contract deployment. The docs for upgradation of Supertokens from MATIC to MATICx were also insufficient.

4. Being a relatively new platform, StackOS had a somewhat limited dev support. Also the stack tokens were paid and we had to struggle a lot to obtain a few from the stackOS team.