Skip to main content
gavAI has three entry points: a visual Builder, an MCP server for AI clients, and a typed REST API. The same app can be authored through any of them — same JSON page document, same per-workspace runtime, same isolation. This page describes who each entry point fits, what the platform handles for you, and what “production-grade” means in concrete terms.

​
Three audiences

The three entry points are not separate products. A page composed in the Builder, a page generated by an MCP-driven agent, and a page POSTed as JSON all produce the same document in the same workspace. You can switch between them at any time, on any page.

​
What “production-grade” means here

A common concern about no-code platforms and AI-generated apps is that they ship demos that fall over in production. The boundaries that toys skip, gavAI handles: These are claims you can verify against the architecture, not aspirations.

​
What’s included without writing code

The full product surface is point-and-click in the Builder. You can ship an app that does all of the following without touching code:

​
Monetization

Payments are part of the platform, not an integration step:

​
What’s available if you write code

Every visual gesture in the Builder maps to a typed API call. Everything available without code is also available as code:

​
Where to go next