Setup

Set up Naaradmuni
for your group.

Bring the essentials.

01.Your bot and supergroup
Your owner account and bot need administrator permissions.
02.PostgreSQL
Stores messages, group settings, strikes and evaluation work.
03.HTTPS hosting and scheduling
Runs the application and keeps saved work moving.
04.A model-provider key
Needed for classification and model evaluations; can be added after installation.

Requires your numeric Telegram IDs and Node 22.x. Your host’s HTTPS address is enough.

Application setup guide

Choose a hosting path.

Checked 21–22 Oct 2026
01.

Cloudflare Workers

Hosted HTTPS, authentication, data and export checks passed against publicly trusted PostgreSQL TLS. Two native minute ticks were recorded.

Choose a plan suited to the workload and a reachable PostgreSQL endpoint. Private-CA overrides were unavailable in Workers.

02.

Linux VM

A disposable DigitalOcean Ubuntu VM passed public HTTPS, authentication, minute work, repeat installation and database/application restart checks.

A scripted manual installation. This does not establish one-click provisioning or deployment on every VM host.

03.

Render

A separate Free service passed hosted HTTP and PostgreSQL checks, an actual minute tick and restart persistence. Synthetic webhook ingress was checked.

Free services spin down after 15 idle minutes, interrupting continuous processing. This was not actual Telegram-client delivery.

04.

Vercel

A real Node function build passed hosted authentication, PostgreSQL and export checks. An explicitly invoked protected cron passed.

Native minute cron was rejected on Hobby. Pro/Enterprise minute scheduling was not verified. Function payload and duration limits also apply.

Dated hosting evidence · Application hosting guide

Other included configurations

DigitalOcean App Platform remains unverified as a deployment. Railway was excluded from the recorded run. Fly.io testing stopped at an account card requirement. Included configuration is not a verified deployment.

Install, then observe.

  1. Prepare your bot, owner and group.

    Verify admin permissions and discover your IDs in the setup guide.

  2. Configure PostgreSQL and your host.

    Follow your host’s steps in the hosting guide.

  3. Deploy and verify.

    Check HTTPS, authentication and scheduling.

  4. Connect Telegram in Observe.

    Review scored messages first; enable Enforce later.

Questions.

Can I invite @unspammedbot today?

Unspammed Bot is the planned hosted edition, with a US$5/month placeholder price. Hosted signup and subscriptions are not open yet. You can self-host Naaradmuni using your own bot, database, host and model-provider account.

Will it start deleting messages immediately?

New groups start in Observe. Messages can be scored and reviewed, but deletion, strikes and bans remain off until the owner chooses Enforce. Existing Observe decisions are not replayed as enforcement.

What does enforcement do?

The first strike deletes the spam message and records a strike. The second also queues eligible tracked-message cleanup. The third permanently bans the person and queues eligible tracked-message cleanup. Telegram deletion limits still apply; a ban does not mean every historical message was removed.

What can it review?

Text, captions, polls and hidden links are classified. Configured image processing supports photos and supported image documents. Video and audio are not analysed; unsupported or unavailable media goes to review without a strike.

Do I need a custom domain or a Telegram account connection?

No. Your host’s HTTPS domain is sufficient. Connecting a Telegram user account is optional and separate from the bot-based setup.

Where does my data go?

Your installation stores application data in PostgreSQL. Classification and evaluation use your configured model provider, and moderation communicates with Telegram. Review those providers’ terms and settings for your deployment.

Is there an open-source license?

The source repository is public. No project license was found during this site’s review on 22 October 2026, so check the repository’s current licensing before relying on reuse rights.