LifeOS is under construction

The system connecting your days.

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.

Mock-up based on the current interfaceNo real data
Time stays visibly in charge.Illustrative composition based on the current product; it exposes no user data.

Local-firstData starts on your devices.

ModularEach capability can stand alone.

TraceableActions must remain understandable.

The vision, precisely

One place to see life. Not one app to lock everything in.

The calendar

Decides where time goes.

Work, training, recovery and everyday life share one readable view before any automation.

The modules

Stay specialised.

Force tracks training. Future modules may cover other needs without making the LifeOS core mandatory.

The connections

Stay optional.

An app works on its own first, then shares only useful data with your LifeOS instance.

Products

What exists.
What comes next.

Statuses come from one versioned source shared by the LifeOS and Force sites. Future products stay invisible until their scope is actually decided.

ForceTraining

Plans, guides and records strength, cardio, mobility and timed activities. Works on its own, without an account.

Android beta availableView Force ↗
LifeOSPersonal core

Calendar, notes and modules in a local-first, self-hostable instance. The product is still in private development.

Coming soonNo announced date
Nocturnal foliage, part of the LifeOS visual identity

Local-first operation

Your server works.
The VPS stores nothing.

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.

Data source
Local LifeOS instance
Remote access
Optional limited relay
Force
Works without LifeOS
Public SaaS
Not launched

Public roadmap

Progress through proof, not announcements.

  1. AvailableForce Android beta

    Local-first training with an optional LifeOS connection.

  2. In progressStabilise local LifeOS

    Calendar, notes, modules, security, backups and reliable sync.

  3. NextPrepare clean distribution

    Documentation, reproducible builds, licence audits and multi-device testing.

  4. LaterEvaluate cloud and stores

    Only after validating product, privacy and distribution.

Documentation

Limits are part of the product.

FAQ

Straight answers.

Is LifeOS available?

No. LifeOS is still a private product under development. No release date, price or download is announced.

Does Force require LifeOS?

No. Force works locally on Android. Connecting a LifeOS instance is optional.

Does my data go to a cloud?

Not by default. Force stores its data on the phone. LifeOS targets self-hosting. No public LifeOS SaaS exists today.

Does the VPS host LifeOS?

No. In the planned architecture, the VPS can only relay explicitly allowed traffic to the local server and stores no user data.

Is it open source?

Open-source publication is the goal, but the repository is not public yet. Licences, media and secrets must be audited first.