To add on to what Josh said, using Airplane for scheduling gets you a number of benefits over cron:

- Serverless - no need to maintain a cron server or worry about where the job is running

- Notifications - get notified in Slack or email if a failure happens

- Logging - we'll record every run, what happened, etc

- There are also a bunch of convenience features as well, e.g. having a native SQL integration so if you just want to run e.g. a query on a schedule, you can do so in minutes of work.

cron is a popular starting point on Airplane! We see our users creating tasks that are semi automated, but then adding manual tasks later (but then automating those tasks as well). The nice property of Airplane is that it's very composeable and extensible over time.