A platform for the servers you already own
Provelox runs on Docker Swarm. Give it an image and it gives you a domain, HTTPS, logs, usage and one-click rollbacks, on your own hardware.


Everything an app needs, in one console
These are real screens from a demo instance with made-up data. Pick a part to see it.
Every app in one place
Apps in collections with live status, instance counts, usage and the addresses each one answers on, under a summary of what is running, what needs a look and what has a newer image.


























Deploy from your pipeline with one request
Every app gets its own deploy key that can do one thing: deploy that app. Your CI builds the image, pushes it, and asks Provelox to roll it out. When a release misbehaves, roll back from the console.
For several services together, hand it a compose file. Provelox runs the stack, wires the services to each other, and gives the ones you choose a domain.
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: |
docker build -t registry.example.com/shop/web:${{ github.sha }} .
docker push registry.example.com/shop/web:${{ github.sha }}
# The key can deploy this one app and nothing else
- run: |
curl -fsS -X POST https://api.example.com/v1/ci/deploy \
-H "Authorization: Bearer ${{ secrets.DEPLOY_KEY }}" \
-H "Content-Type: application/json" \
-d '{"image":"registry.example.com/shop/web:${{ github.sha }}"}'What it takes care of for you
- Deploy an image and watch it roll out
- Point an app at an image tag. Provelox rolls it out, shows the progress, and keeps the versions you deployed so you can see what ran before and go back to it.
- HTTPS without the setup
- A proxy routes each hostname to its app and Let's Encrypt issues the certificates. Add your own domains and force HTTPS from the console.
- Docker Compose, as it is
- Paste a compose file and preview what will be created before anything is. Each service becomes an app on a private network, where names like db and redis work the way your file expects.
- Secrets that stay out of sight
- Secrets are Docker secrets, mounted as files under /run/secrets. Provelox passes the value to Docker and never keeps it or shows it again.
- CI keys that can do one thing
- Give a pipeline a key that deploys a single app. It cannot touch anything else.
- It only touches what it made
- Everything Provelox creates carries a label, and it checks that label before it changes or deletes anything. Other services on the server are invisible to it.
And more: Templates, Logs and usage, The console. See every feature.
Questions people ask
- What is Provelox?
- A platform that runs on your own servers with Docker Swarm. You give it a Docker image, and it gives you a domain, HTTPS, live logs, usage and one-click rollbacks, with a web console for all of it.
- What do I need to run it?
- A server with Docker, and a domain with a wildcard DNS record pointing at it. One server is enough, and you can add more later.
- Does it work with Docker Compose?
- Yes. Paste a compose file, preview what will be created, and each service becomes an app on a private network where service names like db and redis work as your file expects.
- Will it get in the way of other things on my server?
- No. Everything Provelox creates carries a label, and it checks that label before it changes or deletes anything. Other services on the server are invisible to it.
- When can I try it?
- Provelox is coming soon. Join the waitlist and we will write once, when it is ready to try.
Be first to know when it is ready
Provelox is coming soon. Leave your address and we will write once, when there is something to try.