.png)
Oura, enabled by you alone.
A personal extension. Only you can turn it on, and the data stays yours.
How it works.
If you want your own recovery data alongside your own week, you can connect Oura. No admin can do it for you and no team sees it.
Connected once, then nobody thinks about it.
You connect Oura
You authorise it from your own account, and you can disconnect it at any time.
Hatch starts reading
Hatch reads the work already happening in the tool. Nobody answers a form, nobody fills in a survey, and nothing gets migrated.
CREATE MATERIALIZED VIEW revenue_by_min AS SELECT date_trunc('minute', ts) AS minute, currency, sum(amount) AS revenue, count(*) AS payments FROM payments WHERE status = 'captured' GROUP BY 1, 2;
It joins the picture
The signal sits alongside everything else Hatch reads, including the agent layer, so who is performing and where capacity sits is visible without anyone reporting on it.
curl https://api.basalt.dev/v1/views/revenue_by_min?limit=5 \ -H "Authorization: Bearer $BASALT_TOKEN"
What you get.
What Hatch reads
Your own Oura recovery and sleep data, and only yours.
Who turns it on
You, at your own discretion. Nobody can enable it on your behalf.
Who it is for
You. The data stays yours.
What it does not ask for
No forms, no surveys, no migration. SOC 2 Type II, and customer data never trains models.
Find out what you actually have.
Thirty days, one named engineer, and a readout of what your team and your agents actually produced. $2,500, credited in full against your first year.