Skip to content

Your project from Git
is live

Connect the repository for your AI-built or custom website, set its build and publish it over HTTPS. For APIs and containers, check the runtime and plan your app needs.

3 free projects on your .hostbrid.dev subdomain. Creating an account is free; publishing with Dev requires a card saved in Stripe. You will not be charged.

a Hugo site, published
12 s
frameworks recognised
17
git providers
3

What each plan includes

Projects is included in your Sites plan. One subscription, two ways to publish.

Starter

Projects
No cap
Services
1
Your own domain
Yes

Pro

Projects
No cap
Services
3
Your own domain
Yes
6.99 €/moChoose plan Pro

Agency

Projects
No cap
Services
10
Your own domain
Yes
14.99 €/moChoose plan Agency

A project is a published repository. A service is a container that runs all the time —an API, a backend, a worker—, and that is why it is counted separately: static sites use nothing while nobody visits them. Domain registration and renewal are paid separately. Publishing with Dev requires a card saved in Stripe; you will not be charged. Creating an account is free and does not require one.

Not sure whether the free plan fits? Compare what it includes and when to pay. Read the guide

Find your framework

17 configurations for publishing static sites. Next.js, Nuxt and SvelteKit require static output; a backend runs as a service.

  • Astro
  • SvelteKitStatic output
  • VitePress
  • Docusaurus
  • Eleventy
  • Gatsby
  • NuxtStatic output
  • Next.jsStatic output
  • Vue CLI
  • Create React App
  • Vite
  • Hugo
  • Jekyll
  • MkDocs
  • Pelican
  • Sphinx
  • HTML

Docker: keep your application running

A static site serves files. A service runs your application in a container and stays on: APIs, backends or a public image.

Services require a paid plan and count towards its allowance: Starter 1, Pro 3, Agency 10. Execution is subject to plan resources; Dev has no always-on services.

Explore Projects

You connect the repository and it publishes itself

Not a mockup: this is the panel, on a sample account. The list shows which version is live right now.

my.hostbrid.com
The panel’s “Projects” screen: two projects —“Landing de la campaña” and “Web del estudio”—, each with its published address, the repository it comes from, the short id of the last commit, when it went out and a green “Published” label.The panel’s “Projects” screen: two projects —“Landing de la campaña” and “Web del estudio”—, each with its published address, the repository it comes from, the short id of the last commit, when it went out and a green “Published” label.
Earlier panel screenshot: automatic deployment on push requires a configured and verified webhook; confirm availability with Support. Each project shows its address, its repository and the exact commit that is live —9f8e7d6, a1b2c3d— with the counters on top: 2 projects and 0 of 3 services.

What you would do by hand, done

Clone, install, build, upload, certificate and domain. You keep writing the code.

Publish from your repository

Import your project from GitHub, GitLab or Bitbucket. Configure the branch, build commands and output folder to publish it with HTTPS.

  • GitHub
  • GitLab
  • Bitbucket

It recognises your project

17 configurations: Astro, Vite, static Next.js, Eleventy, Hugo, Jekyll, Docusaurus, MkDocs and more. If yours is missing, you set two commands by hand.

  • Astro
  • Vite
  • Hugo
  • 17

HTTPS from the first deploy

Your project goes live on its address with a valid certificate, nothing to configure. And on your own domain whenever you want.

  • Let's Encrypt
  • auto

Backends and containers too

A Node API, a service with its Dockerfile or a public image: we give it a domain, HTTPS and somewhere to run.

  • Docker
  • Node
  • APIs

With its database

Managed PostgreSQL, MariaDB or Redis, plugged into your project with one click: the address arrives in DATABASE_URL.

  • PostgreSQL
  • MariaDB
  • Redis

And when something breaks, you see it

The full build log, the container’s real state, and one click back to the previous deploy.

  • logs
  • rollback
Choose by outcome

Get your code to a URL you can share

The route depends on what you built. These checks help you avoid paying for control you do not need or choosing a plan that falls short.

  • Static site from Git

    If this sounds familiar: Your project outputs HTML, CSS and JavaScript.

    What you get: Projects builds the repository output and publishes it with HTTPS; check the framework and output directory.

    See the localhost route
  • API or persistent process

    If this sounds familiar: Your app responds to requests or runs background tasks.

    What you get: Check runtime, port, plan and service quota. Compare VPS if you need operating-system control.

    Plan a mobile API
  • Application data

    If this sounds familiar: Your website or backend needs PostgreSQL, MariaDB or Redis.

    What you get: Connect a compatible managed database; confirm the engine and how your app receives credentials.

    Compare databases

Tested on real repositories

Not on our own examples: importing public GitHub repositories one after another until they all worked.

Talk to sales
  • Astro, Vite, React, Eleventy, Hugo, Jekyll, Docusaurus, MkDocs, SvelteKit and more.
  • npm, pnpm or yarn: we use whichever your lockfile says, not the one that suits us.
  • A Node backend with no Dockerfile starts too: we add a standard one.
  • And if your repository has a Dockerfile, you are in charge: it builds as is.

Questions

Does every push publish automatically?
Automatic deployments require a configured and verified provider webhook. Confirm availability and configuration with Support before relying on them.
How do I publish from a monorepo?
For a standalone application, you can specify its subfolder. If it uses workspaces, sibling packages or a shared lockfile, keep the complete repository root and adapt the build commands and output folder to the application.
What if you do not recognise my repository?
You set the build command and output folder by hand and it works. Or bring a Dockerfile and it builds as is. What we will not do is guess and publish you an empty folder.
Can I deploy an API or a backend?
Yes, as a service: domain, HTTPS and a container to run in. It needs a paid plan because a process running 24/7 costs money every day.
What if a deploy goes wrong?
You get the full build log and roll back with one click. Production stays pinned to the one that worked until you say otherwise.
Can I see my code from the panel?
Yes, folders and files. Read live from your provider: we keep no copy, and the day you revoke access it stops showing immediately.
Can I disconnect my git account?
Whenever you like, from the panel. What is already published keeps working; disconnecting stops future reads from the repository.

Connect a repository and watch it go live

Three free projects, no lock-in, no time limit.

Manage your sites, servers and email.

Forgot your password?

Free, and it takes a minute.

At least 8 characters. Not all digits, not a common one.

We'll email you to confirm the account.