Automate your whole business operations.
Cronable runs AI agents, scripts and pipelines on a schedule — on infrastructure you control. Replace your scattered cron jobs with one visual, git-versioned engine that ships work while you sleep.
Commercial license · Installed on your infrastructure · Support & training included
Replace scattered cron jobs
Retire the tangle of crontabs, launchd plists and one-off scripts. Every scheduled job lives in one versioned, visible place.
Put AI agents to work
Run Claude and other models headlessly on a schedule — analyzing, writing, coding and deciding while you sleep.
Chain everything into pipelines
Run the next job only when the previous one succeeds, pass data downstream, and catch failures with dedicated error jobs.
Run Claude headlessly on your own infrastructure
Point a job at a repo and a prompt. Cronable runs Claude headlessly through the Claude Code CLI on the same server — hands-off and fully automated, authenticated with your own Anthropic API key. Your code, prompts and output never leave your box.
- Claude runs locally via the CLI — hands-off, fully automated
- Runs under your own Anthropic API key — your account, your control
- Choose from several AI providers and models per job
- Chain an agent’s output straight into the next step
# jobs/reports/daily-seo.yaml
id: daily-seo
group: reports
type: claude
cwd: ~/sites/example.com
schedule:
- kind: daily
time: "07:30"
instructions: |
Audit example.com for SEO regressions since
yesterday. Email me the 5 highest-impact fixes.
model: claude-opus-4-8
onFailure: alert-oncallOne agent, running every morning, hands-off on your own server.
Eighteen job types — and room for your own
Actions do the work, orchestration nodes pause and branch the chain, and triggers fire whole pipelines from an inbox, a folder, a calendar or a webhook. Need something bespoke? Ship it as an extension.
Actions
12 typesDo the work when they fire — and hand their output straight to the next job in the chain.
AI agent
Run Claude and other models headlessly in a repo — analyze, write, refactor, decide.
Terminal
Execute any shell command or script, with secrets injected and output captured.
HTTP
Call any API — GET through DELETE, auth from a stored credential — and chain the JSON response.
Send notifications and reports over SMTP or SendGrid when jobs succeed or fail.
Code
Transform data with sandboxed JavaScript — reshape a parent’s output on the fly.
Git
Pull, commit and push repositories on a schedule using the machine’s own credentials.
Database
Run SQL against Postgres, MySQL or SQL Server — rows flow downstream as JSON.
Slack
Post a message to a Slack channel — the last mile of most chains.
SMS
Send a text via Twilio — reminders, alerts and waitlist blasts that actually get read.
File transfer
Move files between your box, SFTP and S3 — upload, download or list, then chain on the result.
Google Sheets
Append to or read a Google Sheet — reports land where the team already works.
Calendar
List upcoming Google Calendar events or create them straight from a chain.
Orchestration
2 typesShape the chain itself — park it for hours or days, or route it down exactly one branch.
Wait
Pause a chain for minutes or days — durably. Survives restarts and holds no capacity while parked.
Switch
Route by any value — children attach per branch and only the matching one fires.
Triggers
4 typesPipeline roots fired by their own source. Every polled trigger reaches out from your box — no inbound ports, no public URLs.
Webhook
Accept inbound triggers from CI, forms or external systems — token-guarded, rotatable in a click.
Folder watch
Fires when a file lands in a watched directory — a dropped CSV kicks off the whole pipeline.
Inbox
Fires on new mail in an IMAP mailbox — the message flows straight into the chain.
Calendar watch
Fires ahead of an upcoming Google Calendar event — prep and reminders, exactly on time.
Custom — bring your own
Build your own job types as self-contained extensions — one folder, installed in a click.
Put the repetitive work on autopilot
A few of the things teams run on Cronable every day. If you do it on a schedule, it can run here.
Daily social media analysis
Every morning an AI agent reviews yesterday’s Instagram, TikTok and LinkedIn performance and posts the wins, drops and next moves to Slack.
Daily SEO analysis
Track rankings, crawl your site for regressions and land a prioritized fix list in your inbox before standup.
Weekly campaign & post ideas
An agent proposes next week’s social calendar and drafts the posts, ready for you to approve in one place.
Find leads and reach them
Discover fresh leads matching your ICP, enrich them, then email them or drop them into Google Sheets — automatically.
Morning inbox summary
Summarize your overnight email and send the digest to Slack before you sit down at your desk.
Ship a feature every day or week
Point an AI agent at a repo and a backlog — it implements, commits to a branch and opens a pull request on a schedule.
Find security holes daily
Nightly, an agent audits your codebase and dependencies for vulnerabilities and files exactly what it finds.
Analyze your service health
Ping your services, analyze the responses with AI and alert you only when something actually looks wrong.
From idea to running job in minutes
Define jobs as code
Write a small YAML file per job — or just ask your AI assistant to create one. Jobs live in your own git repository, the single source of truth.
Cronable syncs from git
Push a new job and the engine pulls it automatically. Edit in the browser and changes commit straight back. Two-way, no restarts.
Schedule, chain or trigger
Fire on an hourly, daily, weekly or monthly schedule, chain off a parent job’s outcome, or trigger from a webhook, an inbox, a dropped file or an upcoming calendar event.
Watch it run live
Follow every run on the draggable DAG with streaming logs and full history — and get emailed the moment something fails.
Synced with your git repo
Jobs live in a git repository you own. Push a change and Cronable pulls it; edit in the browser and it commits back. Two-way, automatic, no restarts.
Create jobs from your AI chat
A bundled skill lets your AI assistant author a valid job straight into git — then the system pulls it in and it just starts running.
See everything. Chain anything. Group it your way.
Watch every run on a live, draggable DAG with streaming logs and full history. Draw an edge to run a job after another succeeds — or fails, or takes a switch branch — so alerts wire themselves. Organize work into folders — perfect when you manage many projects or clients.
packages/extensions/src/job-types/
slack-post/
manifest.ts # fields, validation, UI
executor.ts # what the job actually does
# Install it from Settings → Extensions.Extend it to fit your stack
Every job type is a self-contained extension — one folder with a manifest and an executor. Build your own, or have us build them for you, and install them from the UI in a click. The editor form, icons and validation all come along for free.
Your infrastructure. Your data. Your keys.
Cronable is built to run like a trusted part of your own stack — nothing phones home.
Runs on-premises
Install on your own server or VM. No SaaS, no cloud dependency, no telemetry.
Encrypted secrets
AES-256-GCM at rest, never written to git, and masked out of every log line.
Authenticated console
Per-user logins or OIDC single sign-on, with brute-force lockout; the engine binds to localhost.
You hold the keys
Your data and encryption keys stay with you. Every change lands in git and an audit trail.
Built for the way you work
Corporations
Run it entirely on-premises, behind your firewall.
- Group work by team, client or project in folders
- Encrypted secrets, audited job history in git
- One authenticated console for the whole ops team
Growing companies
Automate the busywork you’d otherwise hire for.
- Reports, reconciliations, outreach and monitoring
- No new SaaS subscriptions or extra headcount
- Chain multi-step processes end to end
Solo devs & founders
Ship something every single day.
- AI agents that analyze, build and report overnight
- Runs on one small server you already pay for
- Create jobs by chatting with your AI assistant
We install it, train your team, and support it
Cronable is a commercial product we deploy on your premises — then make sure your people can actually run it. Pricing is scoped to your team and environment.
Installation on your infrastructure
We deploy and configure Cronable on your server or VM under systemd — no cloud, no lock-in.
Secrets & integrations setup
Encryption keys, AI providers, email and git sync configured and verified with your team.
Operator training
We teach your team to build, schedule, chain and monitor jobs so you can run it confidently.
Support & updates
Ongoing support and product updates included for the term of your agreement.
Frequently asked
Is it really self-hosted?
Yes. Cronable installs on your own server or VM. Nothing runs in our cloud, there is no telemetry, and your data, secrets and job history never leave your infrastructure.
How does Cronable access AI models?
Cronable runs Claude headlessly through the Claude Code CLI on your own server, authenticated with your own Anthropic API key (or a supported cloud provider such as Amazon Bedrock or Google Vertex). You bring your own AI account, so usage bills directly to you with no markup, and nothing is routed through us.
Which AI providers are supported?
Cronable can call several AI providers, so you can pick the right model for each job and avoid vendor lock-in.
How do we create jobs?
Two ways: the visual drag-and-drop DAG editor in the browser, or by asking your AI chat assistant — a bundled skill writes a valid job into your git repository and Cronable picks it up automatically.
Can jobs react to events, not just schedules?
Yes. Four trigger types start pipelines from their own source: an inbound webhook, a file landing in a watched folder, new mail in an IMAP inbox, or an upcoming calendar event. Apart from the webhook, every trigger polls outward from your server — so no inbound ports or public URLs are required.
How are secrets and access handled?
Secrets and typed credentials (API keys, bearer/basic/header auth, database connection strings) are AES-256-GCM encrypted at rest, never written to git and masked from logs. The web UI is authenticated with per-user logins — or your identity provider via OIDC single sign-on — with brute-force lockout, and every login, secret change and settings edit lands in an append-only audit trail. The engine binds to localhost and runs as a dedicated low-privilege user.
Can we build our own job types?
Yes. Extensions are self-contained modules — one folder each — so your team, or ours, can add custom job types that behave exactly like the built-ins.
Can it query our database?
Yes. The database job type runs SQL against Postgres, MySQL or SQL Server using a stored connection-string credential, with proper bind parameters and row limits. Results flow downstream as JSON, so a query can feed an AI summary, a report email or any other job in the chain.
How is it priced?
Cronable is a commercial, per-install license. Pricing depends on your team size, environment and support level, so we quote per engagement. Request a quote and we’ll reply within one business day.
Do you help us install and run it?
Every license includes installation on your infrastructure, onboarding and training so your team can operate it confidently. Ongoing support and updates are included per your agreement.
Automate your operations.
Tell us what your team runs every day. We’ll show you how Cronable does it for you — and put together a quote for your setup.
Contact Cronable for commercial pricing at sales@cronable.ai.