Hi Hugo,
Thank you for the additional details. Your use case is very helpful, and it aligns closely with features already planned for MikroWizard.
Regarding multi-tenant deployments, MikroWizard is planning to include a Customer Portal designed for end customers to access and manage only their own devices and services. This is intended to support exactly the kind of ISP deployment you described and is planned as part of the Pro version roadmap.
For the Device Group permission scoping issue, I completely agree that proper customer isolation is essential. Based on your feedback, I will prioritize the dashboard and log visibility changes so that user permissions are enforced consistently across the platform. My goal is to include these improvements in the next update. i can also help you to change needed parts of the code to use SSL with API.
Regarding API SSL (8729), I agree that encrypted management traffic should be the standard when devices are accessible over the public internet. I will also prioritize native API SSL support and make it configurable directly from the UI in an upcoming release.
As a temporary alternative, the Pro version already includes WireGuard management features. This allows you to build a dedicated management network between MikroWizard and your MikroTik devices, keeping API access on private WireGuard tunnels instead of exposing management ports to the public internet. For many deployments, this provides an even more secure management architecture.
Thank you again for the detailed feedback. Real-world ISP requirements like yours help shape the MikroWizard roadmap and priorities.
Best regards,