Ready HTTPS address for Callback API
VK only sends events to an HTTPS address - the platform issues one right after deploy, certificate included.
Wrote a bot for a VK community and have nowhere to run it? Connect the repo - Dada Cloud builds and runs the bot and issues an HTTPS address for the Callback API. If it crashes, it restarts itself. Free tier, servers in Russia.
VK only sends events to an HTTPS address - the platform issues one right after deploy, certificate included.
A bot on Flask, FastAPI or aiohttp is detected and built automatically - no Dockerfile needed.
The bot is a persistent process, not a sleeping function. If it crashes, it restarts itself.
Subscribers, settings, history - in a managed database next door, DATABASE_URL wired in automatically.
Community user data is stored on servers inside Russia - what the personal-data law requires.
Your first bot can run for free, no card required.
Six steps from code to a community that answers around the clock.
In your VK community settings create an access key with message permissions and enable Long Poll or Callback API - whichever your code uses.
Name the app inside a project and connect a GitHub repo - or upload a zip if you don't use git.
VK_TOKEN and the confirmation string are set in the console and injected at start, so secrets stay out of the repo.
For Callback API the bot must accept POST on the PORT variable and host 0.0.0.0. For Long Poll no public address is needed - switch the app to background-worker mode.
Copy the issued name.dada-tuda.ru address into the Callback API address field and hit confirm - the bot must return the confirmation string.
Message the community and events start flowing. Logs and restarts are visible in the panel.
Real platform tiers, and an honest comparison with renting your own VPS.
| Tier | Price | What you get |
|---|---|---|
| Free | 0 ₽/mo | One bot with a database and a domain, no card required. Enough for a community with normal activity. |
| Startup | 990 ₽/mo | 5 apps and 2 databases - a bot, an admin panel and a broadcast worker in one project. |
| Business | 2,900 ₽/mo | 20 apps, 10 databases, 30-day backups, priority support. |
| Your own VPS | comparable on hardware | A VPS is cheaper per unit of hardware. But the Callback API certificate, systemd, backups and restarts after a crash cost your time. |
Three places a VK bot deploy usually trips.
VK will not deliver events to an http address or a self-signed certificate. The address the platform issues already has a valid certificate - use that one.
A type=confirmation request must be answered with exactly the string from community settings, no quotes and no JSON wrapper. This is the most common reason VK rejects an address.
If the bot doesn't return ok in time, VK retries the event and the user sees a duplicate. Push slow work into a background task and return ok immediately.
Deploy the bot and get an HTTPS address like name.dada-tuda.ru. Set it as the Callback API address in your VK community settings, return the confirmation string from your code - and events start flowing.
Listen on 0.0.0.0 and the PORT env variable the platform injects. Otherwise VK cannot reach the bot.
Yes. A bot on Flask, FastAPI or aiohttp is detected and built automatically, no Dockerfile. For other stacks just add a Dockerfile.
In managed PostgreSQL next to the bot - DATABASE_URL appears in the environment automatically. Data is stored in Russia, which meets 152-FZ.
Yes, the first bot runs on the free tier, no card required.
Callback API: VK pushes events to your HTTPS address, so the bot answers instantly and spends nothing on polling. Long Poll also works - then the bot needs no public address and is best run in background-worker mode.
In the app's environment variables, set in the console and injected at start. Never commit it: the token grants full access to the community.
VK sends a request with type=confirmation and expects the confirmation string from your community settings back as plain text, not JSON. Check that the bot listens on 0.0.0.0 and the PORT variable, and that the address opens over HTTPS in a browser.
Yes. Zip the bot folder (up to 100MB) and upload it in the console - the platform finds requirements.txt, builds and runs the bot. No GitHub repo required.
Create an account and deploy your first app. The Free plan costs $0.