Elysion

Software for funeral operations

Elysion is a multi-tenant B2B application for funeral businesses. It brings the people, appointments, burial arrangements, products and paperwork involved in an order into a shared workspace.

The domain requires connected information: a funeral order relates to customers and deceased-person records, ceremony events, service providers, order items and documents. Modeling these connections allows information to be reused across daily workflows instead of entered repeatedly.

Operational workflows

• Funeral orders connect customer records, deceased-person records, items, ceremonies and supporting documents.
• Planning includes ceremony events and a scheduling calendar.
• Cemetery management covers cemeteries, grave sites, ownership records and interments.
• Inventory includes articles, warehouses, stock movements, reservations, transfers and supplier orders.
• Administration manages tenants, locations, users, roles, permissions, subscriptions and feature entitlements.

Documents as part of the workflow

Versioned Word templates are populated with application data and converted to PDF through Gotenberg. Generated documents remain associated with the relevant record and template version. Azure Blob Storage supports file storage behind application interfaces.

This makes document production a traceable part of an order, alongside the operational data it represents.

A shared platform for distinct audiences

Funeral businesses use a dedicated tenant application; a separate administration application supports platform management. Both use React, TypeScript, MUI, TanStack Router and TanStack Query. Shared libraries provide forms, themes, authentication helpers, error handling and API access.

The frontend lives in an Nx workspace managed with pnpm. Dependency rules separate application-specific code from shared libraries, while an OpenAPI-generated TypeScript client connects the applications to the backend.

Backend architecture

The ASP.NET Core backend runs as a single API application. Domain, Application, Persistence, Infrastructure, Storage and WebServer projects separate business behavior from database, external-service and HTTP concerns.

MediatR organizes commands and queries; FluentValidation handles validation and AutoMapper supports mapping. Entity Framework Core and PostgreSQL implement persistence. Tenant locations, permission assignments, subscription plans, feature entitlements and storage usage are explicit parts of the platform model.

Engineering and operations

Azure Pipelines covers formatting, linting, tests, builds and Docker image publication. Application code and infrastructure configuration live in separate repositories, with Helm and Argo CD supporting Kubernetes deployments across development, staging and production.

Backend unit and integration tests, frontend tests and Storybook support development. Structured logging, OpenTelemetry, Seq and health checks provide operational visibility. The project brings together domain modeling, reusable interfaces, API contracts and delivery work in a specialized business application.