distravia Release delivery · est. 2016

Your release, everywhere, in one upload.

Distravia takes a build artifact and puts it in front of your users — in Sao Paulo, in Jakarta, in Warsaw — without you running a distribution tier of your own.

Software vendors ship to people who are nowhere near their build servers. Doing that well means edge capacity on six continents, a registry that survives a launch day, and someone answering the phone when a release goes out wrong. Most teams would rather spend that effort on the product. That is the whole of our business.

1.4 PBdelivered per month
34delivery regions
99.98%availability, trailing 12 months
2016in operation since

What we run

Release channels

Push a signed artifact once, tag it stable, beta or a channel of your own, and it is resolvable worldwide in under a minute. Rollbacks are a channel re-point, not a re-upload.

Package registry replication

We keep read-through replicas of your internal registries close to your teams and your CI, so a build in Bangalore does not pull every dependency across an ocean.

Artifact storage

Versioned, checksummed, retention-policy driven. Old builds stay reachable for as long as your support commitments say they must.

Who uses it

We do not host end-user content, websites or media libraries. Releases, packages and build artifacts only. It keeps the platform predictable and the abuse surface small.

Read the integration docs or talk to us about a migration.