Show HN: Dayfile.app – Append-only log for your scripts and agents Gilad launched dayfile.app, an AGPL-licensed, append-only event log for scripts and agents, now in beta with a free tier capped at 50,000 events and 25MB of log size. The service accepts entries via a single HTTP POST with a title and optional tags, offers AI access through an MCP server so an assistant can read, post or close to-dos, and supports self-hosting via `pip install dayfile` with a local SQLite database. Dayfile.app adds a heartbeat feature that creates a to-do event when an expected event, such as a successful nightly backup, fails to arrive within a set period, and closes it when the event reports again. Hi HN, I'm Gilad. dayfile.app is a "git log for scripts and agents", with ordered history, append-only logging as foundational characteristics. The service is currently in beta, AGPL-licensed. As I was looking at various ways to record and retrieve a day's to-dos, automation and operational outputs update successes and failures , the idea of a running event log. dayfile.app's primary use case is DevOps tracking and event logging. Building this, I've emphasized simplifying posting - one HTTP request with a title and optional tags used for filtering when reading the log , AI access via MCP server an assistant can read, post or close to-dos and self-hosting as a first-class citizen pip install dayfile , SQLite database is local in this mode . A demo is available at https://dayfile.app/demo https://dayfile.app/demo . If using the cloud service and after generating a write token on the site, an example of posting an entry would be: curl -X POST https://USERNAME.dayfile.cloud/events \ -H "Authorization: Bearer WRITE TOKEN" \ -H "content-type: application/json" \ -d '{"title":"Nightly backup finished","tags": "backup" }' To read back filtering using tag : curl -H "Authorization: Bearer READ TOKEN" \ "https://USERNAME.dayfile.cloud/events?tag=backup&within=7d" or paste What a local file can't do is notice something didn't happen - this is the heartbeat. dayfile.app can be configured to create an event if no associated event arrives. Imagine a backup which didn't run. A to-do event is created if no evidence of a successful backup shows up within a certain period. When the backup reports again, dayfile closes the associated to-do. Current limits: logs are not end-to-end encrypted, sign-in is via GitHub only, the free beta allows 50,000 events and log size of 25MB. Pricing will be sorted out after this launch and as user feedback rolls in. I'd love to hear in the comments on how you'd use it, what would prevent you from doing so, feature requests and suggestions. Bug reports can be submitted as issues on GitHub. Comments URL: https://news.ycombinator.com/item?id=50561824 https://news.ycombinator.com/item?id=50561824 Points: 2 Comments: 1