←Back to LifeNode OS

LifeNode OS

Platform & tools

How LifeNode OS is built, deployed, integrated, and improved — the stack under the hood and the workflow that keeps it reliable.

Technology stack

Application & UI

  • Next.js 16 (App Router) — routing, API routes, and server rendering
  • React 19 — interactive dashboards, nodes, and shell UI
  • TypeScript — type-safe features across the codebase
  • Tailwind CSS 4 — responsive layout for desktop and mobile browsers
  • TipTap — rich text in ProNode and document-style editors
  • Lucide React — consistent iconography across nodes

Data & authentication

  • Supabase (PostgreSQL) — user shell state, widgets, trackers, integrations, and node-specific tables
  • Row Level Security (RLS) — per-user data isolation at the database layer
  • NextAuth v5 — sessions, Google OAuth, and credential sign-in
  • bcrypt — hashed passwords and security-question answers for account recovery

Hosting, observability & billing

  • Vercel — production hosting, preview deploys, and edge delivery
  • Sentry — error monitoring and performance traces in production
  • Vercel Speed Insights — real-user performance signals
  • Lemon Squeezy — subscription checkout, webhooks, and customer portal
  • Termly — consent management and policy embeds on public pages

Integrations & AI

  • OAuth connectors — Gmail, Slack, Google Calendar, and selected health and business tools
  • Server-side token storage — integration credentials never ship to the browser
  • Linos — in-app AI assistant for summaries, drafts, and tracker chat (plan-metered)
  • ChefNode — AI recipe discovery and meal planning in HomeNode

How we build, improve & integrate

  1. Design from real workflows

    Features start from operator pain points — VA EOD logs, BizNode triage, household grocery sync — not abstract dashboards. Ann's GHL and automation background informs what ships first.

  2. AI-assisted development (vibe-coding)

    Cursor and agent skills accelerate implementation while human review keeps data migrations additive, storage keys stable, and billing gates aligned with plan entitlements.

  3. Integrate with MCP & docs tooling

    Supabase MCP for schema checks and logs, Context7 for framework docs, Sentry for incident triage, and Vercel tooling for deploy verification — so changes are validated before they reach users.

  4. Ship safely to production

    Additive database migrations only, patch/merge persistence (never wipe user rows), lint + build verification, and Playwright regression on auth and OAuth when integrations change.

GoHighLevel & business automation mindset

LifeNode OS is not a GHL white-label — it is a separate product — but it inherits the same design instincts Ann uses for clients: clear pipelines, accountable handoffs, and automations that respect human review. BizNode triage and VANode client workflows mirror how high-performing agencies run CRMs without forcing everyone into one vertical SaaS template.

Future connectors are prioritized when vendors offer stable OAuth or public APIs and when users report repeatable workflows (see Feedback & suggestions).

Local development

Developers run npm run dev from app/lifenode-os. Supabase env vars enable cloud sync; without them, local JSON fallbacks apply for shell state in development only. A server-only plan override exists for local QA of gated nodes — it never runs on Vercel production.

Related docs