Skip to content

SDKs & Packages

import { Card, CardGrid } from ‘@astrojs/starlight/components’;

Start here

Use the HTTP check-in recipes for curl, Python, Node, cron, GitHub Actions, Sidekiq, and agents. That path is finished without installing a language package.

Maintained deep integration

Laravel — schedule attach, queue depth, Horizon freshness [Install →](/installation/) · [Package docs →](/sdks/laravel/)

Language packages

Each package below was installed and run against app.crontinel.com on 2026-11-16. Except for Laravel, they record that a job ran (finished or failed, and how long it took) but send no outcome metrics, so they cannot catch a job that finished but did nothing. For that, send the HTTP check-in receipt with a count.

RuntimePackageStatus
Laravelcrontinel/laravelWorks, including the outcome receipt
Gogithub.com/crontinel/goRecords runs (v0.1.1)
Rubycrontinel gemRecords runs (0.1.1)
Railscrontinel-railsRecords Active Job and Sidekiq runs (0.1.1+)
Rustcrontinel crateRecords runs (0.1.1+)
Node.js@crontinel/nodeNot usable from npm yet; use the HTTP check-in
PythoncrontinelRecords runs (0.2.1+)
PHPcrontinel/phpNo client; use the HTTP check-in
.NET.NETNo package; use the HTTP check-in
CLIcrontinel CLIReads status and alerts (v0.1.1)

Which path to pick

Your job runs inUse
Laravel (schedule, queues, Horizon)The Laravel package, which also sends the HTTP receipt
Node, Python, Ruby, Sidekiq, Celery, GitHub Actions, plain cronAn HTTP check-in recipe
Anything else that can make an HTTP requestThe same receipt: POST /api/v1/ingest/cron with your ingest key

Whichever you choose, register the job and its schedule so a run that never starts raises an alert, and send a start receipt if you also want to catch a run that never finishes.

For plan limits on ingest volume, see billing and plans.