Skip to content
Start

What spredr is

spredr is an orchestrator for your backends: it takes your code, builds it, runs it on machines from different providers and keeps it up even when one of them falls. You publish; spredr decides where it runs.

what you can publish

Any service that runs in a container

Each api, site or worker you deploy is a service. If your repo has a Dockerfile, spredr uses yours; if not, it detects your language and builds the image.

APIs and sitesThey answer on their own address with https, or on your domain.
WorkersBots, agents and queue consumers: they run with no public address.
From your repoGitHub or GitLab: every push to the branch publishes a new release.
From your terminalPublishing, watching and configuring, all from the CLI; with --json a script or an agent drives it.
what spredr does for you

What you don't have to run

buildingIt clones your commit, builds the image and signs it.
runningEach service in its own box, with a memory and CPU limit.
publishinghttps on your address and on your domains, through Cloudflare.
switching releasesThe new release takes over when it answers on its health path; if not, the previous one stays.
rescuingIf a machine falls, your services move to another on their own.
watchingLogs, memory, CPU, traffic and risks, live.