git : GitHub
A content-addressed version-control engine, and a hosted home that runs it durably so teams don't have to.
eidos : timestore :: git : GitHub
It's the same engine.
Git is open source. GitHub is the hosted home that runs it for you. Eidos is the open substrate; timestore is the hosted home for it. Nothing in the hosted product is a fork or a crippled-then-upsold version of the open core — it is the exact same engine, made durable, supervised, and account-aware so you never have to operate it.
Two names, one mental model.
eidos : timestore
A content-addressed run-timeline engine, and a hosted home that runs its coordinator durably so you don't have to.
Open core, or hosted. Same code underneath.
The line isn't features — it's durability and operation. The open core does the whole job on one machine, zero cloud. The hosted coordinator is what makes it always-on across your devices and survives a wiped laptop.
Open core Live · free, self-hostable
Hosted Early access · live
CLI checkpoint and resume, cross-process, transcript attached — one machine, zero cloud.
Durable file sync across Macs you sign in. The transcript resume stays the CLI; the DMG does not record it.
Chronos autosave + local recovery of a file this machine saw deleted.
Hosted history survives a restart. Restoring a deletion another Mac recorded is not available yet.
Secrets engine — leased, not copied, with a kill-list. Crypto-shred of an account is designed, not a live deletion.
Device revoke from Settings. Account deletion is suspended and does not shred keys.
Self-host the coordinator — loopback or your own host, zero credentials, no vendor VM.
Accounts (Clerk or OPAQUE), storage quotas, and Solo/Team checkout in Settings.
The whole engine — reconciler, provenance model, MCP tools, daemon, deploy gate. Read it, run it, fork it.
Operated for you — same engine, but durable and supervised, so choosing hosted is choosing not to operate it.
Hosted early access is operating: accounts, file sync, team folders, storage quotas (1 GiB / 50 GiB / 500 GiB), and checkout in Settings. No public price. Trusted / FSKit does not ship. See the honest status →
We commit the core publicly, and we won't take it back.
Apache-2.0, committed in public
The core ships under Apache-2.0 — a real OSI license you can read, run, fork, and self-host. The coordinator runs on loopback or your own host with zero credentials. There is no “community edition” asterisk and no phone-home: what you read is what runs.
The OpenTofu lesson
When a vendor relicensed Terraform out from under the people who built on it, the community had to fork it into OpenTofu to get its open core back. We are not going to put you in that position. The core stays open; the commercial product is the hosted operation of it, not a license toll on the code you already depend on.
The deal is structural: if timestore the company ever went away, the engine you self-host keeps working — because choosing hosted was always choosing not to operate it, never being trapped by it.
Start with the open core.
Clone it, run it, resume a run across two processes with zero cloud — today. When you want it durable and always-on across your machines, that's what hosted adds.
Go to open.eidos.world ↗ GitHub ↗ Get early access to hosted