Add Foundry VTT as a hosting product

I would like to suggest adding Foundry VTT to our product lineup as a new hosting product.

A brief overview of the software:
Foundry VTT is a well-established virtual tabletop platform for online pen-and-paper gaming sessions. Customers typically purchase the software directly from Foundry and then integrate it with their hosting provider. For ZAP, this would not necessarily involve selling the license, but rather primarily providing a suitable hosting infrastructure.

Why this is interesting from a hosting perspective:
Foundry VTT is not a classic short-lived game server use case, but rather a hosting product used over the long term. 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 loyalty, predictable usage, and stable demand.

This would be particularly interesting for ZAP because there are only a few well-known providers of specialized Foundry hosting in the German-speaking market. Even rarer are models that clearly stand out from traditional monthly subscriptions. This is exactly where ZAP could make a real difference with its existing hosting model and, in particular, with potential lifetime options.

Relevant advantages for ZAP as a provider:

• Expansion of the portfolio to include a specialized hosting product outside of traditional game servers

• Tapping into a clear niche with comparatively little competition in the German market

• Long usage duration per customer, as campaigns and worlds are usually operated on a permanent basis

• High platform loyalty, as users do not want to constantly migrate their data, modules, assets, and configurations

• A good complement to the existing ZAP model, especially if flexible or lifetime-based offerings are possible

• Technically clear hosting use case, as customers primarily need a simple, stable, and permanently accessible environment

Important for capacity and product planning:
Foundry is not just a single application, but is often operated with additional modules, extensions, maps, media, automations, and other content. This is relevant from a hosting perspective because, depending on usage , storage requirements, RAM requirements, and overall server load can vary significantly. For ZAP, this would be an advantage in product design because it would allow for clear differentiation between smaller standard packages and more powerful packages.