Skip to content
How it works

How your service runs

You publish your code; spredr builds it, runs it and puts it in reach of your customers with https. This is what happens on the way and what it guarantees you.

your repoGitHub or GitLabpushbuildspredr builds the imageand signs itsigned imageyour region · us or euyour servicein its own box, with itsown memory and CPUmi-apimi-webworkereach of your services in its own boxif it fallsanother machinetakes overif one fallsyour customerson your domainhttps
your repoGitHub or GitLabpushbuildspredr builds the imageand signs itsigned imageyour servicein its own box, with itsown memory and CPUmi-apimi-webworkerif it fallsanother machinetakes over if one fallsyour region · us or euhttpsyour customerson your domain

Your customers come in only over https. The machines have no other open door.

for you

What this guarantees you

only yours runsA machine starts only the image built from your commit. Nobody can swap it for another on the way.
your secrets don't travel looseYour variables are encrypted for the machine that runs your service. The build never sees them.
no other way inYour service gets traffic only over https, at its address or on your domain.
never a broken deployThe new release gets traffic only when it answers on its health path. If not, the previous one stays.