How to Deploy a Site on deploybase

Updated

You can get a site live on deploybase in three ways: ask an AI agent (Claude, Cursor, or any MCP client), drag and drop a folder, or push from Git. All three end with your site on a *.sites.deploybase.eu link, and you can attach your own domain afterward. Pick the method that matches what you already have — a folder of files, a repository, or an agent-driven workflow.

Before you start

  • A free account. Every path below starts with creating one. Hosting is described as free to start, with flat pricing in euros on the pricing page.
  • Your content in one of three shapes: a folder containing at least an index.html, a Git repository (GitHub, GitLab, Bitbucket, Codeberg, or Forgejo), or a project you want an agent to handle.
  • A domain (optional). You can add your own domain when you're ready; it isn't required to go live.

Option 1: Drag and drop your files

Best when you have a static folder and no build step or repository.

  1. Create a free account.
  2. Start a new project and choose Upload a folder.
  3. Drag in the folder that contains your index.html (or pick it from the file browser).
  4. Your site is live at my-site.sites.deploybase.eu.

The free plan accepts uploads up to 250 MiB. No build and no repository are involved, so what you upload is what gets served.

Watch for: the folder you drag must contain index.html at its top level — dragging a parent folder that wraps your site in an extra directory level is the usual reason a page comes up empty.

Option 2: Push from Git

Best when you want every push to update the site and every branch to get its own preview link.

  1. Create a free account and connect your repository.
  2. Push your code.
  3. Each push updates your site. Code placed in a functions/ directory runs alongside it.
  4. Both go live on their own links:
    • Site: my-site.sites.deploybase.eu
    • Function: signup-my-site.fn.deploybase.eu (functions are in beta on paid plans)

A real deployment from the site's own example — a Vite site with one function, pushed on 26 September 2026 — shows what the timeline looks like: 1.7 s queued, 13.6 s build, 7.4 s to upload 12 files and bundle one function, live 32 seconds after the push. That's a small project, so treat it as a scale reference rather than a guarantee.

Watch for: functions are a beta feature on paid plans, so a free-plan Git project should be treated as static-only for now.

Option 3: Ask your AI agent

Best when you'd rather not touch a dashboard or a terminal.

  1. Paste this into your agent:

    Fetch and follow the instructions at https://deploybase.eu/agent-setup to set me up for deploybase, then deploy this project.

  2. The agent connects itself and asks you for one key. Only a person can create it, and the agent tells you where.

  3. It builds your repository and sends you the link.

This path needs a Git repository for now, so it won't work for a loose folder of files — use drag and drop for that.

Which method should you use?

Your situation Method Why
A folder of static files, no repo Drag and drop No build, no Git, 250 MiB limit on free
Existing repo, want branch previews Push from Git Every branch gets a preview link
Want an agent to do the setup AI agent Handles connection and build, needs a repo
Moving from Netlify or Vercel Any deploybase documents bringing your settings with you

After the first deploy

  • Add your own domain when you're ready — it's the last step in every path, not a prerequisite.
  • Roll back instantly if a deploy goes wrong; production is described as a pointer, so rollback doesn't require a rebuild.
  • Collect form submissions without a backend if your site needs a contact or signup form.
  • Move existing settings over if you're coming from Netlify or Vercel, rather than reconfiguring from scratch.

The fastest way to decide: if you have a repo, push from Git; if you have a folder, drag it in; if you want the setup handled for you and have a repo, hand it to your agent.