OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

Swarm Beekeeper

Swarm Beekeeper is a Go command-line orchestrator for Ethereum Swarm Bee nodes. It manages Bee clusters, calls their APIs, and runs configured scenarios and integration checks.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Swarm Beekeeper — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it for repeatable Bee cluster operations and API-based checks, including local development or integration testing. Static Bee endpoints are supported for checks that do not use Kubernetes.

Who it is for

  • Developers testing changes to Bee or building Bee integration workflows
  • Operators coordinating Bee nodes in Kubernetes or checking nodes through static endpoints

Documented uses

  • Create and delete Bee clusters in Kubernetes
  • Run network checks such as pingpong and pushsync against Bee nodes
  • Exercise Bee APIs through configurable scenarios
  • Automate funding Bee nodes with ETH and BZZ
Before you choose

Requirements & limits

  • The tool is a Go command-line application, built from source with make binary.
  • The README lists Kubernetes v1.31+ and a Geth Swap node as requirements.
  • Static endpoint checks can run without Kubernetes, while Kubernetes-based cluster management uses Kubernetes configuration.
  • Configuration can be read locally or from a Git repository.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Build Beekeeper from source

Prepare the Beekeeper command-line binary from its repository.

Before you start

  • A Go development environment
  • The Beekeeper repository

Steps

  1. Clone the Beekeeper repository.

  2. Change into the beekeeper directory.

  3. Run the command below.

    Documented command
    make binary

Expected outcome

A Beekeeper binary is built in the `dist/` directory.

Guide limitations

  • This covers building the tool, not configuring Bee nodes or running cluster operations.
Documentation 1 ↗
Source-based practical guide

Prepare and check a local Bee cluster

Follow the documented local-development sequence to create a Bee cluster and run its CI ping-pong check.

Before you start

  • Docker, kubectl, make and Go
  • The Beekeeper and Bee repositories
  • A local setup using K3s and k3d
  • A Kubernetes cluster (v1.31+) and Geth Swap node

Steps

  1. Clone Beekeeper and build it with the command below.

    Documented command
    make binary

  2. Clone Bee and prepare the local K3s cluster and Geth node with the command below.

    Documented command
    make beelocal ACTION=prepare SETUP_CONTRACT_IMAGE_TAG=0.9.2 OPTS='skip-vet'

  3. Return to the Beekeeper directory and run ./dist/beekeeper create bee-cluster --cluster-name=local-dns.

  4. Run ./dist/beekeeper check --cluster-name=local-dns --checks=ci-pingpong.

Expected outcome

The documented workflow creates a local Bee cluster and invokes the `ci-pingpong` check.

Guide limitations

  • The README says the SETUP_CONTRACT_IMAGE_TAG=0.9.2 value must match exactly.
  • The sequence requires the separate Bee repository and local Kubernetes-related setup.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
ethersphere/beekeeper · Official homepage title · retained in its source language
How we review sourcesSuggest a correction