😵 The reality

🔥 The real problems

1. No control over running jobs

2. No execution limits

3. Overlapping runs

4. No central visibility

5. No maintenance awareness

⚡ What I actually needed

🧰 So I built this

🔍 What it actually adds

✅ Job management

⏱ Execution limits

🚫 Singleton mode

🛑 Kill running jobs

🛠 Maintenance windows

🏷 Tags & grouping

📊 Monitoring

🌍 Multi-host support

🔐 Authentication

💡 Final thought

💬 Curious Writing a cron job takes 30 seconds. Running cron jobs reliably in production?

That’s where things start to break. Once you have more than a handful of jobs, things get messy: Cron itself doesn’t solve any of this. If something gets stuck, you’re SSH-ing into servers and killing processes manually. A job that should run for 2 minutes might run forever. If a job takes longer than its interval:→ multiple instances pile up Multiple servers = multiple crontabs = chaos Deployments happen, jobs keep running → failures & noisy alerts 👉 I didn’t want a SaaS.👉 I wanted something I fully control. 👉 https://cronmanager.meinetechnikwelt.rocks/👉 https://github.com/csoscd/cronmanager A lightweight cron job manager that sits on top of cron and adds the missing pieces. No vendor lock-in. No external dependencies. Not just a crontab file anymore. But in production, you don’t just need scheduling. How are you managing cron jobs today? Templates let you quickly answer FAQs or store snippets for re-use. as well , this person and/or - jobs run twice- jobs hang forever- jobs silently fail- jobs behave differently across servers- nobody knows what’s actually running - real control over job execution- visibility into what’s running- protection against overlapping runs- the ability to stop jobs instantly- multi-host execution- proper monitoring - fully open source- free to use- runs on your own infrastructure- Docker-native → up and running in minutes - working directory- descriptions & tags - set max runtime per job- get alerts (email / Telegram)- automatically kill jobs (local or via SSH) - prevents overlapping runs- skips new executions while one is still running - stop jobs directly from the UI- no SSH needed - pause jobs during deployments- avoid unnecessary alerts - organize jobs- filter and manage large setups easily - success rate- avg / min / max runtime- visual charts over time - run jobs across multiple servers- execute via SSH in parallel - OIDC / OAuth2 support- role-based access (Admin / Viewer) - plain crontab?- custom scripts?- something heavier like Airflow?