Reuse proven building blocks without giving up control
A new project comes with more than 50 BuildPad UI components already installed, from single field inputs up to complete modules like file management. Every one is source code in your own repository, not a package. That covers the interface layer: the DaaS backend behind it is provisioned per project and configured, not copied the same way.
- Components arrive as source
- More than 40 field interfaces
- Whole modules, not just controls
Four levels, and each one is real code.
More than 50 components, built up from shared libraries at the bottom to a complete module at the top. None of it is a black box: every level is source you can open.
Foundation 01 of 04
Shared libraries
Types, services, hooks, utilities, authentication helpers and API routes the rest of the stack is built on. A team that skips the default form can still reuse the permission hook rather than write another authorization client.
What happens when you add a component.
Every level above arrives the same way. Most component libraries install as a package dependency, and you get whatever the package exposes. With Copy & Own, installing is a one-time step.
Resolve
The CLI works out what the component needs, including npm packages, internal libraries and other registry components.
Fetch
The component's source is fetched from the BuildPad UI registry, along with everything it depends on.
Transform
BuildPad package imports are rewritten to your project's own local paths.
Copy
The files are written into your application, where they become part of your source code.
The copied code has no runtime dependency on BuildPad packages, and installed components work offline. Nothing is fetched from BuildPad while your application runs.
Two modules that show what complete means.
Both arrive through the same Copy & Own model, so your application gets the source and can change it.
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.
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
- Repetitive 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.
A component you install is source in your own repository from the moment it lands, not a promise from a package you do not control.
An interface can be produced from scratch every time, or it can come from a closed package you can only configure from the outside. BuildPad UI takes neither path. Because the code is copied once instead of fetched at runtime, a requirement the original component didn't anticipate is a change to your code, not a support ticket or a fork.
The interface is copied. The backend works differently.
Everything on this page is the UI layer: components that render against your project's own DaaS backend. That backend isn't installed as source. It's provisioned when the project is created, then shaped through collections, fields, roles and policies instead.
See how the backend is provisioned