About LifeOS

LifeOS started because no existing tool did what was needed. Calendar apps show events but not habits. Todo apps track tasks but not focus time. Dashboard tools try to do everything for everyone and end up doing nothing well for anyone. The goal was simple: one screen that shows the entire day, from schedule to habits to goals, in a layout that stays open all day.

This is not a product built by a team or backed by a company. It was built by a non-developer using AI-assisted development, one module at a time, solving real daily friction. The code is open source and meant to be forked. If the 5am day boundary does not fit your life, change it. If you want different AI models, swap them. The point is ownership -- of the tool, the data, and the workflow.

LifeOS runs on Vercel and Supabase, both of which have free tiers that handle single-user workloads comfortably. There is no account system, no onboarding flow, no pricing page. You deploy your own instance and it belongs to you.

“

Single-user, single-screen, single-purpose.

”

Principles

  • Single-user by design

    No team features, no collaboration, no multi-tenant database. One person, one instance, one dashboard. This keeps the codebase small and the security surface minimal.

  • Opinionated daily cycle

    The day runs from 5am to 4:59am. Late-night work belongs to today, not tomorrow. This is a deliberate design choice that matches how productive days actually flow, and it is configurable in one file.

  • Built by a non-developer

    LifeOS was built using AI-assisted development. Every line of code was written or reviewed with AI tools. This proves that useful software can come from clear thinking about problems, not just technical skill.

  • Self-hostable and forkable

    The repo is designed to be forked and deployed to your own Vercel and Supabase accounts. Versioned migrations, documented environment variables, and a clear setup guide make self-hosting straightforward.

  • Your data stays yours

    There is no central server, no analytics, no telemetry. Your Supabase database is yours. Your Google OAuth tokens are stored in a locked-down table on your own instance. Nothing phones home.