Managed VPS

VPS Where ZAP-Hosting (you) make basic stuff like initial server setup, security hardening, updates + patches, monitoring, backups, maybe optimization.

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.

Ansible Playbooks

Ansible Playbooks is a good way to deploy software standardized across multiple servers. (IAC [Infrastructure as Code], but in this Case for the stuff on the Machine. While terraform for example is Machine ordering + Definition) Basically a way to run the playbooks in zap-hosting directly instead of having to run them locally. less Network latency Reliable Secure Automation (If machine gets a reset it can automatically Trigger the ansible playbook)

Options for Custom WI apps

I wish i can create own “apps/games“ without create a gameserver and change the start argument

Lifetime VPS Location Migration & Higher Usage Limits

Hello Zap-Hosting Team, I’m writing to suggest some improvements for your Lifetime VPS product to make it more flexible and user-friendly for long-term users: Add an Official Location Migration Currently there’s no easy way to move a lifetime VPS to another server location and there's no even ASIA server location on your choices tbh its really hassle (e.g., for you Asian Customers like me). This means many users end up needing to purchase a new VPS just to get a different region/location, which is inefficient and costly. 👉 Please consider adding an migration feature so we can switch server regions without having to buy a new server. Increase Resource / Usage Limits The existing limits (e.g., CPU/usage caps) can be too restrictive — for example, some VPS can get locked during basic tasks like OS installation or heavier workloads. Higher available limits or optional upgrade tiers would greatly improve usability and reduce disruptions when working on projects. Overall, these changes would make the Lifetime VPS product more practical and satisfying for customers who want long-term reliability and flexibility without unnecessary extra purchases.

Make an option buy a docker containers

Like you buy/rent a managed container. (That runs on managed zap-machines, while they offer stuff like redudancy) but allows people to host that pretty simple… (Ofc they should be somehow a bit restricted, so not one person can just take the entire machine)

Webspace Locations

More Webspace Locations like USA

Login Alert for Unusual Location

Send an email notification when an account login is detected from an unusual or previously unseen region. The alert should provide general information (time and approximate region) and a way to secure the account if the login was not authorized.

Update for Node in Webspaces

I wish the Webspaces get a newer Version of Node

cars

GPU Server/vGPUS

AI is becoming more and more relevant and it is important to have a European partner for this, not just US companies. It would therefore be great if servers with graphics cards/AI accelerators could also be offered. (This would also be a good way to expand the business segment at the moment). The whole thing can then also be offered as streaming PCs, similar to Shadow Cloud Gaming, which could be interesting given the current hardware prices.

Snapshots & Automated Backups for VPS

To improve reliability and reduce data-loss risks for VPS users, ZAP-Hosting can introduce a simple yet powerful Backup System with: 1. Manual Snapshots Users should be able to take on-demand snapshots before doing major updates or changes. These snapshots would let them roll back instantly if something breaks. 2. Free Weekly Auto-Backup Every VPS could come with one free weekly automatic backup. This gives all users at least one fallback point without needing any paid add-ons. There should also be an option to choose which day the weekly backup runs, so people can schedule it around their maintenance routines. 3. Paid Daily Backups For users who want more protection, there could be a paid “Daily Auto-Backup” option. This would take a backup every day and store several restore points. It’s an easy upsell and something many people are already familiar with from other providers. 4. One-Click Restore Restoring should be straightforward. Select the backup or snapshot, click restore, confirm, done. Ideally, there should also be an option to restore to a new VPS instance so production servers aren’t overwritten by accident.

More database selection

Unfortunately, at the moment there is only MarieDB for the databases, but you often need PostgreSQL or MongoDB, which is why it would be really helpful if you could also select these. (For example, I would like to run Wiki.js on my web space which will only support PostgreSQL in the future and MarieDB would therefore no longer work).

Secure ZAP-Storage

Upgrade the ZAP-Storage server to allow for the use of secure protocols. It’s nice that the FTP server is set up to use a password, but FTP does NOT encrypt the login credentials you use when logging in. I suggest using SFTP instead.

Improvements to Affiliate System + Better Stats Transparency

I’d like to suggest several improvements to the Affiliate & Partner system to improve transparency, reduce confusion, and fix balance/stat inconsistencies. Add an “Unwithdrawable” tag or maybe estimated payout date in booking history for all affiliate orders that are below 30 days, so users clearly know why commission cannot be withdrawn yet. Show commission percentage per product in affiliate history so users know exactly how much commission each service provides. Show renewal transactions in affiliate history as renewals also generate commission and are important for long-term earnings tracking. Add a “Lifetime” or “Monthly” tag on services, as lifetime orders currently look like credit orders and are hard to differentiate. Add old balance and new balance details for every affiliate transaction to show balance before and after the transaction and fix balance inconsistency confusion. Add a custom date range option in stats so affiliates can view performance for specific time periods. Consider merging Partner and Affiliate systems or allowing commission on Partner links, as partners are currently told not to use partner links because they do not earn commission, which is confusing. Allow affiliates to export stats and transactions as CSV for accounting and tracking purposes.

Add Storage-as-a-Service (SaaS) to ZAP-Hosting

I would like to propose adding Storage-as-a-Service, allowing customers to purchase standalone, secure cloud storage from Zap-Hosting for backups, logs, maps, world files, modpacks, large assets, and general data storage. This would work similarly to industry standards like AWS S3, Google Cloud Storage, and DigitalOcean Spaces but simplified for everyday users, gamers, and developers. How It Could Work Users purchase storage (e.g., 20GB, 50GB, 100GB, 500GB, etc.) They receive a simple panel with upload/download functionality Optional S3-compatible API for advanced users File access through secure URLs

Add Managed Databases (Database-as-a-Service) to ZAP-Hosting

I would like to suggest adding Database-as-a-Service (DBaaS) options so users can host standalone databases on ZAP-Hosting without needing a VPS or dedicated server. This would include managed instances of commonly used databases such as: MySQL / MariaDB PostgreSQL MongoDB Redis (Optional in future) SQLite cloud storage, etc. Benefits to ZAP Hosting New recurring revenue product More professional ecosystem similar to DigitalOcean, AWS, Linode, etc. Adds value to existing game server and VPS customers Strong upsell opportunity for partners and affiliates

Proposal to reintroduce the prepaid payment option

ZAP-Hosting used to offer the option of paying for servers and services not only via contract models, but also via a prepaid model. This feature was extremely attractive to many users (myself included) as it offered more flexibility and was ideal for occasional users or short-term purposes. Why reintroducing prepaid would make sense: 1. flexibility for customers: Many users only want to use servers on a project-by-project or temporary basis without committing to a contract right away. 2. low barrier to entry: New or cautious customers prefer to test with prepaid instead of an ongoing contract. This can lead to more new customers. 3. customer satisfaction & retention: More choice generally increases satisfaction. 4. many customers have greatly appreciated the function in the past.

Zap Coins Expansion

Special discount tiers unlocked through Zap Coin purchases