Openclaw Deployment & Integration Setup

I need Openclaw running in a production-ready environment and wired into two services: Ollama and Telegram. The deployment can sit on my existing VPS or inside Docker; saving on tokens, and security matter more to me than the exact stack.

Once Openclaw is live, please connect it to Ollama so its API responses flow straight into Openclaw without manual triggers. No extra features are mandatory on the Ollama side right now—reliable connectivity and basic request/response handling are enough for the first milestone.

Telegram integration is more specific. I want a bot that can both send and receive messages and let me drive Openclaw actions directly from chat. In other words, full bot integration plus standard two-way messaging; notifications or other add-ons can wait.

Kimi 2.5 is not part of the initial scope, but keeping the architecture flexible so it can be added later would be a plus.

Deliverables
• Deployed Openclaw instance with persistent storage
• Ollama linked, tested end-to-end
• Telegram bot configured for send/receive messages and bot commands
• Deployment scripts (Docker Compose or similar) and a concise README so I can redeploy or update independently

Acceptance Criteria
A live test where a Telegram message reaches Openclaw, is processed by Ollama, and the response returns to the same chat, all running on my server with logs proving each step.

If any questions arise about server specs, ports, or API tokens, let me know early so we keep setup time short.