Litepaper (start here)

RAIRprotocol is the open deployment layer for web3

Imagine you are trying to develop a dApp aka a "distributed" application. You want to build an engaging application that is connected to an underlying blockchain database in someway.

How much is it going to cost, how long is it going to take? Digging deeper, what does vendor lock-in look like? Are you taking shortcuts now to be beholden to certain providers later.

These problems are why Web3 hasn't scaled yet. All the horsepower exists on the infrastructure layer, while none of the tools are easily accessible, deployable, and most importantly open.

What if a talented team of community devs larger than you could ever amass yourself has already spent years and millions of dollars making a dApp deployment layer you can spin up for free in minutes with Docker. Not just use like other "open source" platforms, but truly OWN.

This is RAIRprotocol.

Deployment Layer

RAIRprotocol allows developers to build their own sovereign dApp infrastructure. RAIRprotocol acts as a dApp aggregator/integrator, and as such does not require its own internal API to function.

There is a key distinction between open source and open infrastructure. RAIRprotocol is fully open infrastructure, while most open source projects monetize behind a closed source API.

A token model is the ONLY WAY to accrue value to an open infrastructure project. As there is no mandatory API key required to use RAIRprotocol.

Comparison between deployment models

Deployment modelsOpen InfrastructureClosed SaaSClosed TokenOpen Source






API Key Required






Native RPC + Alchemy

Unknown Closed API

Unknown Closed API

Closed API through RPC Edge product


Mongo, REDIS

Unknown Closed API

Unknown Closed API

Postgres, REDIS

Smart Contracts

Self Deployment

Through API

Through API

Self Deployment


Affiliate revshare, License Token Model


Usage Token Model

SaaS, Managed Service



Connect to API

Connect to API

Docker + API Secret Required

RAIRprotocol vs Self Managed Examples

  1. Closed Source APIs that can only be called via blackbox. Builders creating on top of these closed systems are reliant on a centralized API. If such a system ever stopped operating, all of the effort would be lost. E.g. like building Farmville on top of Facebook.

  1. Open source closed Infrastructure. While developers can see deeper into how the system works, they are still beholden to a closed API key that governs access to the system. This is still a centralized failure point where if the master API server we're ever to fail, the system would fail.

  1. Compare with RAIRprotocol open infrastructure: an agnostic aggregator of all dApp infrastructure with 10x more connectivity and no vendor lock in bias. E.g. deploy to If the team behind RAIRprotocol we're ever to cease existing, like HTTP, SSL and other open standards, new developers would be able to come in and keep the systems operational.

Moreover if xyz RPC, xyz L1/L2, xyz IPFS provider, or even xyz cloud provider were to fail, each sub system is interchangeable thus making RAIRprotocol a resilient decentralized API deployment layer.

Learn more about the history of open source, our philosophy, and our tokenomics below.

Last updated