Just a zip or tar.gz
Zip the whole project - or an export from Lovable, Bolt, v0 - and drop the archive into the console. Up to 100MB.
Don't want to deal with git and GitHub? Zip your project as zip or tar.gz (up to 100MB) and drop it into the Dada Cloud console. The platform finds your Dockerfile, package.json or requirements.txt, builds the app and runs it - a live HTTPS address appears in 1-2 minutes. Exports from Lovable, Bolt or v0 work too - just zip the export folder.
Four steps from a folder on your computer to a live address
Name your app in the project - it takes a second, the image doesn't matter yet: the platform replaces it once you upload the archive.
Package the project folder (or a Lovable, Bolt or v0 export) as zip or tar.gz - up to 100MB.
On the app page, drag the file into the upload area or pick it manually - the platform detects the framework and port from the manifests inside.
The build usually takes 1-2 minutes, then the app is live at an HTTPS address like name-hash.dada-tuda.ru.
Zip the whole project - or an export from Lovable, Bolt, v0 - and drop the archive into the console. Up to 100MB.
The platform looks for a Dockerfile, package.json (Next.js, Vite, React) or requirements.txt and pyproject.toml (FastAPI, Flask, Django, Streamlit) and builds the app without manual setup.
After you upload the archive a build kicks off - usually 1-2 minutes - and the app gets a working address like name-hash.dada-tuda.ru with a certificate.
If the archive has a Dockerfile, the platform uses it and reads the port from EXPOSE. Without one, requirements.txt or package.json with a recognized framework is enough.
No repo to create, no access to configure, no git to learn - deploy straight from a local folder or a builder export.
Your first app can run for free, no card required.
Real platform tiers, and an honest comparison with renting your own VPS.
| Tier | Price | What you get |
|---|---|---|
| Free | 0 ₽/mo | One app with a database and a domain, no card required. The limit is resources, not a trial clock. |
| Startup | 990 ₽/mo | 5 apps, 2 databases, 7-day backups - for when the project outgrows the demo stage. |
| 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 scp-ing files, installing nginx, issuing a certificate and restarting the process after a crash are all manual. |
Three places an archive deploy usually trips.
A .env file in the archive is baked into the image with your code and shows up in build logs. Set keys as environment variables in the console instead.
User uploads and a SQLite file will not survive the next archive upload. Data goes to PostgreSQL, files to object storage.
Your version history here is the archives on your own machine. If you want one-click rollback and builds per commit, connect a GitHub repo to the same app.
No. Zip the project as zip or tar.gz and upload it in the console - the platform builds and runs the app without a repo.
Zip or tar.gz, up to 100MB.
It looks for a Dockerfile (port from EXPOSE), package.json with next, vite or react-scripts, or requirements.txt and pyproject.toml with fastapi, flask, django or streamlit.
0.0.0.0 and the PORT environment variable. If the archive has a Dockerfile with EXPOSE, the platform reads the port from there.
Yes - zip the export folder and upload it like any other project.
Add a Dockerfile to the archive with EXPOSE set to the right port - the platform builds from that.
Yes - first the app is created with a name, then the archive with the code is uploaded into it. Two quick steps on one page.
Yes, your first app can run on the free tier, no card required.
Zip the folder again and upload it once more - a new build starts while the old version keeps serving until the switch. No git, no commits.
Zipping the whole project folder is enough - the platform finds the root by the manifest inside. You can leave out venv, node_modules and .git: they only inflate the archive and are not needed for the build.
Into the app's environment variables, set in the console and injected at start. Avoid .env files inside the archive - those secrets end up in the image and in build logs.
Yes. Connect a GitHub repo to the same app and builds start following your pushes, while the address and environment variables stay the same.
Yes, they are ordinary folders with a package.json. Zip and upload - Next.js, Vite or React are detected and built with no configuration.
Three common reasons: larger than 100MB, a format other than zip or tar.gz, or no Dockerfile, package.json or requirements.txt inside - nothing for the platform to build from.
Create an account and deploy your first app. The Free plan costs $0.