---
title: "Deploy drosera-operator (testnet)"
description: "Drosera operator and delegation client for testnet. Checkout dev.drosera.io"
category: "Other"
url: https://railway.com/deploy/0OtXZl
---

# Deploy drosera-operator (testnet)

Drosera operator and delegation client for testnet. Checkout dev.drosera.io

**[Deploy drosera-operator (testnet) on Railway](https://railway.com/template/0OtXZl)**

- **Creator:** DROSERA's Projects
- **Category:** Other
- **Total deploys:** 7

## Template content

### drosera-delegation-client

- **Image:** ghcr.io/drosera-network/drosera-delegation-client:latest

### drosera-operator

- **Image:** ghcr.io/drosera-network/drosera-operator:latest
- **Start command:** `./drosera-operator node`

## Documentation

## Operators

Operators are crucial players in Drosera, consisting of organizations and solo stakers who run the Drosera Operator Client software to help maintain and protect the DeFi ecosystem. These dedicated individuals are responsible for executing Traps and performing on-chain response actions, ensuring the security and stability of the network.

To execute a Trap, an Operator must first gain permission by opting into the specific Trap. Once opted in, the Operator gains access to the off-chain Trap and the current peers in the network. This allows them to actively participate in monitoring and evaluating every new block based on the conditions set by the Trap.

In the event that the conditions of a Trap are met, the Operator will promptly execute the on-chain response function. This swift action helps to mitigate potential threats and exploits.

## Delegation Client

The Delegation Client is a tool used to automatically opt your Operator node into Traps. The Delegation Client is a separate application from the Operator node and requires the same private key used for the Operator node.

It works by querying Drosera's Delegation server which delegates traps to registered Operators as they are created. It is a convenience service that is only used in the testnet environment because it is expected for Operators to manually opt into Traps in a mainnet environment that is based on real value incentives.

### Deploying the drosera-operator (testnet) template
- Populate the 2 required environment variables in both the drosera-operator and drosera-delegation-client services.  The environment variables with the same name should have the same values.
  - DRO__ETH__RPC_URL
  - DRO__ETH__PRIVATE_KEY
- Deploy the operator


### After deployment steps
#### Enable Networking
In order for liveness data for this operator to be seen on the frontend, we need to add an http proxy.
1. Open the `Settings` tab of your service.
2. Navigate to the `Networking` section of the settings tab.
3. Click the `Generate Domain` button.
4. Select port `31314` port from the dropdown list (if you changed the DRO__SERVER__PORT variable, choose the value you set).
5. Click the `Generate Domain` button again.

#### Redeploy the Operator
Now we need to redeploy the service to pick up the networking changes
1. Select the `Deployments` tab of your service.
2. In the green active deployment box, click the vertical 3 dot menu.
3. Click `Redeploy`

## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/0OtXZl