Skip to content
Helm

The console for the life you're actually running.

Helm is a private, modular dashboard for the things that run your week — notes, tasks, schedule, people, inbox, and infrastructure. Shape it around your own systems. Let the assistant handle the boring parts under your approval.

Try the demo

Built for

  • developers
  • founders
  • students
  • writers
  • home-lab operators
  • personal CRMs

The bridge

A live console. Toggle modules. Watch the ship change.

Helm is a registry of modules. Disable one and it leaves the navigation, the command palette, the assistant's toolset — together.

Notes

4 notes · semantic graph synced 2m ago

Local embeddings

  • Founding doctrine

    manifesto

    A personal OS, not another productivity suite. The captain decides which instruments are on the bridge.

    ↬ principles↬ modules

  • Why Helm > Notion

    positioning

    Notion treats your life as documents. Helm treats it as a workspace with a registry, jobs, and an operator.

    ↬ assistant↬ modules

  • Pomodoro session 14

    journal

    Wrote MVP scope. Cut shared workspaces, mobile, and authenticator. Ship the single-user bridge first.

    ↬ mvp↬ scope

  • Inbox triage rules

    settings

    Investors → review. Newsletters → archive. Anything marked urgent → ask before deciding.

    ↬ assistant↬ email

Embeddings run on your desktop. The cloud sees titles, not bodies.

Tip · press ⌘P anywhere to open the palette.

This is an illustrative preview, not the live product. Layouts, copy, and data are mocked for presentation purposes — the shipping version may differ in surface and behaviour.

Modules

Twelve instruments. All optional.

Each module is registered, scoped, and billed independently. The registry decides what appears in your navigation, palette, tools, and bill.

  • Notes

    Markdown notes with tags, groups, and URL capture.

  • Knowledge graph

    Semantic edges and local embeddings from your desktop.

  • Tasks

    Kanban boards with priorities, due dates, and drag-reorder.

  • Calendar

    Events, timetable, reminders, external sync hooks.

  • People

    Personal CRM with birthdays, follow-ups, relationship graph.

  • Inbox

    IMAP accounts with AI triage, categories, and suggestions.

  • Resources

    Servers, devices, APIs — uptime, metrics, safe commands.

  • Assistant

    Workspace-aware operator with module-derived tools.

  • Pomodoro

    Local timer with session history and desktop notifications.

  • Journal

    Entries connected to notes, events, and whiteboards.

  • Security

    Scoped tokens, audit log, encrypted integration secrets.

  • Publish (add-on)

    Optional public site. Isolated from private data.

More modules are unlocked as Helm matures. You choose what to enable.

The assistant

Not a chatbot. An operator with a permission slip.

Helm's assistant inherits its toolset from the modules you have enabled, the role you hold, the scopes on your token, and your workspace's approval policy — checked before every model request, not after.

Read tools
Search notes, calendar, people, emails, resources — run immediately.
Write tools
Create and update entities — held under your approval policy.
High-risk tools
Send mail, delete data, reboot a server — always require explicit confirmation.
Every call
Audited, budgeted, and reversible where reversible.

resolved at request time

workspace · solo

Tools

  • notes.search(q)

    Read · auto

  • tasks.upsert(card)

    Write · policy=open

  • calendar.create(event)

    Write · policy=ask

  • people.followup(id)

    Write · policy=open

  • email.send(thread, draft)

    Write · approval required

  • resources.restart(host, svc)

    Write · approval required

Gates · in order

  • Workspace membership
  • Module enabled
  • Role permission
  • Token scope
  • Entitlement (Pro · AI budget 78%)
  • Approval policy
Tools are derived from your registry. Disable a module and its tools disappear from the next request — before any token spend.

Principles

Opinions, where it counts. Constraints, everywhere else.

  1. 01

    Private by default

    Life data is never public unless a publishing module explicitly exposes it — and only behind isolated tenant routes.

  2. 02

    Modular by design

    Every feature is a registered module. Enable, disable, configure, and bill independently.

  3. 03

    Desktop-first, web-capable

    Tauri-based desktop app for daily power use. Web supports setup, billing, and emergency access.

  4. 04

    AI as operator

    Read tools run immediately. Write tools wait. High-risk actions always require approval.

  5. 05

    Local where it matters

    Embeddings, notifications, timers, and exports run on your device — without forcing everything through the cloud.

  6. 06

    Data portability

    Export and deletion are first-class. You can leave any time. No revolving doors.