— About

One founder, five apps, zero focus.

I had a marathon in October and a padel tournament in August. I was using five apps to manage it: Strava for logging runs, Google Calendar for blocking training time, Apple Notes for how each session actually felt, MyFitnessPal when I remembered to log meals, Garmin Connect for heart rate. None of them talked to each other, and none of them understood I was training for two specific things at once. Strava thought I was a runner. MyFitnessPal thought I was losing weight. My calendar didn't know a tempo run from a padel drill night.

The realization that became Orva: the missing thing was never more tracking. Every app wanted to collect more metrics, and my failure mode was never “not enough data.” It was the lack of commitment structure — no single place that knew my real goals, their real dates, and held one coherent schedule against them. Training has a shape: a beginning, a middle, an end. The apps assume you'll track forever. A season doesn't work like that.

What Orva enforces

The central object is the Arc — a bounded commitment block with a start date, an end date, and a goal set you declare up front. The AI drafts every session of the block; you refine it in chat and accept. Then the rules hold: one active Arc at a time, no parallel plans, no adding goals mid-block. Want to also train for Hyrox? That's the next Arc. It sounds restrictive until you notice it's the whole point — every other app gives you unlimited dashboards and you spread yourself thin. Orva gives you exactly one thing to look at, and the AI keeps the thread: every session, how it felt, what you ate, where you are in the block.

What it is not

Orva is not a coaching service — no humans, no expertise upsell. It's not a metrics platform, a calorie obsession, or a habit tracker with streaks and missed-day guilt. It won't pace you mid-workout or nag you in real time. It's the part of your brain that would track all of this if you had infinite attention — a memory, not a coach. The product is built around what I refuse to add as much as what I've built.

Who builds it

Orva is built by one person — me — as part of Antaras, a small team where each of us builds and owns our own product. No funding, no growth team — just a builder who lived the problem this app solves. Orva comes out of my own struggle: training for two real goals at once, juggling five apps, and watching the commitment slip through the cracks between them. The honest ambition is for Orva to stay small, serve the people who actually need this exact thing, and prove that disciplined, opinionated software is worth shipping. If you have feedback — what you wished worked differently across all those apps — reply to any email Orva sends you. I read everything.