Where one person's software lives.
Small apps keep what you make as plain files on one computer you control, and every device you own, and your agents, reach them there.
Whispering, desktop speech-to-text for macOS, Windows, and Linux, installs today.
Run it freely under AGPL-3.0-or-later. What that means.
Try the CLI | How it works | Status | Trust | Repo map | Development | License
Use the latest Epicenter CLI for a new home. The developer preview runs on macOS or Linux, arm64 or x64. It requires Git, curl, and shasum or sha256sum. Bun and an AI account are not required.
curl -fsSL https://github.com/EpicenterHQ/epicenter/releases/download/epicenter-cli-v0.4.1/install.sh | shThe installer verifies the download and installs ~/.local/bin/epicenter.
With Git's user.name and user.email configured, create your Epicenter and
copy the Writing app:
export PATH="$HOME/.local/bin:$PATH"
epicenter init ~/Epicenter
cd ~/Epicenter
epicenter new writing --from EpicenterHQ/epicenter/examples/writing
epicenter serveOpen http://127.0.0.1:4747/writing/ to save a thought, quote, or link with its
source, then find and edit it. Keep the terminal open while the server runs.
Your notes are Markdown files in apps/writing/data/notes/. You own the app's
copy in apps/writing/code/ and can change it with your editor or coding agent.
Writing and Tasks both run on Epicenter 0.2.0 or later. To add Tasks to your home, run
epicenter new tasks --from EpicenterHQ/epicenter/examples/tasksFor CLI commands, MCP setup, and optional background service installation, see the CLI guide.
~/Epicenter is on a computer you control and keep on: the
home. It holds a folder per app in apps/. Each app has a code/epicenter.ts
that declares its collections and actions, an optional UI under code/ui/,
and a sibling data/ folder of Markdown files you can read. One private Git
repository holds the home. Checkpoints save pending code and records together.
import { defineApp, defineCollection, field } from '@epicenter/app';
const tasks = defineCollection({
path: 'data/tasks/{time}.md',
description: 'task',
fields: { title: field.text(), done: field.boolean() },
});
export default defineApp({
description: 'Things I mean to do',
collections: { tasks },
actions: tasks.actions(),
});The epicenter command runs an app's actions on the home. Actions change files;
checkpoints record their state in Git:
epicenter tasks add '{"title":"Call the bank"}'
epicenter tasks list --json
epicenter serveepicenter serve offers every app's actions over MCP, and each app's UI at
/<app>/, on the home. It listens only there; your private network, such as
Tailscale, brings your other devices in. Nothing syncs and no one signs in:
your phone, your laptop, and your agents reach the one copy on the home, and
keep nothing of their own. The home's optional origin is its backup remote.
Software that works without an Epicenter is an outside app: Gmail, Todoist, Whispering. An inside app brings its data in through actions. Mail pulls a copy of your mailbox to the home, and an agent changes Gmail only through a proposal you apply.
The vision | The epicenter command | What an app imports
The CLI developer preview installs as a standalone executable from
GitHub releases.
Writing is an exported app copied separately from GitHub. The executable
carries the runtime; each app remains ordinary editable source.
epicenter service install keeps serve running as a macOS LaunchAgent; the
Linux job for a rented home is not built yet.
The author's inside apps (Capture, Mail, Messages, Reading, Tasks, and Vocab)
run on their home, outside this runtime source repository. Each app has
apps/<app>/code/ and sibling data/ in the home's one private Git
repository. Root checkpoints record pending code and records together;
actions make no commits. App publication copies only code into a separate
history (ADR-0910).
Whispering, an outside app, runs in a browser tab and as a desktop app, and
needs no Epicenter. Epicenter, the company, also hosts services: sign-in and
paid models (apps/api).
The folder sync product that came before is retired (ADR-0899). Some of its code stays here while Whispering imports it.
Your data is on the home, and whoever can read the home can read it.
| Where | Who can read it |
|---|---|
| A home you own | You, and whatever you let reach it: devices on your tailnet, agents you give a shell. |
| A home you rent | You and its provider, which can read the disk, .local sign-in files included. |
| Your other devices | Only what a UI or agent fetches while it reaches the home. They keep no copy. |
The home's private origin backup |
Whoever hosts the backup repository can read all included apps and records. Nothing is pushed until you add an origin. |
| A service an inside app pulls from | The service already holds that data. Mail's Google sign-in is a .local file in Mail's folder on the home, and never leaves it. |
| Epicenter's hosted services | What you send them: a prompt or audio for a paid model, and your account. They hold no part of your Epicenter. |
serve signs no one in and listens only on the home, so which other devices
reach it is your private network's decision. See the
trust model for the details.
Applications under apps/ are outside apps
(apps/README.md).
| App | What it is |
|---|---|
| Whispering | Voice recorder and speech-to-text, in a browser tab or as a desktop app. Recordings, transcripts, and settings are files in a folder. |
| API | Epicenter's hosted services: sign-in, paid models, and hosted-only billing, on Cloudflare Workers. |
| Landing | The website at epicenter.so. |
| Package | What it is |
|---|---|
@epicenter/cli |
The epicenter command: runs each app's actions as commands and MCP tools, serves UIs, and checkpoints included code and records in one private root repository. |
@epicenter/app |
What an app's epicenter.ts imports: defineApp, defineCollection, defineAction, fields, folder, and the client a UI calls actions with. |
@epicenter/ui |
Shared Svelte components. |
@epicenter/ai |
Every source of models as an endpoint, one OpenAI-compatible client, the agent loop, and the model picker. |
@epicenter/server |
The Hono library apps/api composes. |
Whispering's own packages, and the folder sync product's code it still imports
(@epicenter/folder, @epicenter/definition, @epicenter/local), are under
packages/.
~/Epicenter on the home
EPICENTER.md marks the folder as an Epicenter
AGENTS.md sent to every MCP client as instructions
apps/<app>/
code/epicenter.ts collections and actions
code/ui/ the UI's source, built into code/ui/dist/
data/ the app's records in the private root history
packages/cli epicenter: runs actions, serve, snapshots, backup
packages/app what epicenter.ts imports
apps/api Epicenter's hosted services, an outside app from a homeUse Bun in this repo.
git clone https://github.com/EpicenterHQ/epicenter.git
cd epicenter
bun installEvery app starts from the repo root. bun dev:<app> runs every process the app needs; for apps that talk to the hosted API, that includes the API worker on localhost:8787. bun dev:<app>:ui runs the app's frontend alone when that split exists, and bun dev:api runs just the backend. Bare bun dev is bun dev:whispering, and bun run with no arguments lists every target.
| Command | Starts | App port |
|---|---|---|
bun dev:api |
Hosted API worker alone | 8787 |
bun dev:api-dashboard |
API + dashboard UI | 5178 |
bun dev:landing |
Landing site, standalone | 4321 |
bun dev:whispering runs Whispering in a browser tab.
The API needs local Postgres and Infisical; see apps/api/README.md. Rust is needed for Whispering's desktop build.
bun run check is the gate. It runs lint, typecheck, every workspace test, and the structural checks, and it is the same gate CI runs, so a green local run predicts a green pull request. Formatting is handled separately by the autofix workflow.
bun run checkRun the pieces on their own while you work:
bun run format # rewrite formatting (CI autofixes this for you)
bun run lint:check
bun run typecheck
bun run test
bun run check:structure # doc paths, catalog pins, API paths, UI boundary, boot purity, vocabulary, state pathsOne check sits outside the gate on purpose. bun run check:doc-hygiene flags specs and ADRs that time has made stale, so it belongs to review rather than to merge.
Durable decisions and their reasoning live in docs/adr/. Specs in specs/ are in-flight design scaffolding rather than current truth; when a spec and an ADR disagree, the ADR wins. Start with docs/README.md.
Contributions are welcome. Good entry points are docs, the epicenter command, Svelte interfaces, Whispering, and small changes that make the repo easier to understand.
Contributors coordinate in Discord.
Everything is AGPL-3.0-or-later. An MIT toolkit tier existed until 2026-08 and was dissolved; versions already published under MIT stay MIT for those versions.
See the root LICENSE, FINANCIAL_SUSTAINABILITY.md, and the licensing strategy for the full model.
Contact: [email protected] | Discord | @braden_wong_
Your data outlives the app that wrote it. Open source, on a computer you control, built on plain files, with its history in Git.