How to put an app online without a GitHub repo

You have a folder. Something wrote you a working app and put it on your desktop, and now you want it at a web address.

Every guide you find opens the same way. Create a repository, commit your files, push. Netlify’s own support forum has a thread titled how to deploy from file, not from github, which is the question asked in the plainest possible terms. GitHub’s own community discussions have the upstream version, how to upload an entire folder. People are not confused about what they want. They want to skip the part in the middle.

Why the platforms ask for a repo

It is worth knowing that this is not gatekeeping.

A hosting platform connected to a repository rebuilds your app every time the code changes, and it puts the previous version back when a deploy breaks the site. It also keeps a record of what changed in between. Netlify’s documentation on deploy branches is built entirely around that model: a production branch feeds the main URL, and other branches get preview deploys.

All of that is genuinely useful, and none of it is useful to you yet. You have one version of one thing and no branches. The repo is buying you a workflow you do not have.

What accepts a folder today

Two paths work without git, and they are not equally good.

Netlify Drop is the shortest. You drag a project folder onto app.netlify.com/drop and it becomes a site. The behavior is worth reading carefully in Netlify’s deploy docs: if you are logged in, you can drop a project that still needs a build step and Netlify will detect the framework and run the build for you. If you drop a project without being logged in, it publishes the files exactly as they are.

Updating is manual in the way you would guess, so a one word typo fix costs you the same trip as a real release. You rebuild locally and drag the updated folder onto the deploys page again, which the docs note is also how you update any site not connected to a repository. You get a list of deploys out of it, but nothing that tells you what changed in the code between two of them.

A command line tool is the other path. Vercel’s CLI will deploy a directory with a --cwd flag pointing at the project, and Netlify has an equivalent. This works well and it does mean installing a CLI and authenticating it from a terminal. If that sentence was fine, this is the better option. If it was not, it is not a smaller ask than learning git. It is a differently shaped one.

What will not budge

Some platforms treat the repository as the account.

Streamlit Community Cloud is the clearest example. Its getting started guide has connecting your GitHub account as a required step, right after creating the Community Cloud account itself. There is no folder-shaped door.

That is a reasonable choice for a free service aimed at people who already write Python. It is also the reason a lot of small tools stay on the laptop of the person who wrote them.

The catch nobody mentions

Drag and drop solves the file transfer. It does not always solve the app.

Dropping a folder works cleanly when the thing you built is a web page, or a project whose build produces one. If your app needs to run code on a server when somebody clicks a button, or needs to keep data between visits, then a static drop is not enough, and you are back to choosing a platform on its merits.

The second catch is the one that decides whether you can actually send the link. A site you dropped is a public site. Anyone the link gets forwarded to has the tool, which is fine for a landing page and not fine for a headcount planner. Getting your company’s sign-in in front of it is a separate project on almost every platform in this category, and we went through which ones include it in where do you actually put it.

The honest recommendation

If your thing is a web page or a front end build, drop it on Netlify and move on with your day. It is the shortest path in the market and it has been for years.

If your thing runs code, or holds data that only the people you work with should see, the folder is not really the obstacle. The obstacle is that you need a server, a database and a door, and every platform in this space asks you to assemble those yourself.

That last case is what Sploot is being built for: hand over the folder, get back a link with your team’s sign-in already in front of it. It is in private beta with nothing to log into yet, so this is a description of where we are aiming rather than something to go try this afternoon.