Telegram-native managed AI agents

Your own private AI agent.
Alive in Telegram.

A fully managed Hermes agent with persistent memory, tools, skills and automation — without servers, API keys or technical setup.

No VPS No API keys No dashboard required
ROOTLABS / PRIVATE AGENT● LIVE
PERSONAL AGENTAtlas@atlas_agent_bot
Runtime healthy
MemorySkillsCronFiles
Agent activity

→ Researching latest Solana ecosystem updates

→ Comparing 12 sources and recent market activity

Summary ready · delivered to Telegram

Isolated runtimeTenant boundary active
Managed by RootlabsHealth · recovery · updates
POWERED BYHERMES AGENT
CONTROLLED THROUGHTELEGRAM
OPERATED BYROOTLABS
THE PRODUCT

Everything powerful about an AI agent.
None of the infrastructure work.

Rootlabs wraps Hermes in a managed control plane built for personal, persistent agents.

Persistent memory

Your agent remembers context, preferences, workflows and long-running work across sessions.

Real agent tools

Research, files, skills, cron and tool execution — not a thin chat wrapper.

Fully managed

Rootlabs handles runtime health, updates, recovery, secrets and infrastructure operations.

Usage you can see

Clear plan limits and usage visibility so autonomous work stays predictable.

FROM ZERO TO AGENT

Three steps. Then it’s yours.

The onboarding flow lives where your agent lives: Telegram.

01

Open Rootlabs Bot

Start from rootlabs.fun and continue in Telegram. No new account password.

02

Create your managed bot

Give your agent a name and Telegram identity through the native managed-bot flow.

03

Start working

Rootlabs provisions Hermes, private state and plan policy. Your agent opens ready to use.

PRIVATE BY ARCHITECTURE

Your agent should feel personal.
Its infrastructure should be isolated.

Rootlabs does not treat a chat session as a tenant boundary. Each customer receives independently managed runtime state, credentials and persistent data.

  • Isolated Hermes runtime boundary
  • Dedicated persistent state
  • Owner-restricted Telegram access
  • Tenant-scoped secrets and files
ROOTLABS CONTROL PLANE SECURED
Tenant ATenant BTenant C
Agent AMemory · Files · Skills
Agent BMemory · Files · Skills
Agent CMemory · Files · Skills
No shared tenant state
WHY ROOTLABS

Hermes without the ops burden.

Keep the agent. Remove the infrastructure checklist.

Self-hostingRootlabs
VPS provisioningManualManaged
Docker & runtime setupManualIncluded
Model provider & keysYou manageRootlabs managed
Telegram bot setupManualManaged flow
Updates & recoveryYou own itRootlabs operates
Persistent agent stateYou configureIncluded
Daily interfaceTerminal + TelegramJust Telegram
SIMPLE PLANS

Choose how hard your agent works.

Start simple. Upgrade when you need heavier automation and broader tools.

CORE

Your private everyday agent.

For research, memory, files and lightweight scheduled work.

  • Private Hermes runtime
  • Persistent memory & files
  • Curated skills
  • Scheduled tasks with limits
  • Managed model access
Create Core agent
YOUR AGENT IS ONE CHAT AWAY

Stop managing infrastructure.
Start using your agent.

Private Hermes. Persistent memory. Telegram-native. Fully managed by Rootlabs.

Create your agent
FAQ

Questions before
you hand over the ops?

The core experience is deliberately simple. The infrastructure behind it is not.

What is Rootlabs?+

Rootlabs gives you a private, managed Hermes AI agent with its own Telegram bot. We operate the infrastructure; you simply use your agent.

Do I need a VPS or API keys?+

No. Rootlabs is designed so you do not need to rent a server, manage Docker, configure model providers, or maintain API credentials.

Is my agent private?+

Each customer is provisioned into an isolated runtime boundary with separate persistent state, memory, files, skills, cron, secrets and usage controls.

Why Telegram?+

Telegram becomes both the onboarding surface and the place you actually use your agent. There is no extra dashboard or password to manage for the core experience.

What powers the agent?+

Rootlabs uses Hermes Agent by Nous Research as the execution runtime, wrapped by the Rootlabs control plane for provisioning, isolation, billing, health and lifecycle management.