Build interfaces that adapt to the task
Create your first adaptive view. Connect your data, register your views, and keep control of what your application can do.
Start here
Build your first adaptive view with five local records and four questions. Then connect your own data.
- 01
- Provide data
- 02
- Request a task
- 03
- Render an allowed view
Choose your next step#
Connect your application
Define a resource and render requests against your own data.
Connect your data ↗02 · ComponentsExplore the catalog
Try live examples and inspect properties, events, and accessibility.
Browse components ↗03 · AgentsAdd an agent
Expose a working surface through a bounded tool endpoint.
Agent quickstart ↗04 · WorkspacesCompose your views
Coordinate multiple results and register application layouts.
Build a workspace ↗Start with one useful result#
The React quickstart describes five local People records once, then asks four questions about them: everyone, one team, hires per month, and hires per team. Varendo answers with a table, a filtered table, a line chart, and a bar chart, without any table or chart markup from you. You need Node.js 24; no account, backend, or model key is needed.
Use What is Varendo? for the concepts, or choose an integration path for React, Vanilla, Vue, and the explicit Next.js server-rendering setup.
When to use Varendo#
Use it for data interfaces where the same records need different presentations: lists and details, comparisons, forms, dashboards, or workspaces controlled by application intent. It also supplies standalone components when your screen already owns its interaction state.
Varendo becomes useful when validation, data identity, view selection, and state preservation are recurring application work. A fixed marketing page or a one-off illustration usually needs authored HTML and CSS.
What your application registers#
A resource describes the data and its meaning. A data adapter reads it. Your application supplies current authority and allowed actions. Registered views and recipes define how approved results appear. An adaptive region is the container where a result is mounted.
Every request passes through validation, authorization, bounded data evaluation, and rendering. An agent submits the same kind of request as application code; it cannot supply executable UI or grant itself access. Your server still checks real data access and business effects.
For production integration, continue with existing applications and the advanced guides.
