Deploy without git: upload a zip, get a live URL

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.

How to deploy from an archive

Four steps from a folder on your computer to a live address

01

Create the app in the console

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.

02

Zip your project

Package the project folder (or a Lovable, Bolt or v0 export) as zip or tar.gz - up to 100MB.

03

Drop the archive into the console

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.

04

Get a live address

The build usually takes 1-2 minutes, then the app is live at an HTTPS address like name-hash.dada-tuda.ru.

How deploy without git works

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.

Framework auto-detection

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.

Live HTTPS address in 1-2 minutes

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.

Your own Dockerfile works too

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 GitHub needed

No repo to create, no access to configure, no git to learn - deploy straight from a local folder or a builder export.

Free tier to start

Your first app can run for free, no card required.

What it costs

Real platform tiers, and an honest comparison with renting your own VPS.

TierPriceWhat you get
Free0 ₽/moOne app with a database and a domain, no card required. The limit is resources, not a trial clock.
Startup990 ₽/mo5 apps, 2 databases, 7-day backups - for when the project outgrows the demo stage.
Business2,900 ₽/mo20 apps, 10 databases, 30-day backups, priority support.
Your own VPScomparable on hardwareA 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.

Worth knowing up front

Three places an archive deploy usually trips.

Secrets inside the archive end up in the image

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.

The local disk is wiped on every build

User uploads and a SQLite file will not survive the next archive upload. Data goes to PostgreSQL, files to object storage.

There is no rollback to a previous archive

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.

Deploy without git - FAQ

Do I need git or GitHub to deploy a project?

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.

What archive formats and size limit?

Zip or tar.gz, up to 100MB.

How does the platform detect my framework?

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.

What port should my app listen on?

0.0.0.0 and the PORT environment variable. If the archive has a Dockerfile with EXPOSE, the platform reads the port from there.

Can I upload a Lovable, Bolt or v0 export?

Yes - zip the export folder and upload it like any other project.

What if my framework isn't auto-detected?

Add a Dockerfile to the archive with EXPOSE set to the right port - the platform builds from that.

Do I need to create the app first?

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.

Is it free?

Yes, your first app can run on the free tier, no card required.

How do I update the app after editing it?

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.

Should I zip the folder or its contents?

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.

Where do secrets and API keys go?

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.

Can I switch to git later?

Yes. Connect a GitHub repo to the same app and builds start following your pushes, while the address and environment variables stay the same.

Do exports from Lovable, Bolt or v0 work?

Yes, they are ordinary folders with a package.json. Zip and upload - Next.js, Vite or React are detected and built with no configuration.

Why was my archive rejected?

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.

Give your code a public address

Create an account and deploy your first app. The Free plan costs $0.

Create account