Releases
New versions go live without dropping a request.
Each deployment starts beside the one that is running. Traffic only moves once the new container answers its health check, and the old one is removed afterwards.
Animated tour of Hoist: choose where the code lives (GitHub, GitLab or Bitbucket), link a public repository by its address, press Create and deploy, watch the build log until the deployment is live, then see the new service running beside the others in its project.
Your stack. Ready to deploy.
Works with Node.js, Next.js, Express, Fastify, NestJS, Static HTML, Dockerfile, GitHub, GitLab, Bitbucket, Codeberg.
The platform
Everything between commit and live.
The parts of shipping you would rather not build yourself, in one calm workspace.
Watch every build, line by line.
Build output streams into the dashboard as it happens. Your app’s own logs are one click away.
It works out how to build your code.
Hoist reads the repository and picks a build. Bring a Dockerfile and it uses that instead.
package.jsonNode.js 22 app, built with npm
Secrets stay secret.
Environment variables are encrypted at rest and handed to your app only when it starts.
One URL to deploy from anywhere.
Call the service’s deploy hook from CI or a Git webhook to ship the latest commit.
Every app in its own lane.
Each project gets a private network, and every container runs with fixed limits.
How it works
Three steps. One URL.
- 1
Paste a Git URL
Point Hoist at a public repository on GitHub, GitLab, Bitbucket or Codeberg and pick a branch.
- 2
Hoist builds it
Your code becomes a container image. Follow the build live, and set environment variables whenever you need them.
- 3
Open your app
Once the health check passes, your app is live at its own address. Redeploy with a click or a deploy hook.
Every deployment
Queued. Built. Live.
Each deployment moves through the same four stages, and the old version keeps serving until the new one is healthy.
Animated example: a board listing five sample services, each with a deployment moving from queued to building to starting to live.
Demo
FAQ
Good questions, straight answers.
Node.js applications and static sites, straight from a public Git repository. For any other runtime, add a Dockerfile and Hoist builds your application as a container.
Public repository URLs from GitHub, GitLab, Bitbucket and Codeberg. You choose the branch when you create the service. Private repositories are not supported yet.
Hoist builds a new container and checks that it answers before switching traffic to it. The current version keeps serving until then, so a failed build never takes your app down.
Yes. Every service has a deploy hook: send it a POST request from CI or a Git webhook and Hoist deploys the latest commit. Keep the URL private, because it authorizes deployments.
Not yet. Hoist is in early access: the deployment workflow works end to end, but it is not ready for unrestricted public sign-ups or critical production traffic.