Home Assistant alerts, Uptime Kuma incidents, Kopia backups, GitHub deploys —
alongside your calendar and tasks. Native macOS. All local.
Tempo shows and proposes; it never acts on its own.
Private beta · No spam · Unsubscribe anytime
What Tempo does
⚡
Every signal, one feed
Calendar, tasks, HA automations, monitoring alerts, backup runs, CI deploys — one chronological timeline, no dashboard juggling.
↗
Actions, ready to go
SSH to a flagged host, open a HA dashboard, restart a container, ack an incident — every event ships with the buttons you'd reach for.
🔒
Local-first, LAN-reachable
Local SQLite. No account, no cloud, no telemetry. The HTTP ingestion endpoint binds your LAN with per-provider tokens — your NAS, HA, and monitoring stack post directly.
If it speaks HTTP, it works with Tempo.
Modules ship for the usual homelab stack. Anything else just POSTs JSON
to Tempo's LAN endpoint — Home Assistant automation, n8n flow, bash one-liner with curl,
Grafana webhook. No plugin SDK, no rebuild.
Each event carries its own action set. Build them visually in the
Action Builder — buttons, terminal commands,
Apple Shortcuts, URL schemes. Use payload tokens like
{{host}}
so each click already knows the context.
// curl from anything on your LAN// → it shows up in the timeline
{
"title": "web-01 DOWN",
"eventType": "alert",
"providerIdentifier": "com.uptime-kuma",
"metadata": { "host": "web-01", "ip": "10.0.1.42" },
"actions": [
{ "label": "SSH", "trigger": "openURL" },
{ "label": "Ping", "trigger": "terminal" }
]
}
Works with your tools
Apple Calendar
Apple Reminders
Home Assistant
Uptime Kuma
Kopia
UniFi
GitHub Actions
+ any tool with webhooks
Q & A
A native macOS app that pulls every signal from your homelab — Home Assistant, Uptime Kuma, Kopia, UniFi, CI/CD, custom scripts — into one chronological timeline, alongside your calendar and tasks. Each event ships with the actions you'd reach for: SSH, dashboard, terminal command, Apple Shortcut. One place to see what's going on across machines. Tempo shows and proposes; it never acts on its own.
HA is great inside its own world. But your homelab isn't only HA — it's also your NAS backups, monitoring stack, GitHub Actions, network gear, and the calendar/tasks on your Mac. Tempo isn't trying to replace any of those dashboards; it sits on top, surfaces the events that need your attention, and gives you one place to act on them.
Tempo runs an HTTP ingestion server on your Mac, reachable from your local network. Each provider (HA, Uptime Kuma, Kopia, your bash script) gets its own token; every remote ingestion is logged. Optional TLS. The endpoint is LAN-only by default — it never exposes your data to the internet. Anything that can curl can post to Tempo.
Yes — this is the core of Tempo. Every event type has its own action set, defined via the Action Builder: a visual editor, no code required. Actions can open URLs, run terminal commands, execute scripts, or trigger Apple Shortcuts. Use payload tokens — {{host}}, {{ip}}, {{title}} — so each button already knows the context.
Those automate server-side workflows. Tempo centralizes visibility and decision on your Mac. It reads your local calendar, tasks, and reminders (things server-side tools can't touch), puts them alongside infra signals, and lets you decide what to do. They're complementary — Tempo can be the human-facing surface in front of an n8n flow.
No account, no cloud sync, no third-party telemetry. Everything lives in a local SQLite database on your Mac. The HTTP ingestion server is LAN-reachable (so your homelab can post to it) but never exposed to the internet — it accepts only signed requests from per-provider tokens stored in the macOS Keychain. Optional TLS. Optional anonymous usage telemetry, opt-in only.
€49 one-time. All features, all integrations, all updates within the major version. No subscription, no Free/Pro tiers. 15-day trial, fully functional, no account or credit card required.
No — distributed as a signed and notarized DMG (Developer ID), with auto-update via Sparkle. Outside the App Store sandbox so the LAN ingestion server, terminal commands, and AppleScript hooks all work without restrictions.
Yes. Tempo reads from Apple Calendar via EventKit, which natively syncs CalDAV accounts. If a calendar shows up in the Apple Calendar app, it shows up in Tempo.
Private beta is coming. Join the waitlist above for early access — beta testers also get input on which integrations land first.
Roadmap
Now
Private Beta
Timeline UI (agenda + live feed), Apple Calendar & Reminders, LAN-reachable IngestionServer with per-provider tokens, Action Builder, menubar widget. Daily / weekly / monthly views, per-source theming, severity levels.
Next — V1.0
Homelab modules
First-party modules for Home Assistant, Uptime Kuma, Kopia, UniFi, GitHub Actions. System status footer (CPU, memory, network) with extensible providers. Generic webhook templates for everything else.
Later — V1.1+
CLI, more integrations, AI assist
CLI for scripting (push events, query, trigger actions). Google Calendar / Outlook OAuth. Bidirectional sync starting with Apple Reminders. AI Action Builder — describe what you want in plain English (BYO API key). Template gallery.
Roadmap is indicative. Priorities may shift based on beta feedback. Join the waitlist to have a say in what gets built first.
Devlog
2026-04-17
Public site live
Landing online at tempoapp.app. Repository public, Cloudflare Pages deploy pipeline wired up. Tempo itself is in private development; this page is the public face — and the start of the visible trail.
2026-04-13
Domain registered
tempoapp.app secured. Project name and identity locked in: Tempo, as in musical tempo — the rhythm of what's happening across your homelab.