Scheduled jobs & cron on a VPS
Replace a tangle of cron scripts with versioned, observable workflows that fit on a small VPS — no cluster required.
The problem
Cron scripts drift: no versioning, no retries, no visibility into why last night’s job failed. Moving them to a hosted automation platform adds cost and a Node stack you have to operate.
How m9m does it
m9m gives you cron and webhook triggers, HTTP and database nodes, retries, Git-based versioning, audit logs, and Prometheus metrics — all in one binary you can drop on a small VPS. Enterprise-grade observability without an enterprise tier.
How it works, step by step
- 1
Build the workflow
Chain a Cron trigger into HTTP Request, a Postgres node, and a Slack notification — or import an existing job.
- 2
Add retries and alerts
Set per-node retry policies and route failures to Slack, Discord, or email.
- 3
Observe it
Scrape Prometheus metrics and read the audit log to see exactly what ran and when.
Nodes involved
Keep reading
Need help shipping agents or migrating off n8n?
Neul Labs — the team behind m9m — takes on a limited number of consulting engagements each quarter. We help teams migrate n8n workflows, build custom Go nodes, sandbox AI agents in production, and design automation platforms that don't collapse under load.