
Vim
Sublime Text
VS Code
GNU Emacs
Microsoft Visual Studio
Notepad++
Netbeans
IntelliJ IDEA
RunWisp
Cron
Supervisor
Cronitor
PM2
Jobber
Cron As A Service
Cron Jobs Monitoring by Upzilla
RunWisp is an open-source cron replacement and process supervisor in a single binary. It runs your scheduled jobs, keeps your long-running services alive, records every run, and makes noise the moment something breaks. One tool does the work of both crond and supervisord, and unlike either of them, you can actually see what it's doing.
Most servers still run jobs the old way. Cron fires a task and tells you nothing (no history, no exit codes, no alert when a job fails or a scheduled run never happens), so a broken job can sit silently for days. RunWisp closes that gap. Every run is captured with its exit code, duration, and output, and you get alerted on both failed and missed runs.
Why teams choose it:
runwisp.toml that you commit to git and review like any other change.runwisp import brings an existing crontab or supervisord config over automatically.Built for developers, DevOps teams, and self-hosters who want dependable scheduling and supervision with real visibility, without adopting a heavyweight orchestration platform. Apache-2.0 licensed, and it runs on Linux and macOS.
RunWispVim is recommended for programmers, developers, and system administrators who require a highly efficient and customizable text editing experience. It is especially useful for those who work extensively in terminal environments or need a quick, resource-light text editor for remote systems.
No RunWisp videos yet. You could help us improve this page by suggesting one.
RunWisp's answer:
Almost everything is written in Go, except for Web UI where we use Svelte with TypeScript.
RunWisp's answer:
It's the rare infrastructure tool that's actually a pleasure to run:
runwisp import cron / import supervisord to bring your existing setup over automatically.RunWisp's answer:
The monitoring tools (Cronitor, Healthchecks, Dead Man's Snitch) only watch - they wait for a ping and tell you it didn't come, but they never run or restart anything. The execution platforms (Rundeck, Windmill, Dagu) run jobs but pull you into a heavyweight control plane, enterprise-gated team features, or a DAG/workflow model that's overkill for what most servers actually need. And nearly all of them are per-server SaaS with a recurring bill and your job data living on someone else's servers.
RunWisp is the tool that both runs and watches, self-hosted, in one ~25 MB binary you install in minutes. Full per-run history and failed/missed-run alerts, a genuinely good web dashboard and terminal UI out of the box, no external dependencies, no monthly invoice, no data leaving your infrastructure. It does the two jobs most servers need - scheduling and supervision - and makes them effortless to run and easy to see, without asking you to adopt a platform.
RunWisp's answer:
Two groups.
First, developers and DevOps teams who want their scheduled jobs and services defined as code: the entire setup lives in a single runwisp.toml that goes straight into your git repo, so a change to a cron job is a reviewable commit, not an undocumented edit on some server. It gives developers and ops a shared, versioned source of truth for what runs where and makes handoffs and audits painless.
Second, self-hosters and homelab operators (like the Raspberry Pi and home-server crowd) who want real visibility into their scheduled jobs without running heavyweight infrastructure. One tiny binary, ~25 MB of RAM, no external database or runtime, and a clean web dashboard to see everything at a glance.
RunWisp's answer:
RunWisp started with a problem its founder ran into twice. At two different companies, he needed a way to let developers see whether their scheduled jobs had actually run (browse the history, read the output, and trigger a job themselves when needed) without handing everyone an SSH login to a production server. Giving out shell access just to check on a cron job invites mistakes; the alternative was leaving developers flying blind.
No existing tool handled it cleanly, so he built the internal dashboard he wanted: every job, its full run history and output, and a one-click trigger (no server credentials required). When the same need came up again at the next company, it was clear this shouldn't have to be rebuilt everywhere. RunWisp is that tool, productized: a single binary that schedules and supervises your jobs and gives the people who need it a clear, safe view of what's running, without a shell account on the box.
Based on our record, Vim seems to be more popular. It has been mentiond 10 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Lua is quite small, encouraging distros to include it. The ubuntu gvim has, and the gvim AppImage linked from vim.org does. The default Makefile from github is set up to not include it, but you can uncomment one line there to get it. Source: over 3 years ago
I've not used vimwiki locally (tho I'm old enough to remember the Vim wiki on vim.org :), but I think what you are wanting to do is extend vimwiki's syntax file. I presume it installs one at $VIMRUNTIM/syntax or or ~/.vim/syntax. If this sounds right, then create a ~/.vim/after/syntax/vimwiki.vim file and place your match command in there. Then everytime you open a vimwiki file it should apply your... Source: over 3 years ago
Vim.org has 242k total visitors, tailwindcss.com has 4.4m, planetscale.com has 412k, jpl.nasa.gov has 2.6m, all built with Tailwind, all several years younger than Vim's website. Unnecessary comparison, unnecessary defence. It's a valuable tool, fine, but a complete disregard for anyone who doesn't love a crappy website and would like to navigate a website like a normal human is not something to be defended. Maybe... Source: almost 4 years ago
I write in Vim with some customizations in my vimrc to gear it more towards prose writing than code editing. It's not pretty, but Normal Mode and Ex commands are the most powerful text editing tools out there, so that means I spend less time on making corrections and other edits. Source: over 4 years ago
If you are open minded and would like to try it out, click me for more information! Cheers. - Source: dev.to / over 4 years ago
Sublime Text - Sublime Text is a sophisticated text editor for code, html and prose - any kind of text file. You'll love the slick user interface and extraordinary features. Fully customizable with macros, and syntax highlighting for most major languages.
Cron - Cron Calendar.
VS Code - Build and debug modern web and cloud applications, by Microsoft
Supervisor - Supervisor is a client/server system that allows its users to monitor and control a number of...
GNU Emacs - GNU Emacs is an extensible, customizable text editorโand more.
Cronitor - Monitor cron jobs, micro-services, daemons and almost anything else, no setup required. Easier cron troubleshooting and no more silent failures.