Helios.
Multi-tenant Telegram presence intelligence. Built for operators who need every signal Telegram exposes, and absolute invisibility to the people they observe.
The four invariants
Everything the product does
is in service of these.
Stealth is sacred
The userbot cluster never performs any action a target could perceive. Enforced in code, CI, and tests.
Multi-tenant by construction
Every row, every query, every search hit is scoped to one client. Cross-tenant leakage is a P0 incident.
One userbot, many subscribers
Capture once, fan out N times via Redis Streams. Scaling is linear in distinct targets, not in clients.
Owner-tunable at runtime
Every value that could differ is a parameter — edited from the admin panel without a restart.
Pricing
Pick the tier that matches your scale.
Every number on every plan is a runtime parameter — your operator can lift any limit on your contract without a deploy.
Free
$0/mo
0★ via Telegram Stars
3 targets
7-day history
- Basic presence events
- Bot notifications
- 1 client
Pro
$1.99/mo
≈ 199★ via Telegram Stars
25 targets
90-day history
- Activity events (typing, recording)
- 100 req/day API
- Webhook + email routes
Premium
$5.99/mo
≈ 599★ via Telegram Stars
100 targets
1-year history
- Full event set (calls, NFT, full chat)
- WebSocket live stream
- Pattern + sleep schedule
- Custom emoji UI
- 1 000 req/day API
Enterprise
$19.99+/mo
≈ 1 999★ via Telegram Stars
Unlimited
Unlimited
- Team mode (10 seats)
- Dedicated userbot pool
- Custom integrations
- SLA + priority support
Start somewhere
Pick your first page.
New here?
Read the architecture — three layers, the data flow, the foundational invariants. 15 minutes.
About to deploy?
Walk the onboarding guide. Compose for small, k8s for scale, migrations, KMS readiness.
Something is on fire?
The runbook lists the common incidents and the first three things to check for each.
Curious about stealth?
The stealth thesis explains why the userbot fleet is read-only by construction.