A webhook-ready home for your Telegram and WhatsApp bots.

No. Every application gets a free *.shardweb.app subdomain with SSL as soon as it deploys, which already satisfies Telegram's and WhatsApp's HTTPS requirement for webhooks. You can also connect a custom domain if you'd rather use your own.

Yes — as a regular application. Puppeteer and the Chromium process that libraries like whatsapp-web.js or Baileys depend on run fine inside it, and everything under /app, including your session files, persists across restarts on a free 10 GB disk. Those libraries are unofficial community projects that run under their own terms, separate from the official WhatsApp Cloud API also listed above.

Shard Cloud's data center is in Ashburn, Virginia, one of the world's biggest internet interconnection hubs. Hosting there keeps the network path between your bot and Telegram's or WhatsApp's servers short, which helps messages go out with lower, steadier latency.

Any of the nine supported runtimes — Node.js, Python, Go, Java, PHP, C#, Ruby, Elixir, or a custom Docker image — covering libraries like Telegraf, python-telegram-bot, Baileys, and whatsapp-web.js.

Health monitoring restarts it automatically after a crash, an out-of-memory failure, or a failed health check, with a circuit breaker after repeated attempts.

None beyond what you're already on — every application, on every plan, gets a free 10 GB disk that persists under /app across restarts, enough for a WhatsApp Web-based bot's session and the Puppeteer or Chromium process behind it.

No. A Telegram bot can use long polling when its library supports it. Use the free HTTPS subdomain when you want webhooks; otherwise, deploy the bot normally and keep its process online.

Yes. Use the official WhatsApp Cloud API with a webhook endpoint, or run libraries such as Baileys or whatsapp-web.js as a regular application with persistent session files. Unofficial libraries remain subject to their own terms and WhatsApp's policies.