Deeploy Unlocked: Accessing the Power of Ratio1

Since the beginning, the vision behind Ratio1 has been clear: create a decentralized computing protocol where Cloud Service Providers (CSPs) operate like franchisees, building sustainable businesses on top of the protocol’s economy. Instead of Ratio1 directly chasing end-users, CSPs act as the bridge - thriving on Ratio1’s capabilities while delivering services to their clients.

To make this vision a reality, we built the Deeploy App (R1-301): a simple yet powerful gateway that gives CSPs seamless access to Ratio1’s distributed computing power.

Who Can Become a CSP?

One of the strengths of Ratio1 is its openness. Almost anyone can become a CSP.

At present, the requirements are:

• Owning a Node Deed / Master Node Deed License linked to an Oracle Node
  
  

• Passing the KYC/KYB verification process

Without a licensed Oracle Node, a user cannot interact with the Deeploy App, since the app communicates with the Deeploy API through these nodes.

This article is written both for those just curious about Ratio1, and for those seriously considering stepping into the role of a CSP.

What is the Deeploy App?

Think of the Deeploy App as Ratio1’s control center for CSPs.

It is a continuously evolving application that already comes with pre-built deployment templates for:

• Generic applications
  
  

• Common services
  
  

• Native apps

And this is just the beginning. As CSPs and their clients demand more, the template library will expand to cover new use cases - ensuring that no workload is left unsupported.

From Node Operator to CSP to Deployed Jobs

Turning a Node into an Oracle

To step into the role of a CSP, a Node Operator must apply to become both an Oracle Operator and a CSP. It’s important to note that once a Node is turned into an Oracle, its license will not directly run jobs, meaning it will not receive Proof of AI rewards from job execution. Instead, its role is to mediate and interact with the Deeploy API.

Deploying a CSP Smart Contract

When a CSP logs in for the first time at deeploy.ratio1.ai, they are prompted to deploy their CSP Smart Contract.

This step is foundational:

• Every CSP owns their own smart contract
  
  

• All CSP activity is traceable on-chain
  
  

• Deployments remain transparent and independent

In other words: your business as a CSP runs on infrastructure you fully control, with accountability baked in. More information on this subject will be provided in the below “behind the scenes” chapter of this article.

Organizing with Projects & Jobs

Once a CSP has a smart contract, they can begin by creating projects. A project can consist of one or many jobs - for example:

• A dApp
  
  

• A CMS application
  
  

• A database cluster

This project-based structure keeps things neat, organized, and scalable.

Deployment Flow: Tunnels & Jobs

Before starting a job within a project, CSPs must first create a tunnel.

Why? Because tunnels establish secure communication between applications and the Ratio1 infrastructure. They’re created and managed directly in the Tunnels section of the Deeploy App.

To enable this, CSPs simply connect their Cloudflare credentials, allowing the CSP to create and manage Cloudflare Tunnels directly from the Deeploy App.

This modular setup ensures that even complex, multi-job deployments remain flexible, secure, and manageable.

Deeploying a Job

The actual job deployment journey looks like this:

1. Create a project and add jobs inside it.
   
   

2. Choose a job type from templates (Generic App, Service, or Native App).

   

   
   

3. Specify machine requirements - with or without GPU, and the number of nodes.

   

   
   

4. Apply filters for node selection. Currently, only the KYB label is supported (ensuring Node Operators are verified companies), but more labels are coming soon (e.g., Dora compliance, geographic location, and industry standards).
   
   

5. Review job specs & pricing - including run time.

   

   
   

6. Fill deployment information - environment variables, ports, image links.

   

   
   

7. Finalize and pay - lock USDC into the escrow smart contract to confirm deployment.

At this point, the job is officially on Ratio1.

To make onboarding even easier, we’ve created a step-by-step end-to-end application deployment tutorial. This guide walks CSPs through the full process inside the Deeploy App - from creating a project and setting up tunnels, to configuring jobs, locking funds, and launching workloads on Ratio1. Whether you’re new to decentralized compute or an experienced operator, the tutorial ensures you can move from zero to live deployment with confidence.

Watch the full tutorial here:
Link

Behind Deeploy: The Technical Pillars

The Deeploy system flow and consensus is based on a merge between off-chain processing done by the oracle network or Ratio1 ecosystem and the on-chain smart-contract based processing. While the oracle network receives, authenticates and launches jobs it has to rely both on a escrowing system that securely holds the funds for the job lifetime (or at least for the lifetime that the job has been paid for) while providing immutable on-chain consensus for the job transitions - such as the moment when a job loses a worker and automatically is being deployed to an available one or the situation when a horizontal scaling is required say from 2 replicas to 4 replicas. All these imply immutability, transaction security with verifiable budgets and sources.

It all starts with the Cloud Service Provider (CSP) entity creation that is a straight-forward step: all you need to do is obtain the “oracle status” for one of your running nodes. This step is done by gaining reputation in the network and being accepted by peers as a reliable Node Operator. Following this step the only requirement is to have the setup of the own CSP Escrow smart contract as each individual CSP is required to have their own escrow account (on-chain smart contract) that will hold all the committed funds and will gradually release the rewards to each of the participating Node Operators. 

1. Escrow Smart Contracts - Proof of AI (R1-302)

Every job runs in the Ratio1 network based on on-chain funds locked in an escrow smart-contract. The funds are distributed after each successful epoch to all the job participants (i.e. the nodes that ran the job during that epoch). Launch of each individual job is done via an on-chain consensus process where each individual R1 oracle node sends (and pays for) a transaction confirming who is running that particular job based on its own opinion.

This ensures:

• Funds remain secure until execution is verified
  
  

• Node Operators are only paid after results are validated
  
  

• Clients can trust an immutable, verifiable record of execution

Proof of AI creates a transparent trail proving that computations were actually run on Ratio1 nodes - eliminating disputes and embedding trust directly into the protocol.

2. Deeploy & ChainDist - Distributed Consensus for Workloads (R1-342)

The R1 ChainDist ensures the monitoring and scheduling of the workloads that have been launched in the network by Deeploy. Why Deeploy is responsible with authentication, verification of payments and launching the initial decentralized replicas the ChainDist is responsible for both creating the initial job launch consensus as well as any further required consensus for worker replacement or worker addition or deletion.

In short ChainDist guarantees that:

• On-chain committed jobs have been verified based on a consensus of oracles - one third of all the available oracle
  
  

• Any change in the job execution, number of replicas, all workers running the replicas and results - all are validated through multi-node consensus
  
  

• Fault-tolerance and redundancy are built in and each epoch close will trigger an arbitrary oracle to allocate (not distribute) the rewards for each participating worker of the past epoch

This allows Ratio1 to scale compute power without sacrificing reliability. Important to note is that each individual oracle will have to hold a minimal sum of ETH in order to pay the gas fees for participating in the consensus and writing their own “opinions” on-chain as well as for running the reward allocation (when it receives its turn to do it).

3. Open Development & Templates

Ratio1 is designed as an open ecosystem. On GitHub, CSPs can find:

• Deployment templates
  
  

• Service adapters
  
  

• Best practices for secure and scalable deployments

That means both developers as well as CSPs are able to deploy both 3rd party applications but also applications and frameworks developed by Ratio1 Community for various purposes - from cybersecurity to computer vision, from sensor network monitoring to decentralized private storage. Community contributions continuously enrich the protocol - expanding what CSPs can offer their clients.

Why Deeploy Matters

For CSPs:

• A one-stop gateway to onboard, deploy, and manage jobs
  
  

• On-chain accountability through CSP smart contracts
  
  

• New revenue opportunities through the Ratio1 economy

For Clients:

• Access to a growing network of providers
  
  

• Transparent, verifiable deployments
  
  

• Proof of computation integrity

For the Ecosystem:

• Expanding marketplace of applications
  
  

• Stronger decentralization by lowering CSP entry barriers
  
  

• A thriving protocol economy powered by real workloads

The Road Ahead

The Deeploy App is just the beginning. With every iteration, it will become more intuitive, efficient, and flexible - making it easier for anyone to tap into Ratio1’s decentralized compute.

Whether you’re a seasoned cloud provider or a curious newcomer, Deeploy is your gateway to unlocking the power of Ratio1.