CrowdCrunch is your growth hack for achieving scale.

Crowd computing marries the benefits of peer-to-peer (p2p) systems with the established infrastructure and design principles of the cloud. With apps Powered by CrowdCrunch™, users are simultaneously hosts, acting as both client and server. Peers coordinate to perform tasks or forward data to one another or to end users, with the developer orchestrating this symphony of microservices. Incentivize peers to host services with traditional payments or discounted premium app features, and watch your users grow.

Crowd Advantages

Why choose crowd over cloud? Let us count the ways...



Unlike cloud-hosted apps based on a client-server architecture, p2p networks grow in strength and efficiency as the number of users grow. This means you can simply pay to on-board new customers, since your users are simultaneously your hosts.



A decentralized approach means no single point of failure or centralized target for cyber-attacks. In fact, services hosted at the network's edge can be easily severed from the rest of the crowd to the dampen the effects of outages or DDoS attacks.



Instead of relying on a server to dole out data to each requesting client, a p2p network enlists the help of the peers themselves to forward data. This allows faster downloads while unburdening the outsourcing node.



CrowdCrunch enables content and services to be stored closer to the end user than ever before. This helps reduce network latency, which means that real-time applications, like video streaming services, are fluid, even on very low-bandwidth networks.



Give your app superpowers with offline functionality. Since peers communicate directly, your users can continue to share messages, photos, docs and more—even without Internet access—as long as they share a common network, such as a home or office LAN.

shutterstock_492560935 copy.jpg


By unlocking latent potential in peer devices and leveraging their local bandwidth, developers deploying crowd-based apps can spread load across the crowd, unburdening the outsourcing node. Prepare to run planet-scale apps from your laptop. 



CrowdCrunch doesn't own the computers that do your crunching, so we don't have the costs associated with traditional, cloud-based clusters. This allows us to offer a world-class product at a steep discount.



Got trust issues? Us too. As a p2p network, service-to-service communication never passes through CrowdCrunch severs. That means private messages are just that: private. No third-party cloud to trust. Let's restore privacy to the web, one app at a time.


Migrating microservices from cloud to crowd


The microservices design pattern is a software design philosophy that emphasizes separating the functionality of an app into small, autonomous and loosely coupled services, such that each contains everything necessary to execute a single function of the app. The goal is to modularize an app's business logic and allow for rapid refactoring as needed.

The microservices pattern has gained traction among the cloud-native community building global-scale apps, where developers must deal with high-volume requests, complex application logic, support for desktop, mobile and various other devices, and outages due to hardware failures, severe weather or malicious cyber-attacks. To mitigate these challenges, microservices are commonly replicated and distributed across a data center or multiple data centers, enabling high availability and fault tolerance.

CrowdCrunch takes the practice of replicated and distributed microservices to its logical extreme: allowing consumer-grade computers to act as service hosts. The modularity of cloud-native applications and the small size of microservices makes the microservices design pattern ideal for p2p networks comprised of relatively weak machines on low-to-moderate bandwidth networks. This means that applications built in the cloud-native style do not require significant modifications to be deployed as a crowd-based application with CrowdCrunch.

Commercial-grade and built atop mature, open-source software, the CrowdCrunch framework provides a p2p transport layer for porting cloud-native apps to the crowd.


With namespaces and control groups isolating processes from the host environment, containers allow your apps to run anywhere, as expected. CrowdCrunch supports common container solutions, such as Docker, enabling you to easily migrate your apps to the crowd.

Scheduling, monitoring and managing container deployments is simplified with Kubernetes. This commercial-grade framework is integrated into the CrowdCrunch stack for continuously maintaining the health of your crowd-based apps.

IPFS is a p2p, distributed file system protocol for the web, designed as a replacement for HTTP. Network nodes store files as collections of unique data blocks, along with indexing information, for fast and efficient lookups at planet scale. CrowdCrunch utilizes the IPFS network stack to achieve reliable peer-discovery and routing for delivering or retrieving containers that make up your apps.