Describe operational data
Keep each source's fields and relationships explicit so an operator and an API consumer work from one model.
Dashier is built around a practical idea: developers should be able to focus on their application without recreating a separate admin dashboard for every data model. The product brings data sources, generated tables and forms, REST endpoints, and access controls into one administrative layer.
Its working hierarchy is Organization → Projects → Data Sources → Records. A source definition describes fields and relationships and becomes the basis for managing records and connecting an existing application.
Product principle
Build your application. Never build another admin dashboard.
Product teams often need internal CRUD screens, role-aware access, and endpoints alongside their customer-facing application. Building each of those surfaces separately adds code to maintain and creates opportunities for models and permissions to diverge. Dashier aims to make that administrative layer consistent with the data definition, while leaving the application’s customer experience and domain-specific behavior in the application.
Keep each source's fields and relationships explicit so an operator and an API consumer work from one model.
Generate tables and forms for the record work that would otherwise be repeatedly rebuilt in individual applications.
Expose a per-source REST interface and configure access for teammates and API callers.