What is openclaw-nearai-worker?

nearai/openclaw-nearai-worker — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2026-06-21

★ 9RustAudience · developerComplexity · 4/5ActiveSetup · hard

Mindmap

mindmap
  root((openclaw worker))
    What it does
      Deploys OpenClaw via Docker
      Uses NEAR AI Cloud models
      Multi tenant isolation
    Tech stack
      Rust
      Docker
      Nginx
      SSH bastion
    Use cases
      Offer OpenClaw as a service
      Spin up per user instances
      Secure SSH access
    Audience
      Developers
      Teams hosting AI agents
    Notable
      Telegram device approval
      Auto HTTPS with Lets Encrypt
      Key based SSH only

mindmap root((openclaw worker)) What it does Deploys OpenClaw via Docker Uses NEAR AI Cloud models Multi tenant isolation Tech stack Rust Docker Nginx SSH bastion Use cases Offer OpenClaw as a service Spin up per user instances Secure SSH access Audience Developers Teams hosting AI agents Notable Telegram device approval Auto HTTPS with Lets Encrypt Key based SSH only

What do people build with it?

USE CASE 1

Deploy OpenClaw once on a server and offer it to multiple users via isolated Docker containers.

USE CASE 2

Give each user their own subdomain web interface and SSH access to their AI agent instance.

USE CASE 3

Run a single-user development instance of OpenClaw backed by NEAR AI Cloud models.

USE CASE 4

Set up Telegram-based device approval so users can pair new devices without manual whitelisting.

What is it built with?

RustDockerNginxSSH

How does it compare?

	nearai/openclaw-nearai-worker	loslos321-lab/goldworm	tktech/gdeye
Stars	9	9	9
Language	Rust	Rust	Rust
Last pushed	2026-06-21	—	2026-04-04
Maintenance	Active	—	Maintained
Setup difficulty	hard	moderate	easy
Complexity	4/5	4/5	2/5
Audience	developer	researcher	developer

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires Docker, a NEAR AI Cloud API key, and for multi-tenant use, a server with nginx/Let's Encrypt.

Copy-paste prompts

Prompt 1

Show me how to deploy this multi-tenant OpenClaw worker on a server with nginx and Let's Encrypt HTTPS.

Prompt 2

Walk me through configuring the compose-api to spin up an isolated OpenClaw instance for a new user.

Prompt 3

How do I set up SSH bastion access so I can SSH into a specific user's OpenClaw container?

Prompt 4

Explain how to configure this worker to use my NEAR AI Cloud API key for model access.

Prompt 5

Help me set up Telegram device pairing so users can approve new devices for their OpenClaw instance.

Frequently asked questions