An operator-grade platform, built quietly.
TelegramOS exists to give serious operators the tooling they could not get anywhere else: many accounts, real proxies, real tenant isolation, real teams, real audit trails. We are intentionally a quiet company. The work is the message.
Anonymous creators
The people who built TelegramOS choose to remain anonymous. We believe the platform should be judged on its security model, its uptime, and its product, not on a founder's personal brand. You will not find a "team" page with photos here, and that is deliberate.
What the team does
The team behind TelegramOS builds the product and operates it: development, infrastructure, payments, trust and safety, and user support. We do not publish a headcount or an org chart; how the platform actually runs is described in the docs and policies.
Security and reliability are the product
We treat tenant isolation, encryption at rest, role-rank guards, and audit logs as features users pay for, not afterthoughts. If we cannot ship something safely, we do not ship it.
TelegramOS ran as a private tool before it became a SaaS. The public beta first went live on a temporary beta domain and moved to telegramos.net in June 2026, which is why the changelog is older than the domain.
What we believe
Privacy is a default, not a setting
We minimize data we collect, encrypt sessions at rest, and support a Data Processing Addendum out of the box.
Boring infrastructure
PostgreSQL, Redis, FastAPI, Next.js, NATS. Nothing exotic. Boring infrastructure is reliable infrastructure.
Audit everything that matters
Every privileged action is logged with actor, IP, user-agent, and structured metadata. Append-only.
Operators come first
We do not pretend to be a chat app, a CRM, or a marketing suite. We are a Telegram operator platform, and we keep that focus.
Our guarantees
We are a private operator-grade platform. Rather than vague promises, we publish concrete commitments — and we keep the changelog public so you can see how actively the platform is maintained:
Tenant isolation
Every query is bound to a tenant at the data layer. Cross-tenant access is impossible by construction, not by policy.
Session encryption
Telegram session payloads are encrypted at rest with Fernet (AES) under the platform key, with an optional passphrase-derived vault for accounts you own. Message content and files are not encrypted by the application.
Privilege boundaries
Role-rank guards prevent admins from elevating themselves or anyone else above their own authority.
Audit trail
Privileged actions are append-only logged with IP, user-agent, and structured metadata for the change.
Rental terms
A banned rented account is not replaced. It stays yours until its term ends, and you can release it for free or rent another. After a subscription ends, rented accounts stay reserved for you for 5 days before they return to the pool.
No silent breaking changes
Every shipped change appears on the changelog. Security-relevant work is tagged so you can audit it at a glance.
A note on anonymity
Anonymity does not mean unaccountable. We sign every release tag, publish a changelog of every shipped change, and treat security disclosures with the urgency they deserve. The operating organization is incorporated, banked, and audited; what we choose not to publicize are individual identities. If your compliance program requires more, contact us through the contact page. We do sign DPAs and answer security questionnaires under NDA.