Project · scheduling
Tempo
- How you run it
- not recorded
- Holochain version
- 0.6.0
- Activity
- maintained
- Checked
- 29 October 2026
What is Tempo and what is it for?
Tempo is a Holochain app for scheduling together. It gives a group a shared calendar to arrange time in, rather than each person keeping a private one, and it is developed by the lightningrodlabs group as one of a family of small Holochain apps.
Tempo is a Holochain app for collaborative scheduling. Its repository describes it as a collaborative scheduling app built on the Schedule-X calendar interface, developed in the lightningrodlabs organisation alongside that group's other small Holochain apps and libraries, such as Moss for groups and Slate for drawing together. The repository's DNA is split into a profiles zome and a Tempo zome, and the codebase pairs a Svelte frontend with a Tauri desktop shell.
Most calendars belong to one person: you keep your own, and arranging a time with others means comparing several of them. Tempo takes the other starting point, putting the calendar in the middle of the group so that the schedule is something the participants share and work on together. It is built as a small, self-contained app that a group can add to its toolkit rather than as a broad suite.
A concrete place to start is the repository's own run instructions, which bring up Tempo with two participants at once so you can see a shared schedule in action: npm start for two local agents in the Electron build, or npm run start:moss to place it in a Moss group. The README also lists the Tauri desktop build and the build and packaging commands. Everything published about Tempo so far lives in that repository. Learn more at the project repository: https://github.com/lightningrodlabs/tempo
How to get it
Desktop app
- Install the Holochain development environment and enter the project's dev shell: nix develop
- Launch the app with npm start for the default Electron build, which runs two local agents, or npm run start:tauri for two Tauri desktop windows
Questions people ask
- Where does Tempo's source code live?
- Tempo is developed in the lightningrodlabs organisation on GitHub, where its repository sits alongside the group's other Holochain apps and libraries. source
- Can Tempo run outside Moss?
- Yes. The repository documents standalone desktop targets as well as a Moss target: npm start for the Electron build, npm run start:tauri for the Tauri build, and npm run start:moss for a Moss group. source
From 2 public sources, checked 23 September 2026.
Try Tempo
- Code on GitHubOpen on GitHub ↗Last change 28 May 2026.
- ReleaseNo GitHub release recorded.
- Moss code in the repository (last changed 1 May 2026)package.json @ ecf6b3a ↗
- Desktop app code in the repository (last changed 1 May 2026)src-tauri @ ecf6b3a ↗
- p2p-shipyard code in the repository (last changed 1 May 2026)src-tauri/Cargo.toml @ ecf6b3a ↗
Details & sources
- Source
- lightningrodlabs/tempo
Evidence
- Last change
- api.github.com/repos/lightningrodlabs/tempolisted by a third party · seen since 20 October 2026 · github.repository@1
- Activity
- api.github.com/repos/lightningrodlabs/tempolisted by a third party · seen since 20 October 2026 · liveness@1
- Moss
- package.json @ ecf6b3ain the code · seen since 20 October 2026 · moss.in-code@1
- Desktop app
- src-tauri @ ecf6b3ain the code · seen since 20 October 2026 · desktop.in-code@1
- p2p-shipyard
- src-tauri/Cargo.toml @ ecf6b3ain the code · seen since 20 October 2026 · p2p-shipyard.in-code@1
Compatibility
- hdk
- 0.6.0 · Cargo.toml @ ecf6b3a
- hdi
- 0.7.0 · Cargo.toml @ ecf6b3a
- holochain-client
- 0.20.4-rc.0 · ui/package.json @ ecf6b3a
- happ.yaml
- present · workdir/happ.yaml @ ecf6b3a
- web-happ.yaml
- present · workdir/web-happ.yaml @ ecf6b3a