Job scheduling for Windows servers

Outgrown Task Scheduler? You don't need Control-M.

ThinkTorch runs your scripts on your own Windows servers, on schedules and in chains. No ports to open: the agent only dials out. When a job fails at 2 AM, the email tells you why, and you rerun it from the run page.

Free forever · no card · 2 agents included

Subject [Prod] Nightly DB backup failed, exit code 1

Runs Nightly DB backup

Failed

Nightly DB backup

  • Prod
  • 2 m 0 s
  • exit 1
Fault

Failed with exit code 1 at 02:02

Backup failed: not enough space on D: (needed 42 GB, free 3 GB).
Rerun Open job
02:00:01 Starting full backup of NorthwindERP on SQL01.
02:00:09 Checkpoint written; snapshot taken.
02:00:10 Writing D:\Backups\northwind-full.bak (42.0 GB).
02:01:58 Write stopped after 3 GB: the device is out of space.
02:02:00 Backup failed: not enough space on D: (needed 42 GB, free 3 GB).

Other recent runs

  • Succeeded 07:41 · 2 m 4 s
  • Succeeded 02:00 · 1 m 58 s
  • Succeeded 02:00 · 2 m 3 s
Example: a failed run in a demo workspace, and the email it sent.

What runs, and when?

Anything you can start from a command line: a script, a program, a file transfer. On a schedule in plain words, after another job finishes, when a file lands in a folder on an agent's computer, or when a webhook is called. Retries are set per job, and an optional workspace time limit stops a runaway run.

  • Backups
  • ETL chains
  • Health checks
  • Reports
  • Housekeeping
Last run Name Schedule Runs after
Succeeded Nightly DB backup Daily 02:00 UTC
Succeeded Archive backup to NAS File transfer Not scheduled Nightly DB backup, on success
Running Hourly sales report export 5 * * * *
Succeeded Sync price list Every 6h

Flow Nightly DB backup on success Archive backup to NAS

File watch prod-app-01 · D:\incoming\prices · *.csv one run per file

Example jobs in a demo workspace.

Where does it run, and who can touch it?

On your own computers. Each one runs a small agent that dials out to ThinkTorch and asks for work, so there are no inbound ports to open. The job runs there, against your own files; ThinkTorch keeps the schedule, the status, the command and its output.

Environments are a wall. A Prod job is never claimed by a Staging agent, even with matching tags, and only an Admin can mint the key that puts an agent in Prod. Access is set per environment: Viewer, Operator, Editor or Admin.

Changes to jobs, runs, agents, environments, roles, keys and invites are recorded, along with attempts that were refused: who, what, where and when, in an audit log per workspace.

File transfers of a folder or a pattern need a Windows agent.

Prod

Nightly DB backup needs db

  • prod-db-01 windows,db claims it
  • prod-app-01 windows,app

Staging

  • stg-db-01 windows,db never: other environment
  • stg-app-01 windows,app
  • Viewer
  • Operator
  • Editor
  • Admin
Example environments in a demo workspace.
When09:14
Whosam@northwind.test
Actionjob.updated
SubjectNightly DB backup
EnvironmentProd
What happenedTried to edit job 'Nightly DB backup' without the Editor role.
OutcomeRefused
Example: an audit log entry in a demo workspace.

What happens when it breaks?

The failure finds you, says why, and is one click from fixed.

  1. It lights up.

    Attention Failed 1

    Failed Nightly DB backup

  2. You get an email.

    Subject [Prod] Nightly DB backup failed, exit code 1

    To ops@northwind.test

    Sent to the notifications address you set, once any retries are used up.

  3. It says why.

    Fault

    Failed with exit code 1 at 02:02

    Backup failed: not enough space on D: (needed 42 GB, free 3 GB).
    02:00:00 Connecting to SQL01 as svc_backup (password ***).

    Search the log, follow it live, download it.

  4. You rerun it.

    Rerun

    Rerun in one click, or let auto-retry go first. An optional workspace time limit stops a runaway run, and a run whose agent dies is marked Failed instead of hanging.

Example: one failure, from lamp to rerun, in a demo workspace.
  • Predictable One run, one agent. Each run is claimed by exactly one agent, atomically, and a Prod job never runs outside Prod.
  • Secrets Secrets are encrypted at rest and masked as *** in run logs.

Past Task Scheduler, nowhere near Control-M

ThinkTorch Task Scheduler Enterprise (Control-M, AutoSys)
Setup Install an agent, done Per server, task by task Weeks, often a consultant
Failure alerts An email when a run fails for good None built in Yes
Retries & timeouts Retries per job, and a workspace time limit Restart and time-limit settings per task Yes
Job dependencies Chain on success or failure Not built in Yes
History & logs Every run, in one place Per server, if history is on; no output Yes
Audit trail Changes and refused attempts Change events per server, if history is on Yes
Secrets in logs Encrypted, masked as *** Unmasked, wherever your script logs Yes
Runs on your servers Yes - agent is outbound-only Yes Yes, installed by you
Price Free to start, from $19/mo Included with Windows $$$$ + procurement

Simple, honest pricing

Start free, upgrade when you outgrow it. Every plan has every feature - you only pay for scale.

Free
$0
Kick the tires - every feature, capped resources.
  • 2 agents
  • 1 environments
  • 5 jobs
  • 2 seats
  • Shortest schedule: every 10 minutes
  • Log history: 7 days
Start free
Starter
$19 /mo
or $190/yr - 2 months free
For a solo operator or a tiny setup.
  • 5 agents
  • 2 environments
  • 20 jobs
  • 3 seats
  • Shortest schedule: every 5 minutes
  • Log history: 30 days
Get Starter
Business
$149 /mo
or $1490/yr - 2 months free
For orgs that need room to grow.
  • 40 agents
  • Unlimited environments
  • Unlimited jobs
  • 30 seats
  • Shortest schedule: every minute
  • Log history: 1 year
Get Business
Enterprise
Custom
For large fleets: no caps, custom terms and a direct line to us.
  • 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.

Questions, answered

Something not covered here? The Help guide explains agents, jobs, schedules, alerts and security in full.

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 retries first, if you set retries. If the last attempt fails too, it emails the notifications address you set and 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. 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.

Install an agent. Create a job. Watch it run.

Free forever, no card. Every plan has every feature; you only pay for scale.