Your servers. Our scheduler.
Job orchestration you actually own
Schedule scripts and commands, run them on computers you control, and know the moment something breaks - with dependency chains, auto-retries, and failure alerts. The agent only dials out; there are no inbound ports to open.
free to start · no credit card · 2 agents included
What it does
Everything a pile of cron jobs can't
If you can run it from a command line, ThinkTorch can schedule it, chain it, retry it, and tell you when it breaks.
Real scheduling
By the minute, hour, day, or a full cron expression - with the next run time shown for every job.
Your own servers
Jobs run on hardware you control, against your own files, via a small outbound-only agent. ThinkTorch receives each job's command and its output.
Chains & retries
Trigger jobs on success or failure, auto-retry the flaky ones, and stop runaway runs with a timeout.
Know it broke
A live view of failures and activity, plus an email the moment a job breaks.
Where it fits
Past a pile of cron jobs, nowhere near Control-M
| Cron / Task Scheduler | Enterprise (Control-M, Rundeck) | ThinkTorch | |
|---|---|---|---|
| Setup | Per-server, by hand | Weeks, often a consultant | Install an agent, done |
| Failure alerts | None | Yes | Email the moment a job fails |
| Retries & timeouts | DIY scripting | Yes | Built in, per job |
| Job dependencies | Cron can't | Yes | Chain on success or failure |
| History & logs | Scattered or none | Yes | Every run, in one place |
| Runs on your servers | Yes | Usually their infra | Yes - agent is outbound-only |
| Price | Free | $$$$ + procurement | Free to start, from $19/mo |
Getting started
Up and running in three steps
Connect an agent
Run a tiny program on any computer you own. It reaches out to us - no inbound ports to open.
Create a job
Define the command to run, a schedule if you want one, and how many times to retry on failure.
Watch it run
Follow live status and logs, see failures at a glance, and get emailed if something breaks.
Use cases
What can you do with it?
If you can run it from a command line, ThinkTorch can schedule it, chain it, retry it, and tell you when it breaks. A few things teams use it for.
Backups you can trust
Back up databases or files on a nightly cron - and get emailed the moment one fails, instead of finding out when you need the backup.
Pipelines that wait their turn
Chain extract → transform → load. Each step runs only when the previous one succeeds; if one fails, the chain stops and you're told.
Uptime & health checks
Ping a URL or service every few minutes. If it doesn't come back healthy, the run fails and an alert lands in your inbox.
Scheduled reports
Generate and send reports on a schedule, and auto-retry the flaky steps so a momentary blip doesn't skip a day.
Housekeeping at scale
Rotate logs and clear temp files across every server you run an agent on - one schedule, all your servers.
Glue between systems
Trigger a deploy, refresh a cache, or ping a chat channel via webhook the moment an upstream job finishes.
Where it runs
Runs on your servers
The agent runs wherever your jobs need to run, against your own files. ThinkTorch receives each job's command and its output.
Pricing
Simple, honest pricing
Start free, upgrade when you outgrow it. Every plan has every feature - you only pay for scale.
- 2 agents
- 1 environments
- 5 jobs
- 2 seats
- Shortest schedule: every 10 minutes
- Log history: 7 days
- 5 agents
- 2 environments
- 20 jobs
- 3 seats
- Shortest schedule: every 5 minutes
- Log history: 30 days
- 15 agents
- 5 environments
- 100 jobs
- 10 seats
- Shortest schedule: every minute
- Log history: 90 days
- 40 agents
- Unlimited environments
- Unlimited jobs
- 30 seats
- Shortest schedule: every minute
- Log history: 1 year
- Unlimited agents
- Unlimited environments
- Unlimited jobs
- Unlimited seats
- Shortest schedule: every minute
- Log history: Unlimited
Prices in USD. Every plan includes every feature - cancel anytime.
FAQ
Questions, answered
Do I have to open any firewall ports?
No. The agent only makes outbound connections to ThinkTorch and asks for work, so there's nothing inbound to expose.
Where do my jobs actually run?
On computers you own, via the agent you install: the job runs there, against your own files. ThinkTorch stores the schedule, the status, each job's command, and the output the agent sends back, and keeps that output for your plan's log-history window after the run finishes (Free 7 days, Starter 30 days, Team 90 days, Business 1 year, Enterprise unlimited), then deletes it.
What can a job be?
Anything you can launch from a command line: a PowerShell or Python script, a batch file, or any executable, with the arguments you give it.
What happens when a job fails?
It can auto-retry a number of times you set, it emails your notifications address, and it shows on the Attention page with a link straight to the log.
Is there really a free plan?
Yes - free forever, no credit card. You only move to a paid plan when you need more agents, environments, jobs or seats, or schedules that run more often. Every plan has every feature.
Can my whole team use it?
Yes. Invite teammates and give each a role per environment (Viewer, Operator, Editor, Admin). It's one workspace and one bill, and your plan caps how many people can run or change things; Viewers are free and unlimited. Seats per plan: Free 2, Starter 3, Team 10, Business 30, Enterprise unlimited.
Which operating systems are supported?
The agent runs on Windows today. It executes whatever commands you'd normally run there - cmd, PowerShell, Python, and so on.
Can I cancel anytime?
Yes, from the Billing page. Downgrading or canceling never deletes anything you've already created.
Create a workspace in under a minute
Free forever, no card. Every plan has every feature - you only pay for scale.