Atelier — One Moment, Perfectly Timed

Capabilities

Every feature, crafted
for a single perfect moment

Atelier ships with a refined suite of scheduling primitives. Each one designed from first principles to unlock deferred execution at exactly the right time.

⏰

Temporal Expressions™

Schedule with natural precision — noon, midnight, teatime, or any HH:MM expression. Our parser understands human time, not just machine time.

📋

File-Driven Orchestration

Feed entire execution scripts with -f flag support. Compose complex workflows in a file, hand them to Atelier, and walk away. It ships when you say so.

📬

Completion Signals

Never wonder if your job ran. The -m notification engine delivers confirmation the moment execution completes. Zero ambiguity. Maximum peace of mind.

🔮

Relative Time Engine

Think in deltas, not absolutes. Express intent as now + 30 minutes, now + 2 hours, or now + 3 days. Atelier resolves the math so you can focus on outcomes.

📊

Queue Intelligence

Organize pending work across 26 named queues with -q. Route critical jobs to priority lanes. Achieve the kind of operational clarity that compounds over time.

⚡

Load-Aware Dispatch

Our batch mode monitors system load in real time and executes only when conditions are optimal. Ship when the system is ready, not just when the clock says so.

🔍

Job Introspection

Full transparency into scheduled work with -c deep inspection. See exactly what will execute, when, and how. Audit every job before it fires. Trust, but verify.

🛡️

Access Governance

Enterprise-grade allow/deny lists control who can schedule. Lock down your execution pipeline with surgical precision. Security that doesn't slow you down.

The Process

From intent to execution
in three elegant steps

Declare Your Moment

Express when your command should execute using Atelier's natural temporal language. Tomorrow at teatime? Thirty minutes from now? Next Tuesday at noon? Just say it.

atelier 4pm tomorrow

Compose Your Intent

Provide the commands to execute — interactively via stdin, or from a curated file. Each instruction is captured, sealed, and queued for its appointed time.

atelier -f deploy.sh midnight

Walk Away

Atelier handles the rest. Your job enters the queue, executes at precisely the right moment, and optionally notifies you on completion. One shot. No recurring overhead.

atelier -l to review pending jobs

Try It

Time Expression Parser

Enter a natural time expression and watch Atelier resolve it to a precise execution window.

Expression Parser

Time Expression

Enter an expression above to see it resolved

Try these:

Job Queue Preview

Today, 4:00 PM echo "deploy triggered"

Queue a

Tomorrow, 12:00 AM ./backup.sh

Queue a

Tomorrow, 12:00 PM curl -X POST https://api.example.com/notify

Queue b

Atelier — Session

$ echo "db-maintenance --full" | atelier 3:00 AM tomorrow

job 7 at Tue Apr 7 03:00:00

$ atelier -f deploy-pipeline.sh teatime

job 8 at Mon Apr 6 16:00:00

$ atelier -l

7 Tue Apr 7 03:00:00 a matb

8 Mon Apr 6 16:00:00 a matb

$ atelier -d 8

$ atelier -v noon

Mon Apr 6 12:00:00

$ _

The world doesn't need
another scheduler.

Every scheduling tool on the market assumes recurrence. They're built for the infinite loop — the daily backup, the hourly ping, the weekly rollup. But the most high-leverage moments in infrastructure aren't recurring. They're singular. A migration that runs once. A deployment triggered at precisely the right window. A cleanup that fires and is never needed again.

Atelier exists because one-shot execution deserves its own category. We believe the act of deferring a single command to a future moment is a craft — not a configuration file, not a cron expression, not a CI pipeline. It's a statement of intent: this thing should happen, once, at this time. Nothing more.

We built Atelier for the operators, the SREs, the solo founders who know that timing isn't everything — it's the only thing.

What People Are Saying

Trusted by teams who
ship at the right moment

"We used to schedule maintenance windows with cron and then immediately delete the entry after. Atelier just... gets it. One-shot by default. It's the tool we didn't know we were hacking around to build."

Kira Lindström VP of Platform Engineering, NovaBridge

"The time expression parser is genuinely beautiful. I typed 'teatime tomorrow' and felt something I haven't felt in infrastructure tooling in a long time: joy."

Ethan Sato Solo Founder, Midnight Labs

"The batch mode alone saved us thousands in compute costs. It just waits until the system is ready. No elaborate load-balancing config. No capacity planning meetings. It just knows."

Rachael Mbeki CTO, Canopy Infrastructure

"Our compliance team loves the allow/deny governance model. We went from 'anyone can schedule anything' to 'surgical access control' in under an hour. Atelier is the rare tool that makes security feel elegant."

Victor Park Head of Security, VaultOps

Pricing

Choose your moment

Every plan includes the core temporal expression engine. Scale up for queues, governance, and load-aware dispatch.

Aperçu

$0 forever

Perfect for solo developers dipping their toes in deferred execution.

5 scheduled jobs per month
Default queue (a) only
Basic time expressions (HH:MM)
Job listing with -l
Community support

Start Free

Frequently asked

What happens if my job fails?

Atelier captures all output from your scheduled command. If the -m notification flag is enabled, you'll receive a completion report regardless of exit status — including any error output. Think of it as your execution receipt.

What exactly is "teatime"?

Teatime resolves to 4:00 PM. It's one of our curated temporal keywords alongside noon (12:00 PM) and midnight (12:00 AM). We believe scheduling should feel human, not mechanical.

How is Atelier different from a recurring scheduler?

Recurring schedulers are designed for infinity — the same task, over and over. Atelier is purpose-built for the single moment. One execution. No cleanup. No dangling entries. The job runs, delivers its result, and is gone. It's deferred execution distilled to its purest form.

Can I review a job's contents before it executes?

Absolutely. Use the -c introspection flag followed by the job number to see the full contents of any scheduled job. Audit before execution — trust, but verify.

What if I change my mind about a scheduled job?

Use the -d flag with the job number to gracefully remove any pending job from the queue. Life is about optionality, and Atelier respects that.

One Moment,Perfectly Timed

Every feature, craftedfor a single perfect moment