Liloopy
Liloopy starts with a simple but important distinction: a routine defines what should happen, while an execution preserves what happened at a specific date and time.
Tell us what you want to organize01 /
A recurring task is more than a reminder
Recurring tasks often end up as scattered reminders. That helps remember that something exists, but it does not always show what was pending, what was completed, or how the routine behaved over time.
Liloopy separates the routine definition from each execution. This creates a useful history and treats every occurrence as part of a process rather than as a note that disappears after completion.
02 /
The core works without a server
An integrated scheduler creates and expires executions, while reconciliation checks the state when the application starts. Data stays in local SQLite, and migrations keep the database aligned as the application evolves.
The result is an application that does not depend on an account, a backend, or a permanent connection. The history stays on the machine and remains available to understand what actually happened.
03 /
An application that steps aside when you do not need it
Liloopy can remain in the system tray while its work continues in the background. Closing the window does not stop the process: the application can be reopened from the tray and notify the user when needed.
The intention is to make routines part of the day without turning them into another window to manage.
04 / next step
Do you have a process that should work for you?
Tell us what repeats, what gets lost along the way, and what a tool would need to preserve.
Talk through your routine