Quick Start
Choose your stack below and follow the steps. Every quickstart follows the same flow:
| Package | What you’ll do | Time |
|---|---|---|
| CLI / Docker → | brew install → first ping | ~2 min |
| Laravel → | composer require → artisan install → first cron run | ~3 min |
| Node.js / TypeScript → | npm install → npx tsx quickstart.ts | ~3 min |
| Python → | pip install → python quickstart.py | ~3 min |
| Go → | go get → go run quickstart.go | ~3 min |
| Rust → | cargo add → cargo run | ~3 min |
| PHP → | composer require → php quickstart.php | ~3 min |
| Ruby → | gem install → ruby quickstart.rb | ~3 min |
| Ruby on Rails → | bundle install → auto-instrument | ~3 min |
| .NET → | dotnet add package → dotnet run | ~3 min |
Before you start
- Sign up at app.crontinel.com (free tier included).
- Create an app from the dashboard — give it a name (e.g. “my-first-app”).
- Copy your API key (
crn_live_...) from the app settings page.
That’s it — on to your package.
Verify it works
After following your package’s quickstart:
- Go to app.crontinel.com → Apps → select your app
- Check the Cron, Queue, or Events sections — data should appear within 30 seconds.
- If you see your job run with exit codes and duration, you’re all set.
No data yet? Make sure CRONTINEL_API_KEY is set in the environment where your code runs, and that your app can reach https://app.crontinel.com (no firewall blocking).
Next steps
- Set up alerts to get notified when a job fails
- Learn about monitors for deeper insight
- Connect your self-hosted instance to the SaaS