Platform
One place to deploy, host and watch your websites: deployments, HTTPS, custom domains, visitor stats and uptime checks, on servers we run for you.
- SourceGitHub · mainor a ZIP upload
- BuildNext.js · detectedisolated build container
- Runs oncompute node512 MB · 1 CPU · own network
- Addressshop.exampleHTTPS · certificate renewed
- Watcheduptime · SSL · trafficin your dashboard
Everything a website needs, in one place.
Each part does one job, and they are built to work together. You see all of it from one dashboard.
- Deploy
Deployments
Connect a GitHub repository or upload a ZIP. We detect the stack, build it in an isolated container and only switch over once the new version answers.
How deployments work - Run
Hosting
Each website runs in its own container with memory and CPU limits, on its own private network, behind a proxy that handles HTTPS.
What hosting includes - Address
Domains
A free address the moment your site is online, and your own domain with a few DNS records. Certificates are issued and renewed for you.
Connecting a domain - Servers
Compute nodes
The servers websites run on. Our control plane decides where each site goes and watches every node's health.
About compute nodes - Check
Production readiness check
A free, automated check of your project before you deploy: build, exposed secrets, missing settings, heavy assets and SEO gaps.
Check a project - Plans
Pricing
Plans by number of websites, with storage and bandwidth included. Monthly, six-monthly or yearly, in euros. Extra usage is never charged automatically.
See plans
From a commit to a watched, live site.
What happens every time you deploy, and afterwards.
- Source01
Your code arrives.
The latest commit of the GitHub branch you chose, or the ZIP you uploaded.
- Build02
We build it.
The stack is detected and built in an isolated container, with its own memory and time limits.
- Check03
We make sure it answers.
The new version is started and health-checked. If it fails, the previous version keeps running.
- Serve04
It goes live.
The proxy routes your addresses to the new container, over HTTPS.
- Watch05
We keep an eye on it.
Uptime is checked every two minutes and certificates every hour. Visitors, bandwidth and storage are counted.
You write the code. We run it.
Managed hosting means there's no server for you to log in to, patch or secure.
- We handle
- Servers · Docker · the proxy · TLS certificates · build environments · uptime and certificate checks · nightly backups, and restoring a site from one when you need it · deciding which server runs your site
- You handle
- Your code · your environment variables · your DNS records at your domain provider · pressing Deploy when you have changes
- Either of us
- Setting it up. If you'd rather not, email us and we'll deploy your site and connect your domain for you, free of charge.
What ProHostiva is built for.
So you can tell whether it fits before you sign up.
- Built for small to medium traffic: personal sites, business sites, client projects, web apps and APIs. Not for large high-traffic platforms.
- One container per website. Projects made of several containers (Docker Compose) aren't supported.
- Containers keep nothing between deployments: each deploy starts from your code. Keep uploads and databases in an external service.
- Deploys from GitHub are one click, not automatic on every push.
- DeploymentsFrom GitHub or a ZIP to a running site.
- HostingContainers, HTTPS, monitoring, backups.
- DomainsA free address, plus your own domains.
- Compute nodesThe servers your sites run on.
- Readiness checkA free check before you deploy.
- PricingPlans in euros, monthly to yearly.
Not sure what you need? Email support@prohostiva.com and a person will answer. We can deploy your site and connect your domain for you, free of charge.