Reuse proven building blocks without giving up control
Every new project comes with more than 50 BuildPad UI components installed, from single field inputs to complete modules like file management. Each is source in your repository, not a package. The DaaS backend behind them is provisioned and configured per project instead.
Reusable Modules
How reuse works here
- Components arrive as source
- More than 40 field interfaces
- Whole modules, not just controls
Installed into your codebase
Four levels, and each one is real code.
More than 50 components, from shared libraries up to complete modules. Every level is source you can open.
Foundation
Shared libraries
Types, services, hooks, utilities, authentication helpers and API routes that everything else builds on. Skip the default form and you can still reuse the permission hook instead of writing your own.
Smallest
Field interfaces
Schema-aware components for each data type and input pattern. DaaS field metadata maps to the right one automatically, so no collection needs a new input.
- Text and code
- Tags and sliders
- Selection and boolean
- Date and time
- Files and media
- Relations
- Workflow
- System fields
Composed
High-level components
Field interfaces combined into dynamic forms, tables with sorting and selection, paginated lists, field-aware filtering and content layout.
- VForm
- VTable
- CollectionForm
- CollectionList
- FilterPanel
- ContentNavigation
- ContentLayout
Complete
Application modules
Whole ready-made experiences, including file management and admin screens for users, roles and policies. Two are below.
What happens when you add a component.
Every level above arrives this way. A package dependency gives you only what it exposes. Copy & Own installs once.
Resolve
The CLI works out the component's npm packages, internal libraries and other registry components.
Fetch
Its source comes from the BuildPad UI registry, with everything it depends on.
Transform
BuildPad package imports are rewritten to your local paths.
Copy
The files are written into your app as your own source code.
No runtime dependency on BuildPad packages. Installed components work offline.
Two modules that show what complete means.
Both arrive through Copy & Own, so you get the source and can change it.
Files
A file experience, not an upload button
- Upload, file library, folder navigation and search
- Preview for image, video, audio and PDF
- Metadata editing and delete included
- Reusable hooks for file and folder operations
Upload, browse, search, preview and metadata, with folder and file hooks included.
Users
Administration for access control
- List and detail screens for users, roles and policies
- Role hierarchy and policy attachment handled
- The backend governance model surfaced in the app
- Admin work you do not have to build
List and detail screens for users, roles and policies: the backend model, exposed.
Reuse that survives customization.
An installed component is source in your repository from the moment it lands, not a package you do not control.
Other interfaces are rebuilt each time or locked in a closed package you can only configure. BuildPad UI is copied once, so an unplanned requirement is a change to your code, not a support ticket or a fork.
That is why Files and Users behave like the rest of your app, not an embedded widget. They use its field interfaces, high-level components and shared libraries, so the fiftieth feature fits like the first.
One layer of three
The interface is copied. The backend works differently.
All of this is the UI layer. The DaaS backend it renders against is provisioned with the project, not copied as source, then shaped through collections, fields, roles and policies.
See how the backend is provisionedWant to see this in a real app?
We show you this part working end to end, in an app we have built.
