WaveMaker review

WaveMaker is an application-development platform, not a standalone API, library or command-line tool. It combines agentic and template-driven code generation with a visual design canvas and code-editing tools. The hybrid studio lets developers move between agent, visual and editor modes to review and refine generated code.

The platform targets web and mobile application development, including design-to-code work from Figma. Its design agent generates front-end code, design tokens and a themed component library. WaveMaker also describes a two-pass coding system that combines a meta model, deterministic AI and human review. That places it in the app-building layer of a stack: teams use it to create applications and integrate APIs, rather than adopting it as an API runtime by itself. Enterprise customers can choose on-premise or private-cloud deployment. The vendor does not publish the underlying runtime architecture or deployment topology, so teams should confirm how generated applications are packaged and operated before committing.

The vendor describes API integration as part of application development, but does not publish a named API protocol, SDK, programming language, CLI or plugin surface on its homepage. It also describes a Figma design-to-code workflow and a configurable hybrid studio. That gives teams visual, agent and code-editor paths for working on generated applications, but does not establish which language or framework the generated code targets.

Confirm supported SDKs, languages, API protocols and integration patterns in WaveMaker’s technical documentation or with sales before planning an integration. In particular, ask whether your APIs require a specific authentication or request pattern, and how generated code handles those requirements. The homepage describes design tokens and themed components but does not give a documentation or API reference link in the published product text. Treat API integration as a capability to validate against your own services, not as evidence of a particular REST, GraphQL or event-driven interface.

WaveMaker lists no free plan and publishes no monthly or annual price for any tier. All tiers require a custom sales quote, so there is no public starting price to use for a budget estimate. The Solo plan is for individual developers and includes one developer seat, unlimited applications, unlimited end users and a 30-day free trial.

Teams is intended for small developer teams and includes unlimited applications and end users, but its exact seat cap and billing unit are not published. Enterprise is listed for on-premise or private-cloud development, with developer-seat-based licensing and unlimited applications and end users; deployment limits are not published. The vendor also does not publish add-on or overage costs. The listed pricing is seat-based where stated, rather than request- or compute-based, but the vendor does not publish enough detail to estimate a production bill. Ask for seat pricing, renewal terms, deployment charges, add-ons and any usage-based fees in the quote.

The vendor does not publish a public open-source licence or a source-availability statement for the WaveMaker platform. It does offer an Enterprise option for on-premise or private-cloud deployment, so WaveMaker is not limited to a vendor-hosted deployment. The vendor does not publish the deployment requirements or limits for those options.

Data export and project portability are also not described in the product text. Because WaveMaker combines generated code with platform-specific agent, visual and editor workflows, migration could involve more than moving application source; confirm which artifacts can be exported and used independently. Before signing, ask who owns generated code, whether it can be built outside WaveMaker, what formats are available for export, and what happens to access and support after a contract ends. Do not assume an open-source licence or unrestricted code portability.

WaveMaker says its agents use governed execution, enterprise architecture guardrails and a two-pass coding system with human review. Those are relevant controls for generated application code, but they do not replace operational limits or service commitments. The vendor does not publish rate limits, uptime figures, an SLA, backup and recovery terms, or numeric scaling limits in the published product text.

The homepage describes applications as secure and performant at scale, but teams should treat that as a vendor claim until they can review the technical and contractual details. Ask how authentication, secrets, dependency updates, vulnerability fixes and environment promotion work in your deployment model. For on-premise and private-cloud projects, confirm infrastructure requirements, upgrade responsibilities and support coverage. The pricing page lists deployment limits as unpublished for Enterprise, so establish whether the quote covers the environments and application count your production architecture needs.