We’re here to shed a little light on how you can host and configure your multi-app projects on Platform.sh with a step-by-step guide on how to set up a project on our platform. Enabling your team to focus more on creating incredible user experiences and less on multi-app infrastructure management. As well as a few multi-app development tips along the way. We’re going to look at this through the lens of a customer on the lookout for multi-application hosting with a few specific constraints.

A platform as a service, or PaaS, is one of the three major cloud computing service models. In our opinion, it’s the only one that successfully delivers all benefits of the cloud to software developers, including control, cost-effectiveness, flexibility, and scalability. Of course, other as-a-service models are still useful. In fact, all three main cloud computing models offer different advantages to organizations.

Developing apps takes a lot of blood, sweat, and tears. It can feel like a marathon that doesn’t even have the courtesy to end once you cross the finish line. From managing infrastructure to scaling, operations, and security (to name just a few things), it takes plenty of work to ensure that your cherished creation is loved by users and customers. App hosting takes much of this responsibility off your shoulders, and a solid Platform as a Service (PaaS) provider can go even further.

You’re probably all very familiar with the URLs we currently generate automatically for your environments on Platform.sh by now. And while they are very useful, they’re not the most friendly-looking as, we build them using the following pattern: This approach is important because it ensures that our URLs are unique for all projects and their environments but it also makes them pretty long, overly complicated, and let’s face it—not the prettiest. But this is the case no more!

Today Bun 1.0 is being announced—one of our friends in the ‘.sh’ tld—so it’s an absolute pleasure to share a small celebration and our first thoughts on this fully-baked runtime.