Verification
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.
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.
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.
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.
Local tests, provider builds, deployed HTTP checks, scheduler/restart checks and physical Telegram-client checks are distinct evidence levels. Real owner-account login and full-history cleanup were not exercised.
Persistent Node hosting needs a running process for the minute timer. Render Free spins down after 15 idle minutes. Vercel cron plans allow minute intervals on Pro/Enterprise and daily on Hobby; automatic paid-plan minute scheduling was not verified.
The Vercel configuration requests a 300-second function. Its function limits include a 4.5 MB request/response payload cap. Optional Telegram account TCP connections need separate provider testing.
Production storage is PostgreSQL. Verify TCP reachability, TLS certificate trust, permissions, migrations and restart persistence, and ensure reverse proxies preserve paths, Origin, authorization and cookies.
DigitalOcean App Platform has a validated manifest but no recorded deployment. Railway was excluded from the recorded run. Fly.io testing stopped at an account card requirement. Netlify has no Unspammed adapter or scheduler integration.
Start with the setup guide and hosting instructions using your own bot, owner/group IDs, PostgreSQL database and HTTPS host. Verify authentication, Telegram ingress, durable data and scheduler recovery in Observe before enabling Enforce.
Plan your installation