Enterprise-grade home services marketplace platform — customers discover, book, pay for, and review at-home services; internal teams manage the full service commerce lifecycle through a dedicated admin panel.
Built as a modular monolith on Clean Architecture and DDD principles, designed so business modules can be extracted into microservices later without a rewrite.
New to this repository? Read docs/ORIENTATION.md first — it covers what actually exists today versus what is still planned, and the non-obvious conventions that will otherwise cost you time.
| Layer | Technology |
|---|---|
| Backend | .NET 8, ASP.NET Core Web API, Entity Framework Core |
| Database | PostgreSQL |
| Cache / Jobs | Redis, Hangfire |
| Frontend | Next.js, React, TypeScript |
| Infrastructure | Docker, REST, JWT authentication |
backend/
consumer-api/ Customer-facing REST API (ConsumerApi)
admin-api/ Admin/backoffice REST API (AdminApi)
shared/ Shared class libraries
Domain/ Business entities and rules (innermost layer)
Application/ Use cases and orchestration
Infrastructure/ Persistence, external services
BuildingBlocks/ Cross-cutting primitives (results, errors, validation)
frontend/
customer-web/ Customer web app (Next.js) — scaffold pending
admin-web/ Admin panel web app (Next.js) — scaffold pending
database/
migrations/ EF Core migration artifacts
scripts/ Operational SQL scripts
seed/ Idempotent seed data
docs/ Project documentation suite (see docs/README.md)
.claude/ AI collaboration rules (CLAUDE.md)
Prerequisites: .NET SDK 8.0.4xx (pinned in global.json), Node.js LTS, Docker.
# Build the full backend solution
dotnet build Nestly.sln
# Run the consumer API
dotnet run --project backend/consumer-api/ConsumerApi
# Run the admin API
dotnet run --project backend/admin-api/AdminApiFrontend apps and docker-compose for local PostgreSQL/Redis are pending scaffold — see the backlog.
The full documentation suite lives in docs/:
- PROJECT.md — vision, goals, modules
- SRS.md — complete requirements specification (v2)
- ARCHITECTURE.md — system architecture blueprint
- API.md · DATABASE.md · DOTNET.md · FRONTEND.md
- SECURITY.md · TESTING.md · CODING-STANDARDS.md · DEVOPS.md
- PROVIDER.md — deferred Provider/Vendor module design
- tasks.csv — phased development backlog
Greenfield — architecture and requirements are fully specified; feature implementation follows the phased backlog in docs/tasks.csv, starting with foundation hardening (Phase 0) and the Identity & Customer module (Phase 1).
main— productiondevelop— integration branch (default for PRs)