Decides where time goes.
Work, training, recovery and everyday life share one readable view before any automation.
LifeOS is under construction
One calendar as the source of truth, independent modules, and data kept on your infrastructure. LifeOS aims to become the “Odoo for life” — without pretending every module already exists.
There is no LifeOS download yet. Force, the ecosystem’s training app, is currently available as an Android beta.
Local-firstData starts on your devices.
ModularEach capability can stand alone.
TraceableActions must remain understandable.
The vision, precisely
Work, training, recovery and everyday life share one readable view before any automation.
Force tracks training. Future modules may cover other needs without making the LifeOS core mandatory.
An app works on its own first, then shares only useful data with your LifeOS instance.
Products
Statuses come from one versioned source shared by the LifeOS and Force sites. Future products stay invisible until their scope is actually decided.
Plans, guides and records strength, cardio, mobility and timed activities. Works on its own, without an account.
Calendar, notes and modules in a local-first, self-hostable instance. The product is still in private development.

Local-first operation
The target is a self-hosted instance on your own hardware. If remote access is enabled later, the VPS only acts as an encrypted relay: no database, backup or persistent business component.
Public roadmap
Local-first training with an optional LifeOS connection.
Calendar, notes, modules, security, backups and reliable sync.
Documentation, reproducible builds, licence audits and multi-device testing.
Only after validating product, privacy and distribution.
Documentation
FAQ
No. LifeOS is still a private product under development. No release date, price or download is announced.
No. Force works locally on Android. Connecting a LifeOS instance is optional.
Not by default. Force stores its data on the phone. LifeOS targets self-hosting. No public LifeOS SaaS exists today.
No. In the planned architecture, the VPS can only relay explicitly allowed traffic to the local server and stores no user data.
Open-source publication is the goal, but the repository is not public yet. Licences, media and secrets must be audited first.