Push to deploy
Every push to your production branch builds and deploys. Works with GitHub, GitLab, Bitbucket, Gitea and Forgejo.
Choose a product
Web HostingWebsites and WordPress on a fixed-price planCloudDeploy apps, APIs and databases from Git or DockerAI BuilderCreate and change sites and apps with AIAdd to any project
Domains & emailDatabasesManaged WordPressAgent runtimesMigrationsDevelopers
Everything AIDevelopersMCP for AI assistantsDocumentationSecurityStatusHostingsurge
PricingSign inDeploy
Deploy any app from Git. Every push builds.
Connect a repository or upload a folder. Hostingsurge detects the framework, builds your app and runs it on servers in the EU — with logs, one-click rollback and custom domains with automatic SSL.
Push to deployA preview per branchBuild and runtime logsRollbackAutomatic SSLServers in France
shop-webProduction: shop.example · branch main
DeployDeploymentsLogsDomainsSettings
Buildingfeat/reviewsAdd product reviewsPreviewAddress when the build is ready—
ReadyCurrentmainUpdate checkout copyProductionshop.example48s
Readyfeat/searchAdd search to the headerPreviewfeat-search--shop-web.hostingsurge.app52s
Readyfix/cart-totalFix cart total roundingPreviewfix-cart-total--shop-web.hostingsurge.app41s
Push to deploy: on
build logs · feat/reviewsBuilding
✓ Next.js detected ✓ Dependencies installed › Building the application…
From repository to live app
Three steps the first time. After that, a push is all it takes.
- Connect your codeImport a repository from GitHub, GitLab, Bitbucket or any Git URL — private ones connect with a read-only deploy key we generate. No Git? Upload a folder or a ZIP file.
- We handle the buildHostingsurge recognizes the framework, sets the build and start commands and streams the log while it builds. You can change the commands at any time.
- Go live, then push to updateWhen the build is ready, the new version goes live in production. With push-to-deploy on, every push to your production branch ships the next version — and a rollback is one click away.
Bring the stack you already use
The framework is detected from your code and the build is set up for you. This is what you can deploy today.
| Runtime | What you can deploy | Runs as |
|---|---|---|
| Static site | HTML, CSS and JavaScript, or the output of a static site generator | Static files |
| Next.js | Full Next.js apps with server-side rendering | A Node.js server |
| Vite | React, Vue and Svelte apps built with Vite | Static files |
| Node.js | Servers built with Express, Fastify, NestJS, Hono and more | Your start command |
| Python | Django, Flask and FastAPI apps | Your app server |
| PHP | PHP sites and Laravel apps | nginx and PHP-FPM |
| Docker image | A ready-made image from a container registry | The image, as is |
| Folder or ZIP | Files uploaded straight from your computer, no Git needed | Same as its framework |
Everything a production app needs
Logs, rollbacks, variables, domains and scheduled jobs — in the dashboard, the CLI or the API.
Build and runtime logs
Follow a build line by line, then read what your app prints while it runs — in the dashboard or from your terminal.
One-click rollback
Make an earlier production deployment live again, or promote another deployment to production. One click either way.
Environment variables
Keep keys and settings out of your code. Set them per project, mark secrets as sensitive and pull them locally with the CLI.
Custom domains and SSL
Add your domain, verify it with a TXT record and get a Let’s Encrypt certificate automatically. Redirect www and old domains too.
Cron jobs
Run recurring commands on a schedule inside your app’s container. Need one to run right away? Hit Run now.
Deploy hooks
A secret URL that redeploys production when called — from CI, a CMS publish button or any other service.
A preview per branch
Push a branch and it gets its own preview address, so you can check a change before it reaches production. Not for WordPress sites.
Protection and edge rules
Put a password or an IP allow-list in front of a deployment, force HTTPS and set response headers and redirects.
Databases next to your app
Add PostgreSQL, MySQL, MariaDB, Redis or MongoDB on your team’s private network. The connection string lands in your environment variables.
Not metered yet: traffic and storage. Build minutes are counted per team, and each project runs within the CPU and memory limit of your plan.
Deploy from your terminal, CI or AI assistant
The dashboard is one way in. The CLI, the REST API and MCP handle deploys, logs, variables and domains too, so scripts, pipelines and agents can ship.
- A CLI for terminals and CI, with --json output for scripts and agents
- HOSTINGSURGE_TOKEN for CI pipelines, so there’s no login step
- A REST API with an OpenAPI spec
- MCP for Claude, ChatGPT, Cursor and VS Code: sign in, no keys to paste
# Install the CLI and log in npm i -g https://hostingsurge.com/cli/hostingsurge.tgz hostingsurge login # Link this folder to a project and deploy it hostingsurge link hostingsurge deploy --prod # Follow what your app prints hostingsurge logs --follow
Built for isolation
Teams, builds and data are kept apart, on servers in the EU.
Isolated per team
Every team’s projects, data and credentials are isolated from other teams.
Isolated builds
Each build runs on its own. A failed build never replaces the version that’s live.
Hosted in the EU
Servers in France, behind a firewall, with TLS and a hardened proxy in front of your apps.
No servers to manage
No SSH keys, proxies or control panels to look after. You work in the dashboard, the CLI, the API or over MCP.
Deploy questions, answered
Stacks, Git, domains and what happens when a deploy fails.
Which frameworks and languages can I deploy?
Static sites, Next.js with server-side rendering, Vite apps, Node.js, Python and PHP, plus Docker images from a registry and folder or ZIP uploads. The framework is detected from your code, and you can adjust the build and start commands.
Do I need GitHub?
No. Import from any Git host by URL — GitHub, GitLab, Bitbucket, Codeberg, Gitea or your own server. Private repositories connect with a read-only deploy key that Hostingsurge generates. You can also upload a folder or ZIP file, or deploy from your terminal with the CLI.
How do I move a project from Vercel?
Use the Vercel import with a read token. It brings over the framework and build settings, visible environment variables and domain redirects; you add secret variables and recreate cron jobs yourself. The app runs on a preview address while Vercel keeps serving, and you change DNS when it checks out. How migrations work
What happens if a deploy fails?
The failed build stops with its full log, and the version that’s live keeps serving. If a release that did go live misbehaves, roll back to an earlier production deployment in one click.
Can I use my own domain?
Yes. Add the domain, publish a TXT record to prove you own it and add the exact DNS records the dashboard shows. The SSL certificate is issued automatically, and you can redirect other domains, like www, to your main one.
Where are my apps hosted?
On servers in France (EU), behind a firewall with TLS and a hardened proxy. Every team’s projects, data and credentials are isolated from other teams.
What does Deploy cost?
Deploy is part of Cloud, priced like Railway and Render. Hobby is $5 and Pro $20 a month, each including the same amount of usage; beyond that CPU is $20 per vCPU-month and memory $10 per GB-month, billed per second. Fixed-price instances start at $7 a month, and static sites and builds are free. Prices in USD, excluding VAT. Deploy prices
Deploy your first app on Free.
Connect a repository or upload a folder. Moving from Vercel? Import the project and check it on a preview address before you change DNS.