The ability to combine servers into usable network clusters with load balancers is a fantastic suggestion. This feature would indeed be beneficial for users looking to scale their infrastructure and manage multiple servers efficiently. It could enhance performance, reliability, and the overall scalability of the hosting environment.

Have a well-organized and efficient staging environment: In a staging configuration, it would be great to be able to push to live and pull from production without going through the multiple states of cloning, renaming, etc. Bonus if, like some other platforms, we can choose what is synced: files/db, etc

For large sites with hundreds of GB of media which almost never changes, differential backup can drastically reduce the cost. Would be a shame to have to pay an S3 bill for that times 30 days retention. Summary: Implement differential backups

The backup is needed; however, it doesn't need to be backed up too frequently on some kind of website. Please consider the longer backup, like a weekly or customized period.

Global SMTP configuration rather thant per site

This will be helpful in increasing the performance of the website; Cloudflare, BunnyCDN or any other custom options are also good.

A proper status of the service running on server. Example i disabled the UFW via ssh, and forgot to enable it.... The dashboard didnt came up with a warning or indicator that a required service was down. A kind of overview on the existing "manage service" would be good to include system services like firewall, ftp, ssh etc.

Using SFTP as the destination for remote backups.

A simple firewall log to see the activities/blocks in dashboard. Right now ufw logs need to be looked manually on server.

With many test sites, it becomes difficult to remember which URL is which website. Please add the website name to the sites overview. This will make it easier to find the correct test website.

This will help us to see Historic Server Usage, also please enable site wise usage checks, which site consumes how much resources. Thanks

Siteground/Cloudways has their own cache plugin which have general features like combine CSS/JS, https enforce, enable object cache, image optimizer, lazyload etc. Also, it would be nice to have toggle security features from the plugin. I don't want to give flywp admin access to everyone.

AWS SES is ont of the best and cheapest SMTP provider for mail delivery. This should be included.

enable/disable native cron (DISABLE_WP_CRON)

Default backup profile feature for FlyWP that can be applied to all websites on a server at once.

Smart Updates is a feature (available at Plesk, Cloudways, for example) that automatically installs all WordPress updates (including Themes, Plugins, Translations etc), checks for any PHP/Database/server/front end errors on user-given key pages and automatically rolls back to previous backup if errors appear after update. We need this! :)

FlyWP would benefit significantly from implementing Docker quotas that manage usage on CPU, memory, and storage. Here's a breakdown of why this feature is essential and how it positions FlyWP competitively with providers like Cloudron: 1. Enhanced Resource Management Docker quotas allow for precise allocation of resources such as CPU, memory, and storage to individual containers. This ensures: Optimal Performance: Prevents resource hogging by individual users or sites, maintaining consistent performance across all applications. Scalability: FlyWP can optimize its infrastructure to serve a larger customer base without requiring excessive over-provisioning. Fair Usage Policies: Customers only consume the resources they pay for, avoiding conflicts over shared resources. 2. Improved Stability and Uptime With quotas in place, FlyWP can prevent scenarios where: One high-demand container impacts the performance of others on the same host. Memory or CPU exhaustion crashes critical services. By capping container resource usage, the platform ensures a more predictable and reliable environment for all customers. 3. Competitive Edge Against Cloudron and Others Competitors like Cloudron already use Docker quotas to provide robust isolation and predictable performance for applications. FlyWP adopting similar practices can: Match Industry Standards: Customers familiar with platforms like Cloudron expect these features. Attract Developers and Businesses: Resource caps give businesses confidence that their hosted applications will not be adversely affected by "noisy neighbors." Support Advanced Users: Developers often prefer platforms with fine-grained control over resource usage to optimize performance for their apps. 4. Cost Efficiency for FlyWP and Customers FlyWP: By monitoring and limiting excessive usage, FlyWP can better predict infrastructure needs and reduce operational costs. Customers: Tiered plans with clear resource allocations (e.g., CPU, memory, storage) provide transparency, allowing customers to choose the best-fit plan without paying for unnecessary overhead. 5. Security and Isolation Docker quotas enhance security by isolating workloads and limiting exposure to: Denial of Service (DoS): Prevents malicious or misconfigured containers from consuming all resources. Data Loss Risks: Avoids scenarios where one container fills up disk space, affecting storage availability for others. 6. Transparency and Monitoring Implementing Docker quotas gives FlyWP the ability to: Offer detailed metrics to customers on their CPU, memory, and storage usage. Alert customers when they approach their limits, providing opportunities to upgrade plans proactively. Conclusion By introducing Docker quotas, FlyWP will align itself with best practices seen in platforms like Cloudron, enhancing its resource management, stability, and scalability. This not only improves customer satisfaction but also positions FlyWP as a more competitive and reliable platform in the managed WordPress hosting space.

The ability to modify the WordPress Memory Limit the same way as PHP Memory Limit.

I generally use Fluent SMTP to handle emails, I could potentially remove this as it can be handled in the FlyWP Dashboard but I'd miss out on the email logging feature which I find essential during development

This would help in categorizing servers and sites, eg., news-websites, online-stores, etc.