Services Overview

98 service files in backend/src/services/ with matching interfaces in backend/src/interfaces/. Each service encapsulates business logic for a domain entity, injected into routes via the DI container.

DI Container

Services are created and wired in backend/src/services/create-services.ts, then attached to the Hono context as c.var.services. See Dependency Injection.

Key Services by Domain

Core Business

Service	File	Purpose
BuildingsService	buildings-service.ts	Building CRUD, geometry, metadata
ProjectService	project-service.ts	Projects lifecycle, phases
ScenarioService	scenario-service.ts	Scenarios comparison
BuildingComponentService	building-component-service.ts	Building Components management
MeasureService	measure-service.ts	Measures per scenario

CRM

Service	File	Purpose
ContactService	contact-service.ts	Contacts CRUD, claiming
CompanyService	company-service.ts	Companies management
LeadService	lead-service.ts	Leads pipeline

Finance

Service	File	Purpose
QuoteService	quote-service.ts	Quotes CRUD
QuoteFinanceService	quote-finance-service.ts	Financial Calculations for quotes
InvoiceService	invoice-service.ts	Invoices generation
CatalogService	catalog-service.ts	Products catalog
FundingCalculatorService	funding-calculator-service.ts	Funding Applications calculations

Documents & Files

Service	File	Purpose
DocumentRequestService	document-request-service.ts	Documents request workflow
DocumentObtainingService	document-obtaining/	Document Obtaining collection
FileService	file-service.ts	Files upload/storage
PdfExportService	pdf-export-service.ts	PDF Templates generation

Auth & Users

Service	File	Purpose
AuthService	auth-service.ts	Authentication, 2FA, password reset
UserService	user-service.ts	Users management
PortalService	portal-service.ts	Portal token operations

Automation & Scheduling

Service	File	Purpose
WorkflowStateMachine	workflow-state-machine.ts	Workflows state transitions
TaskService	task-service.ts	Task management
AppointmentService	appointment-service.ts	Appointments scheduling
FormService	form-service.ts	Forms submission

External Integrations

Service	File(s)	Purpose
HubSpot suite	hubspot/ (14 files)	HubSpot Integration sync
EntraService	entra/	Azure Entra SSO
NotificationService	notification-service.ts	Notifications dispatch
FeedbackService	feedback-service.ts	Feedback System
AuditLogService	audit-log-service.ts	Audit Logs
DepartmentService	department-service.ts	Departments

Interface Pattern

Each service has a matching interface in backend/src/interfaces/:

backend/src/interfaces/buildings-service.interface.ts
backend/src/services/buildings-service.ts

The interface defines the contract; the service implements it. Routes depend on interfaces, not implementations.

Related

• Service Layer Pattern — Detailed pattern documentation
• Dependency Injection — How services are wired and injected
• Routes Overview — Routes that consume services
• Backend Architecture — Layered architecture overview
• External Integrations — Third-party service connectors