Skip to main content
Project 4 min read

ClawAPP Suite: Private Bot Server

Deploy private bot infrastructure with ClawAPP Suite—self-hosted OpenClaw server, plugin, and mobile app. Full control, no vendor lock-in.

Originally published:

GitHub by vimalinx

Self-Hosted Communication Platform for OpenClaw Bots

ClawAPP Suite is a private server solution that enables OpenClaw bots and mobile applications to communicate through self-hosted infrastructure instead of relying on centralized platforms. By deploying your own server, you gain complete control over your bot communications, data storage, and authentication—critical for teams that require privacy, compliance, or independence from third-party services.

Core Architecture

ClawAPP Suite consists of three integrated components working together to create a complete self-hosted ecosystem:

  • Server — A Node.js-based chat server handling user management, token-based authentication, message routing, and account administration. Deploy locally or on a VPS.
  • OpenClaw Plugin (Gateway Extension) — A bridge that connects your OpenClaw bot instance to the Vimalinx server via polling or webhook inbound modes, enabling message delivery without external dependencies.
  • Android App (Vimagram) — A native mobile client for account registration, token generation, and chat management. Users can register, authenticate, and manage credentials directly on their device.

Key Features

  • Private Server Deployment — Run a complete messaging infrastructure on your own hardware with zero vendor lock-in
  • Token-Based Authentication — Secure, cryptographic authentication without passwords transmitted to the server
  • Flexible Inbound Modes — Choose between polling (reliable, low-latency) or webhooks (push-based, lower overhead) for message delivery
  • Automated Installation — Interactive bash script handles dependency checks, plugin copying, server configuration, and gateway validation in one command
  • Multi-Language Mobile App — Native Android client with system language detection and support for Chinese and English interfaces
  • User Management & Whitelisting — Control who can send messages with open or whitelist-based direct message policies
  • Invitation Code Support — Restrict registration using invite-only mode for secure onboarding
  • Gateway Integration — Seamlessly integrates with OpenClaw's existing Gateway infrastructure—no separate broker needed

Getting Started

For Plugin Users (Most Common):

  1. Install OpenClaw CLI: npm install -g openclaw
  2. Configure with: openclaw onboard
  3. Clone the repository and run: ./install.sh
  4. Use the Vimagram app to register and generate a host token
  5. Paste your token when prompted during installation
  6. Verify with: openclaw channels status --probe

The installation script automates dependency checking, plugin placement, server configuration, and gateway verification. Advanced users can set environment variables to skip steps or provide parameters non-interactively.

For Server Deployment: See server/README.md for Docker, systemd, or PM2 production deployment guidance.

Who This Is For

  • Bot Developers — Teams building OpenClaw bots who need private communication infrastructure without cloud dependencies
  • Enterprise Teams — Organizations requiring data residency, compliance, or independence from third-party messaging services
  • Privacy-Conscious Operators — Users who want full control over bot data and communications without metadata leakage to centralized platforms
  • Self-Hosting Enthusiasts — Developers comfortable with VPS deployment, Node.js, and CLI-based configuration
  • OpenClaw Ecosystem Contributors — Plugin and extension developers extending the OpenClaw Gateway with custom communication backends

Configuration & Customization

The installation script generates configuration in ~/.openclaw/openclaw.json with these key parameters:

  • baseUrl — Your Vimalinx server address (e.g., http://your-server:8788)
  • token — Authentication token from the mobile app
  • inboundMode — "poll" for periodic message fetching or "webhook" for server-initiated push
  • dmPolicy — "open" to allow any user DMs or "whitelist" to restrict senders
  • webhookPath — Custom endpoint for webhook mode (default: /vimalinx-webhook)

Environment variables allow headless configuration: VIMALINX_SERVER_URL, VIMALINX_TOKEN, VIMALINX_INBOUND_MODE, and VIMALINX_FORCE_OVERWRITE for automation.

Technical Highlights

Written primarily in Kotlin and TypeScript, ClawAPP Suite leverages the OpenClaw Gateway protocol for seamless integration. The project uses polling as the default inbound mode for reliability—the server periodically pulls messages from your Vimalinx instance. Webhook mode is available for teams that prefer server-initiated delivery. All user data defaults to local storage; sensitive tokens appear only once in the mobile app for security.

The plugin architecture allows future extensions without modifying core OpenClaw. The server component is stateless and horizontally scalable, making it suitable for small deployments and larger installations with multiple bots.

Resources & Support

Common issues like "openclaw not found in PATH," token expiration, and Gateway connection failures are documented with solutions in the project README.

License & Community

ClawAPP Suite is open source under the MIT License, enabling both personal and commercial use. The project accepts contributions and maintains an active issue tracker. With 26 stars and 6 forks, it represents a growing alternative for teams seeking independence from centralized bot platforms.

Source: GitHub repository vimalinx/clawAPP-suite, last updated February 2026.

Share:

Original Source

https://github.com/vimalinx/clawAPP-suite

View Original

Last updated: