Free during private beta

Free to declare.
Billed on what
you deploy.

One plan, one unit: the production service. Jobs, dependency edges, schedules, calendars and environments are unlimited on every tier.

Below is the pricing we plan to launch with. It may shift before then, and beta teams will hear about it first.

Work out your bill

3
112

Billing period

Estimated monthly cost

$134/ month

Assumes 3 production services on the $99 plan, which includes 2, plus 1 × $35, billed monthly. Dev and staging are unlimited and never counted. Planned launch pricing, subject to change.

The same graph in three environments. One of them is billable.

Nothing differs between them but the word at the top. Putting a price on graph richness is putting a price on knowing what your nightly depends on.

Development$0
ledger_close → recon_batch
fee_accrual → settle
settle → regulatory_export
calendar: fiscal_close
Staging$0
ledger_close → recon_batch
fee_accrual → settle
settle → regulatory_export
calendar: fiscal_close
ProductionCounted · 1
ledger_close → recon_batch
fee_accrual → settle
settle → regulatory_export
calendar: fiscal_close

Identical graph, promoted twice. What you pay for on the right is that it is real — governed, audited, on the hook.

What actually differs

Unlimited jobs, edges, schedules, calendars, dev and staging environments, the Weev agent (upcoming) and fair-use run volume are on every tier. This is the rest.

Free

The job you check every morning

$0

Production services
1
Run history
7 days
SSO and role-based accessPlanned
—
Approval workflows for promotionPlanned
—

Professional

For teams whose jobs move money

$99/mo

Production services
2, then $35 each
Run history
90 days
SSO and role-based accessPlanned
—
Approval workflows for promotionPlanned
—

Enterprise

For orgs replacing a scheduler

Custom

Production services
volume pricing
Run history
extended audit retention
SSO and role-based accessPlanned
✓
Approval workflows for promotionPlanned
✓
// planned launch pricing and planned capabilities · subject to changeSecurity & architecture →

Why the unit isn't a job

The price list wrote the documentation.

Control-M-class schedulers license by job or task count. The rational response inside those shops is to stop defining jobs — bundle five steps into one script so the licence covers it. That is the reason nobody in the building can say what the nightly actually depends on.

We charge for the thing you would deploy anyway, and give away the thing we want you to do more of. Define five steps or five thousand — the price does not move.

Questions

Is there a run limit?

Each tier has a generous fair-use ceiling, there to stop abuse rather than to meter you — no per-run charge, no overage bill. Your jobs keep running; we won't drop production work over a plan limit.

Is this pricing final?

No — it's the pricing we plan to launch with, and it may change during the beta. Everything is free while Weev is in private beta.

What counts as a production service?

One project deployed to a production environment. Everything inside it is unlimited, and development and staging never count toward it.

Declare the whole graph. Pay for one service.

Free through the beta, and you're talking to the engineers building it.