Understand the Platform

A guided path through the Emofy Platform for engineers — from "what is this product" to the request lifecycle, auth, and the domain model.

This section is the engineering handbook for the Emofy Platform. It is written for someone who is new to the codebase and wants to understand the whole system: what the product is, how the apps and services fit together, how a request flows through the backend, how authentication and multi-tenancy work, and where each feature lives.

If you are building a third-party integration instead of working on the platform itself, start in the Developer / Partner API section.

This site is access-gated. The platform section documents internal APIs and architecture — treat its contents as internal-only.

Start here

What is Emofy?

The product, who it serves, and the one idea the whole architecture is built around.

Local development setup

From a fresh clone to a running stack — install, env, and your first health check.

Repository tour

Every app and shared package in the monorepo, and what each is for.

Architecture overview

The big-picture map: apps, the backend pipeline, data, and the ecosystem.

A reading path for your first day

The pages below are ordered so each one builds on the last. Read them top to bottom and you will have a working mental model of the platform.

What is Emofy? — the product thesis. Everything downstream makes sense once you understand the child development passport and the EMA ecosystem.
Repository tour — find your way around apps/ and packages/.
Local development setup — get the stack running so you can read code with the app in front of you.
Architecture overview → Backend → Request lifecycle — how the system is shaped and how one request travels through it.
Authentication → Authorization (RBAC) → Multi-tenancy — the trust model.
Domains overview — the map of every feature area and the rule that decides what lives in core vs. an EMA.
API conventions and the ADR index — the agreements that keep the codebase consistent.

Reference

Internal API Reference

Interactive OpenAPI reference for the full internal API surface.

Architecture Decision Records

The significant decisions that shaped the platform, each with its rationale.

The one rule to remember

Emofy is a multi-tenant platform. Almost everything is scoped to an organization, and tenant isolation is enforced in the data layer by the OrgScopedRepository pattern — never by hand. If you remember nothing else from your first day, remember that.