Questions About Wappler's Suitability for Scaling and Compliance

Wappler General
1

Hi everyone,
I'm currently planning a serious healthcare project (MDR/AI Act compliance required) and considering Wappler + Supabase for this project.
Before committing fully, I would appreciate input from the community and core team on some specific questions regarding Wappler's portability, scalability, and compliance potential:

Portability & Code Ownership:

  1. How portable is a Wappler project once built? Can another development team maintain and extend it without using Wappler?
  2. Is the code export (Node.js or PHP) clean enough for external technical audits, especially under MDR and EU AI Act certification requirements?

Scalability & Architecture:

  1. Is Wappler suitable for building large-scale production apps (potentially handling millions of users)?
  2. Can Wappler handle modular backend designs or simulate microservice architecture natively?
  3. Does Wappler support Kubernetes deployments, serverless functions, or container-based scaling directly, or would this require external setup?
  4. How scalable are Wappler’s Server Connect APIs for high-load external integrations?
  5. Can Wappler handle real-time event streaming (e.g., WebSockets scaling, Kafka-style event streams)?

DevOps & CI/CD:

  1. Can Wappler projects be integrated into GitHub-based CI/CD pipelines for professional deployment workflows?
  2. Is it possible to version control Wappler workflows, server actions, and database schema changes reliably?
  3. Can Wappler auto-generate backend unit tests or at least support easy test coverage and audit logging needed for certifications?

Compliance & Security:

  1. Has any Wappler project been certified under GDPR, HIPAA, MDR, or EU AI Act audits yet?
  2. What best practices exist within Wappler for handling medical-grade data isolation, encryption at rest, encrypted communications, and audit-level access logging?

Thanks a lot in advance! :pray:
I really appreciate any deep technical insights or real-world experiences, especially from those who have scaled Wappler projects beyond MVP stage or into regulated industries.

2

In my honest opinion, Wappler is not suitable when it comes to DevOps & CI/CD. The architecture is meant for non-enterprise. Unit testing is lacking, environment variables are an afterthought implementation that does not conform to the strategies used in other back-end frameworks. That being said, if you're willing to hire, I know of someone that has implemented CI/CD in Wappler exactly like you want.

The output code is open, the front-end would be easy to modify, but the backend it's not feasible to modify without Wappler editor. Steps are stored in JSON, not typical code.

Considering steps are stored as JSON instead of code, it's a bit tricky.

I know of someone that did something in Wappler for healthcare, but I don't think it's a good idea for you, Wappler architecture is not enterprise ready. Maybe you could consider Laravel + Blade or AdonisJS?

1 Like
3

Thanks a lot for your detailed feedback — it was very helpful.

I appreciate you highlighting the strengths and current limitations of Wappler, especially around backend structure, DevOps, and compliance readiness.

This really helped me get a much clearer understanding for making the right technical decisions moving forward.

Thanks again for your time and insights!