RunWisp · Self-hosted cron and supervisor that records every run.
runwisp.com
The open-source cron replacement and process supervisor with a built-in web dashboard. One binary, one TOML file, zero runtime dependencies.

I created a tool that’s easy to set up and gives you fast and beautiful web UI and TUI from a single Go binary.

It can serve both as a cron replacement, or just as a cron supplement - let’s say, to version control your cron tasks in a small team. It also has an alert system that allows you to send slack/discord/telegram/email when something bad happens.

I want your feedback. You can help me shape this product into something people will find pleasant to use.

This daemon is copyleft GPL-3.0-or-later - completely free to use.

RunWisp is currently in pre-release phase but is slowly approaching its v1.0 stable release.

Website: https://runwisp.com/

GitHub repo: https://github.com/runwisp/runwisp - feel free to open an issue!

Quick start: https://docs.runwisp.com/getting-started/quick-start/

AI Disclosure

  • Design - Hint
  • Implementation - Pair
  • Testing - Assisted
  • Documentation - Pair
  • Review - Hint
  • [object Object]@lemmy.caEnglish
    5·
    18 hours ago

    I hope this doesn’t come off as too harsh, but the text reads as very AI generated, and I think if you rewrote the main text you could do a much better job.

    It’s not clear to me why to use it, the pitch today is that it makes failures loud, which is nice, but very poorly described.

    The tool itself looks good, but the website looks very “Claude”, especially the text at the top saying “ONE BINARY · LINUX · MACOS · WSL · 25 MB RAM IDLE”

    Those are great pros, but are they the guest thing the user should see?

    Honestly the first paragraph of the quick start is a much better pitch:

    RunWisp is one small Go binary. You list the shell commands you want to run in a runwisp.toml, and RunWisp takes care of the rest — firing jobs on cron, restarting services when they crash, and capturing every line of stdout and stderr so you can go back and look at what happened. There’s a TUI in your terminal and a Web UI in your browser for poking around. No external database, no agent, no sidecar

    This tool looks decent, but for me I find nix helps manage the complexity of systemd well

    • runwisp_com@lemmy.worldOPEnglish
      43·
      18 hours ago

      actually not harsh

      this is exactly the kind of concrete feedback I was hoping for. You’re right that the quick-start paragraph explains the actual value better than the current pitch… I should lead with that, then treat the binary size and platform support as supporting details rather than the headline.

      Thank you for taking the time to look at this.

      • [object Object]@lemmy.caEnglish
        8·
        18 hours ago

        No problem.

        The other thing with AI stuff is it conveys very little trust. It’s easy-come easy-go, so it’s hard to tell how much maintenance the owner will has put in or will put into the project.

        Scheduling is high risk, so it’s important that it feels safe