dayfilebeta

Public beta · open source

One log for your scripts, apps and agents.

Each one posts a short line, "Backup finished" or "Deployed v1.8", whenever something happens. See what ran, what changed and what needs attention in one timeline, in the browser, in any feed reader or from your own code. The history stays in order and is never silently rewritten.

Sign in with GitHub See a live example

Beta: free while we build it, up to 50,000 events per log. Expect changes, and keep your own copy of anything important.

What people use it for

A history of your automations

Backups, cron jobs and scripts each post one line when they run. Open your log to see what ran, what didn't, and when.

curl -X POST https://you.dayfile.cloud/events \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title": "Backup finished"}'

A deploy and incident timeline

CI, monitors and people write to the same place, so the order of events is the story. Tag them and filter by deploy or alert.

A feed for your agents and scripts

Give each tool a read-only token and let it check the log: did the backup run, is anything still open? Same history, no extra database.

Notes and to-dos, too

Anything you want to remember goes in the same log. Tag an event todo to track it until you close it.

These are ways to use it, not built-in integrations: anything that can make a web request can post.

How it works

dayfile is one private page of everything that happened, kept in order. Things you care about get written to it automatically. You read it in a browser, a feed reader or your own code.

Write once, then read the same history from different places.

How a log, tokens and feeds fit together Scripts, email, devices and agents add events to your log using a write token, which can only add. The log keeps every event in order. Feeds are saved views of the log. The default feed shows everything and the work feed shows events tagged work; both are read through a read token, by a feed reader and by your own code. The blog feed shows only public events and anyone can read it without a token. scriptemaildeviceagent write token can only add Your logyou.dayfile.cloud Backup finishedDentist moved to ThursdayRenew the domain nowyesterdayappears in 7 d append-only: kept in order, never edited Feeds: saved views of the log Who reads them defaultworkblog everythingevents tagged workpublic events only your feed readeryour own codeanyone on the web read tokenread tokenno token
Anything that can make a web request adds events to your log with a write token, which can only add. A feed is a saved view of the log. A read token opens private feeds for reading only, and a public feed needs no token.

  1. Get your address

    Sign in with GitHub and pick a username. That gives you you.dayfile.cloud, your log.

  2. Make a token for each thing that writes

    A token is a password for one job. A write token can only add events, so you can give one to a script, an automation or a device. A read token can only read.

  3. Send events

    An event is a short note with a title: "Backup finished", "Dentist moved to Thursday". Anything that can make a web request can send one.

  4. Read it where you like

    Open your log here, subscribe in any RSS or Atom feed reader, or fetch it as JSON. Make a feed public to share it without a password.

Your history is an audit trail: events are never edited. A correction, a closed to-do or a retraction is a new event that points back at the old one, so you can always see what changed and when. You can still export your whole log or delete your account from Settings.

See it in two commands

Write

curl -X POST https://you.dayfile.cloud/events \
  -H "Authorization: Bearer $WRITE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title": "Dentist moved to Thursday"}'

Read

curl https://you.dayfile.cloud/feed.json?tag=todo&status=open \
  -H "Authorization: Bearer $READ_TOKEN"

# or subscribe in any RSS or Atom reader:
# https://you.dayfile.cloud/t/<token>/feed.atom

Sign in and create both tokens in a click, under Tokens. A write token can only post; a read token can only read.

Sign in with GitHubSee a live example

Why not just a file, or a monitoring tool?

A log file lives on one machine

Here every machine, script and agent writes to one place, and a feed reader or another tool can read it back with a scoped token.

Monitoring platforms can be more than you need

No agents to install, no query language, no dashboards to build. It is a log and a few feeds, and you can export it as SQLite.

Notes apps aren't built for every tool to write to

dayfile has one simple endpoint that any script, device or agent can post to, and feeds that anything can read back as a timeline.

Not a replacement for alerting

dayfile keeps the history. It does not page you or watch your servers.

Dull on purpose

Scoped tokens

A write token can only post, and only as the sources you name. A read token can only read what its audience labels allow. Only a hash of each token is stored.

Scheduled events

An event can be written now and appear later, or stop appearing after a date.

Plain text first

Every event has a title, so any feed reader can show it.

Quiet site

No analytics, no ads, nothing loaded from other sites. A cookie is set only when you sign in.

Your data, your control

Tokens are passwords

A write token can only post; a read token can only read. If one leaks, revoke it in one click and it stops working at once. A token inside a feed URL gives the same access, so share it like a password.

Private by default

Every event is private to you until you label it public. A public feed shows only events labeled public, and making a feed private again cannot take back copies someone already fetched.

Mistakes

Posted something you shouldn't have? Retract it and it is hidden from dayfile's normal views, but the record stays in your log's history and in your export. Only deleting your account removes it, along with the whole log.

Leave any time

Download your log as a standard SQLite file from Settings, or run the same open-source code yourself.

Start in a minute.

Open source (AGPL-3.0). Self-host it, or use it here for free while it is in beta.

Sign inContact us