Everything you do in Adobe Experience Platform Launch has the ultimate goal of producing a set of files to control the behavior of your application at run-time. This set of files is called a build.
Builds need to be hosted somewhere so client devices can retrieve them at run-time as needed.
Platform Launch can either manage the hosting of these files for you or you can do it yourself.
Adobe is not in the business of web-hosting. If you choose to have Adobe manage the hosting, your builds are delivered to a third-party content delivery network (CDN) that we have a contract with.
Currently, the primary CDN provider is Akamai. Files hosted on Akamai have a domain of
The primary reason to use managed hosting is convenience. It is easier to create the required host, and you don’t have to worry about maintenance.
If you don’t want Adobe to manage your hosted files, you must host them yourself. To host your files, you need to get the completed builds from Platform Launch and to be responsible for getting the files through your company’s release cycle onto company managed servers.
There are a number of reasons to choose to host your own build files.
There are two methods you can use to acquire completed builds so that you can self-host.
You can have Platform Launch deliver builds as a packaged .zip file (encryption optional). You can then unzip the package and insert the contents into your release cycle to place them on your own servers.
Use a Managed by Adobe host and select the Archive option on your environment. The environment provides a download link. Whenever a build is created, you can retrieve it from the environment’s download link.
You can have Platform Launch deliver builds directly to an SFTP server that you created. You take responsibility to get these filed into your release cycle and push them live.
To perform a direct delivery, you should create an SFTP host and assign that host to your environment. Whenever you build a library in that environment, the files are delivered to your SFTP server.