How bnod-gh/danta works
Danta is a multi-tenant dental-practice management SaaS. The primary user workflow is staff using the web dashboard or mobile app to access practice operations and clinical records; the API provides business logic and persistence, with identity, gateway, practice, and worker services supporting the product. The tree shows distinct booking, patient-care, billing, imaging, claims, communications, and reporting capabilities. Arrows between frontends and services are architectural links documented only at a high level; the sampled excerpts do not establish their runtime wiring.
Main entry points: gateway/src API gateway · web/src Web dashboard · app Mobile app · api/src Core API
Components 20
User applications
- Web dashboard
apps/web/src - Mobile app
apps/mobile/app
Platform services
- API gateway
apps/gateway/src - Identity service
apps/identity/src - Core API
apps/api/src - Practice service
apps/practice/src
Practice operations
- Appointments
apps/api/src/modules/appointments - Scheduling
apps/api/src/modules/schedules - Billing and payments
apps/api/src/modules/invoices - Claims integrations
apps/api/src/modules/claim-integrations - Communications
apps/api/src/modules/communication - Reporting
apps/api/src/modules/reports
Clinical care
- Patient records
apps/api/src/modules/patients - Clinical records
apps/api/src/modules/clinical-notes - Dental charting
apps/api/src/modules/dental-charts - Dental imaging
apps/api/src/modules/imaging-images
Data and jobs
- Background jobs
apps/worker/src - Database
packages/database - File storage
apps/api/src/storage
Other components
- Practice staff
Connections 7
- Practice staff → Web dashboard: uses dashboard
- Practice staff → Mobile app: uses mobile app
- Web dashboard → API gateway: sends requests
- Mobile app → API gateway: sends requests
- API gateway → Core API: routes requests
- API gateway → Identity service: routes requests
- Core API → Database: persists data