Add Foundry VTT as a hosting product

I’d like to suggest adding Foundry VTT to the product range as a new hosting product. A little about the software: Foundry VTT is an established virtual tabletop platform for online pen-and-paper sessions. Customers usually buy the software directly from Foundry and then set it up with their hosting provider. So for ZAP, the focus wouldn’t necessarily be on selling the license, but primarily on providing suitable hosting infrastructure. Why this is interesting from a hosting perspective: Foundry VTT isn’t a typical short-term game server use case; it’s more of a long-term hosting product. Game masters and groups often run their worlds, campaigns, files, maps, media, and configurations for many months or even years. This creates a use case with long-term customer retention, predictable usage, and steady demand. This could be particularly interesting for ZAP because there are only a few well-known providers of specialized Foundry hosting in the German-speaking market. Even fewer offer models that clearly stand apart from traditional monthly subscriptions. This is exactly where ZAP could make a real difference with its existing hosting model, especially with potential lifetime options. Key benefits for ZAP as a provider: Expand the portfolio with specialized hosting outside the traditional game server market Tap into a clear niche with relatively little strong competition in the German market Long usage periods per customer, as campaigns and worlds are usually run over the long term Strong platform retention, as users don’t want to keep moving their data, modules, assets, and configurations A good fit with ZAP’s existing model, especially if flexible or lifetime-based offers are possible A clear technical hosting use case, as customers mainly need an environment that’s simple, stable, and always accessible Important for capacity and product planning: Foundry isn’t just a standalone application; it’s often used with additional modules, extensions, maps, media, automation, and other content. This matters from a hosting perspective because storage needs, RAM requirements, and overall server load can vary considerably depending on usage. This would be an advantage for ZAP when designing its products, as it could clearly distinguish between smaller standard packages and more powerful packages.

Originally posted by Darkiyus on our previous feedback board.