A governed architecture for developmental data.

Embreier turns observations made by qualified adults into a longitudinal record that stays traceable from evidence to action.

Request a demoHow Embreier works

Core principles

Five properties the system is built to hold.

Not features. Constraints the architecture enforces, whichever adult is in the room.

Provenance by design

Every observation carries who made it, where, under what conditions and with what qualification. Provenance is written at capture, not reconstructed afterwards, so a decision taken months later can still be weighed against the evidence that produced it.

Human-owned decision support

Models synthesise evidence and draft proposals. A named adult accepts, edits or rejects, and that person is recorded as the owner with a review date. No consequential action is taken by the system alone.

Evidence-linked actions

Every proposal carries the observations underneath it. Follow the chain in either direction: from an action back to what was seen, or from an observation forward to what was decided and what followed.

Privacy by architecture

Consent is separated by purpose and revocable. Views are constructed per role rather than filtered after the fact, and institutional patterns appear only above a minimum cohort size.

Longitudinal infrastructure

Continuity survives a change of session, educator, class and year. What accumulates is movement and confidence over time, not a score taken once and carried forward.

Architecture

From one adult in a room to a longitudinal outcome.

Each step is authenticated, attributed and auditable. Governance runs alongside the pipeline rather than sitting at the end of it.

Qualified adultcertified, credential in dateAuthenticated captureone tap, one short noteObservation + provenancesetting, conditions, observer, evidence gradeDevelopment recordthe governed longitudinal storeEvidence synthesisproposal drafted, evidence citedNext action + named ownerwith a review dateFollow-up observationwhat actually happenedLongitudinal outcomemovement and confidence over timeFamilythe weekly cardEducatorone next actionSchoolsuppressed cohort viewResearchde-identified, consentedROLE-CONSTRUCTED VIEWSCONSENT · ACCESS CONTROL · SUPPRESSION · AUDIT

The record architecture · the loop closes back into the record · September 2026

Data protection

Identity and observation are stored apart.

Content and provenance live in the record; identity is held separately and keyed. The two are rejoined only for an adult whose role authorises it, which is what makes a family view, a classroom view and a suppressed institutional view different objects rather than different filters.

Swiss nLPDGDPRData held in Switzerland

Legal bases we operate under. Not certifications, and not presented as any.

Governance

Governed from the first observation.

Explicit consentSeparate permissions by purpose: delivery, observation, research. Revocable at any time.
ProvenanceEvery entry retains its source, its conditions and the qualification of the observer.
Role-based accessEach adult sees only what their role requires. Views are constructed, never filtered client-side.
Cohort suppressionInstitutional patterns appear only above a defined minimum group size.
No child surveillanceNo ambient audio, no video, no continuous capture. Purposeful inputs only.
No autonomous decisionsA named adult remains responsible for any consequential action.

See the architecture running.

Forty minutes: capture, provenance, the action a named adult owns, and what followed.

Request a demo

Read further

Where to go next.

Questions
Twenty-six answers
The company, the standard, the record, governance and the business model.
Product
The record, in use
A sample account, the workflow, what a school buys and what it costs.
Evidence
What is established
Validity, attribution, transfer, generalisability, and what remains to be shown.
Investors
The company
Overview, evidence, team, governance and materials.