Private alpha · Live on real data · Deployed in EU

Your data already knows.
Selvra tests it.

An autonomous research engine for one person's life. It collects passively, finds patterns, designs pre-registered studies — and runs each analysis once, by rules locked before the result exists. Then it remembers what it learned.

selvra · autonomous loop · 07:00
$ make loop→ fetching 22,954 readings · 85 days · live→ scanning 3 patterns found, 5 open hypotheses→ study 001 training → overnight glucose · retrospective, rule locked before analysis→ running the single confirmatory analysis … exposure1 training night vs 15 comparison nightseffect−0.47 mmol/L · 95% CI [−1.60, +1.24]verdictUNDETERMINED — by the locked rulenexta new study, once more training nights are logged

A real run, on the founder's real data. One exposed night cannot decide anything — and the engine says so instead of guessing. Even the interval's own calibration (~87% real coverage, measured on simulated data) ships with every report.

Every insights app shows correlations. Selvra runs experiments — the method of clinical trials, applied to a single person, automatically.
Built by a type 1 diabetic, on his own data
By the numbers

Real architecture.
Not vision-vocabulary.

EU sovereignty
Raw readings and the diary stay in the EU and never reach a model. What leaves is study text — design drafts and finished reports sent to the LLM, only when that layer is enabled.
Pre-registered by construction
Question, thesis and decision rule are locked and git-timestamped before the data is touched. The engine refuses to run anything that changed since.
Every claim labelled
Observed, derived, interpreted or self-reported — and every metric states what it does not measure. An ontology gate fails the build otherwise.
Statistics that fit one person
Days from one life are not independent. Block bootstrap for observations, randomisation tests for n-of-1 experiments — calibration-tested weekly.
22k+
Real glucose readings analysed
150+
Automated checks, every push
1
Confirmatory run per study — ever
EU
Region by construction
The engine

A research loop
that runs itself

Scan, hypothesize, pre-register, test, interpret, remember — the cycle a good analyst runs once, the engine runs every morning. The only decision left to a human is locking the study. That one stays human on purpose.

∞

Patterns, never peeks

The scanner finds deviations, clusters and trends, and proposes study questions — without revealing effect sizes. Measuring the effect is the study's job; seeing it early would corrupt the test.

Why not another insights app

Insights apps correlate: "your glucose rose after pasta." Selvra pre-registers a hypothesis, locks the decision rule, runs the analysis once, and reports a confidence interval you can hold it to.

Selvra

Memory that compounds

Every study leaves a lesson: question, verdict, next step. The engine reads its memory before designing, so each study builds on what is known instead of repeating it. Value compounds with time.

How it works

A morning loop,
not a dashboard

Talk to us →
01

Data arrives on its own

Glucose every five minutes, sleep and steps from a wearable, events from a calendar. Exposures can be derived from the data itself — and the design review checks each one against confounders like day type before it may be used. Manual logging shrinks to seconds a day.

02

The engine designs the study

The scanner proposes questions; the design layer drafts a full pre-registration — thesis, falsification, negative control, smallest effect that matters. A design review gates it. You lock it. That is the whole job.

03

Proof, in plain language

When the data suffices, the single confirmatory analysis runs by the locked rule — automatically. The verdict is interpreted in plain language, prioritised against open questions, and remembered for the next design.

Verticals

One engine.
Any domain with a goal.

Give the engine a passive data source, a measurable goal and an event log, and the same loop runs. Health first — where wrong conclusions cost the most, so the rigor is earned where it is hardest.

Deep Med Low Knowledge compounds illustration, not data
Type 1 diabetes

Selvra Diabetes

Live — running daily on real data

The research engine on real CGM data: Dexcom readings every five minutes, wearable sleep and steps, pre-registered studies with locked decision rules. "Does training lower my overnight glucose?" gets a confidence interval, not a guess — validated value-for-value against reference implementations.

signature ≠ trap
Musical signature

Motiq

Awaiting v0.2.5 SDK

Identifies what makes a musician's voice distinct. Separates signature from creative trap. Designed for the protocol from inception — Selvra integration as foundation, not feature. Awaits Python SDK port.

decision rule locked before the result
Business experiments

Selvra Business

On the roadmap

The same loop on company data: ERP transactions as the stream, margin and churn as outcomes, price changes and campaigns as exposures. Pre-registered answers to "did it actually work?" — after the engine has earned its rigor in health.

What a new domain inherits

Build the domain,
not the method

Get in touch →

Study engine

Pre-registration, locking, a single confirmatory run per study — the discipline of clinical research, solved once.

Statistical layer

Block bootstrap for autocorrelated days, randomisation tests for experiments, power estimated from your own data.

Design review

Every draft is checked against positivity, carryover and power on your own data before it can be locked.

Audit-ready provenance

Every claim traceable. Every action logged. Every result reproducible. Trust is structural, not promised.

Quality gates

150+ automated checks on every push: data contracts, an ontology that forces every metric to state what it does not measure, reproducibility.

Autonomous loop

Fetch, scan, run what is ready, interpret, prioritise — scheduled every morning. The analyst that never sleeps.

Your data already knows.
Let's test it.

Selvra is in private alpha, running daily on real data. Whichever side you come from — reach out.

I live with T1D → I'm building →