Froots
Sign in Download ⌘D
v1.0 · macOS · Windows · Linux · iOS · Android

One app.
Your whole orchard.

Notes, routines, and agents — growing in the same soil. $14.99/mo. Free to try, forever.

Download Froots See the editor →
◉ Local-first ⌘ Encrypted sync ⟢ BYO model
index.md
orchard.md
routines/harvest.yml
⌘K orchard
The stack

Four tools,
one workspace.

Froots bundles what you'd normally glue together with five subscriptions and a shoebox of browser tabs. Every surface writes to the same local-first vault. Nothing is locked behind a cloud you don't control.

01 — Editor

A rich text editor that thinks in blocks, not documents.

Markdown under the hood, Notion-style blocks on top: tables, toggles, embeds, code, math, databases. Everything is a node — and every node is addressable by a routine.

02 — Routines

Automations that feel like writing a recipe.

Chain triggers, tools and model calls on a visual canvas. Zapier-style reach, n8n-style flexibility, with a first-class AI step.

03 — IDE

A code surface with a built-in agent harness.

Tabs, LSP, git, terminal — and a sidecar agent loop you can inspect, replay and roll back turn by turn. Built for the AI-pair-programming era, not retrofitted for it.

04 — Agents

Persistent little workers with memory of your vault.

Spawn named agents with scoped tools and permissions. They read your notes, call your routines, and leave receipts for everything they did.

05 — Sync

End-to-end encrypted. Yours on every device.

Desktop, mobile, web — same vault, same keys. We host it, but we can't read it. Self-host when you're ready.

06 — Fabric

Everything in one graph. Search across notes, routines, runs and agent memory.

Backlinks aren't just for markdown files anymore — a routine that edits a note shows up in that note's history. An agent that read a doc shows up in the graph. Your workspace has a spine.

◦ Semantic + lexical search in 40ms
◦ Scoped to vault, folder or tag
◦ Graph view with time slider
◦ Works offline; syncs on reconnect
Chapter one · The Editor

Write it once. It runs forever.

Select a paragraph. Hit ⌘⇧R. Your words become a routine any agent in your vault can run — forever, on your schedule.

Every block is a first-class object. Tables are databases. Lists are queues. The editor looks like Bear; it thinks like a compiler.

Try the editor Read the manual →
april 20 · orchard.md

A small philosophy of tools.

Most software asks you to translate a thought into its grammar. Froots is built on the opposite bet: your notes are the program. Write something once — a checklist, a brief, a decision — and it becomes an artifact that can execute itself.

Today's Bear writes beautifully but forgets the moment you close the window. Today's Notion remembers but does nothing. Today's Obsidian remembers and connects — but will not lift a finger. Froots is what happens when all three go to therapy together.

Routine · Turn selection into "daily standup" — ⌘⇧R

The cursor returns. The thought is done. Somewhere, quietly, a little agent picks up where you left off.

#philosophy #readme #pinned
Chapter two · Routines

Automations that
grow from sentences.

A routine in Froots is a small graph of steps — triggers, tools, model calls, branches. You can build one by dragging nodes, or by just writing it in plain English and letting the editor compile it.

Routine · daily harvest L3 · work

Every weekday at 8am, pick the three ripest issues and bring them to my desk with context.

Froots parses that sentence into a flow, lets you tweak the steps visually, and hands you a named, versioned automation you can share.

▸ Cron trigger ▸ Linear query ▸ Agent step ▸ Notion write
Cron · 08:00
Mon – Fri
Linear · query
priority:high, state:todo
Agent · Scribe
summarize top 3 → note
Notion · write
db: Daily, cover:🍓
Notify
channel: #me
Routine · morning L1 · ambient

When my alarm rings, start the coffee and raise the blinds before my feet hit the floor.

A two-node routine, built in ten seconds. Same grammar as the big ones — a trigger, a few actions, no cron expressions to memorize.

▸ Alarm ▸ HomeKit ▸ Shutters
Alarm · 06:45
iOS · nightstand
HomeKit · brew
device: Breville
Shutters · open
room: bedroom, 60%
Routine · reading digest L2 · weekly

Every Sunday at 9pm, email me everything I highlighted this week as one tidy digest.

Pulls from your Froots vault highlights, lets an agent cluster and title them, ships a Sunday-paper email you can actually look forward to.

▸ Cron ▸ Vault query ▸ Agent digest ▸ Email send
Cron · Sun 21:00
tz: America/New_York
Vault · highlights
range: last 7d
Agent · digest
cluster + headline
Email · send
to: me, subj: Week in notes
Routine · meeting prep L3 · work

Fifteen minutes before a meeting, brief me on the last three threads with whoever's in the room.

Watches your calendar, searches Gmail for each attendee, hands the raw thread to Scribe, drops the brief on your lock screen before you walk in.

▸ Calendar watch ▸ Gmail search ▸ Agent · Scribe ▸ Notify
Calendar · T−15m
any attendee
Gmail · search
per attendee, last 3
Agent · Scribe
brief: 120 words
Notify · me
iOS · lock screen
Routine · ship it L4 · ops

On merge to main, run the tests, build the release, deploy to staging if green, and post the diff to #eng.

A full CI/CD pipeline — webhook, test, build, branch-on-exit-code, deploy, notify — written as one sentence, shipped as one graph.

▸ GitHub webhook ▸ pnpm test ▸ Docker build ▸ Fly deploy ▸ Slack post
GitHub · push
branch: main
pnpm · test
shell, fail-fast
Docker · build
tag: sha-short
Fly · deploy
env: staging
Slack · post
#eng, diff + status
The roster

Meet your
little workers.

Every Froots install ships with four built-in agent personalities. Each has its own scope, tools and tone. You can rename them, re-skin them, or spawn new ones — but most people just get attached.

Researcher
Lime

Reads widely, cites everything, never gets tired of the library. Good at finding the second-best source.

Scribe
Yuzu

Writes your standups, meeting notes, release notes and weekly digest. Will match your voice if you let it.

Maker
Clem

Lives in the IDE, runs tests, opens PRs, rolls back when you ask. Turn-based agent, fully inspectable.

Gardener
Cherry

Keeps your vault tidy — archives stale notes, renames, fixes links. Runs quietly on a schedule you set.

Pricing

One price,
priced fairly.

Froots is free to download and use on one device with full access to everything. Pro adds our AI models, multi-device sync, and everything in Seedling. Teams bumps your model limits and runs a hosted cloud for your team — think Google Drive or OneDrive, but for your vault.

Seedling
Free
$0
  • One device, full access
  • Editor + local vault
  • Unlimited notes, markdown, math, tables
  • Routines + agent harness
  • Graph view and backlinks
Download Froots
No card required. Local-first, always.
the full orchard
Froots
Pro
$14.99 / mo
  • Everything in Seedling
  • Usage on our AI models — no extra key needed
  • Multi-device sync, end-to-end encrypted
  • 4 built-in agents + bring-your-own
  • Priority community support
Start 14 day trial
Bring your own keys if you prefer — always optional.
Orchard
Teams
$29/ seat / mo
  • Everything in Pro
  • Larger AI model limits
  • Hosted cloud vault (like Google Drive / OneDrive)
  • Shared vaults with roles
  • Audit log + SSO + admin policies
Talk to us
SOC2 Type II in progress · Q3 2026.
Roadmap

Four seasons
of growth.

Froots is in its first year. We ship in public, on a predictable cadence. Here's what's already ripe, what's on the tree, and what we're still planting.

Spring · Shipped

Foundations

Routines
The IDE
The editor
Local-first vault
Desktop apps · macOS / Win / Linux
Summer · You are here

Mobile & portability

iOS app
Android app
Import / export your data
Vault migration from Obsidian / Bear / Notion
Autumn · Next

Cloud & self-host

Hosted Froots cloud
OneDrive / Google Drive sync backends
Self-host, one-click deployments
Team vaults with roles and SSO
Winter · Later

Frontier

Our own model
Plugin SDK · public
Real-time collaboration (hosted cloud)
On-device local models
FAQ

The honest
fine print.

Straight answers about what Froots is, what it isn't, and where your data actually lives. If we missed something, write to us.

Is Froots a notes app or an automation tool?

Both, honestly. Underneath, it's a single graph — notes, routines, agent runs and code files all addressable from the same place. On the surface, you can use just the editor and ignore the rest. Most people start there.

What does "per device, per user" actually mean?

If you use Froots on your laptop and your phone, that's two devices. If your teammate wants their own copy, that's another user. Pricing is transparent and flat — no hidden seat tiers, no usage-based surprises.

Who pays for AI model tokens?

You do — directly to Anthropic, OpenAI, or whoever you point us at. We don't mark up inference. Bring your own key, keep your own bill. You can also run local models with zero token cost.

Can I self-host?

The app runs entirely offline already. For sync, you can use our hosted endpoint or point Froots at your own S3-compatible store. Self-hosted multi-user is on the roadmap for Winter.

How is this different from Obsidian / Bear / Notion?

It's the love child, basically. Bear's writing experience, Obsidian's local-first graph, Notion's blocks, and an agent harness none of them ship. The bet is that writing and doing belong in the same tool.

Is my data encrypted?

End-to-end, with keys derived on-device. We can't read your vault even if we wanted to — and we really don't want to.

Tweaks