Workflow licence and purchase options
Production use is free up to 50 Designated Workflows per installation, counted cumulatively. Above that you buy capacity in blocks of 25, per installation and per year.
Orders open once a merchant of record is chosen. Until then no component order is taken. Every order is then accepted at the prices and on the terms on this page, without negotiation. The steps below show the path every order will follow. Questions: sales@stella-ops.org.
Options
| Option | What it covers | Price |
|---|---|---|
| Free | Production use of an installation with up to 50 Designated Workflows; use outside production at any count. | No charge, no order and no licence file |
| Paid capacity | Production use above 50 Designated Workflows, in started blocks of 25, for one installation. | $250 per block for twelve months; timely renewal $125 per block |
| Embedded in your product | Production use of the engine as part of a commercial product you deliver to a named end customer, on that customer's installation. | No charge: an Order with a no-fee embedded line |
| Hosted service for third parties | A general workflow platform on which other parties deploy and operate their own workflows. | By quote |
| Support Review | A written engineering assessment of one defined issue concerning the Workflow engine. No review is included in an order. | $75 per review, refunded when the review finds a reproducible defect in a supported release |
Paid capacity in blocks
- Each started block of 25 Designated Workflows above 50 costs $250 for twelve months of new versions. Your capacity is 50 plus 25 for each block: one block covers up to 75. There is no monthly price and no upper limit on blocks.
- The count and the capacity you buy apply per installation: each installation is ordered and counted on its own, and capacity is not shared between installations. Calling an installation development, test or staging does not exempt its production use; use outside production needs no order. Ordering both the Workflow engine and the Router brings no discount.
- A timely renewal costs $125 per block for twelve more months. Blocks added at a renewal cost $250 each. You may renew fewer blocks, but the cumulative count does not go down.
- To add capacity during coverage, each extra block costs $250 × the days left to your coverage end date ÷ 365, rounded to the cent, at least $20.55 per block. Added blocks keep your coverage end date.
| Days left | Price per block |
|---|---|
| 365 | $250 |
| 146 | $100 |
| 73 | $50 |
| 30 | $20.55 |
| 1 | $20.55 |
What a purchase covers
- A payment buys twelve months of coverage, starting on the day the payment is received; an order cannot name a later start date. The coverage end date is twelve months after the payment date.
- Every version first published before the coverage end date, older versions included, stays licensed at the capacity you bought, without limit of time. A version first published on or after that date is not covered, patches included: using it above the free limit needs a renewal or a new purchase.
- Renewal is automatic unless either side gives notice at least 30 days before the coverage end date. A renewal paid before the coverage end date adds twelve months to it. An unpaid renewal lapses and nothing is owed for it; a later purchase costs the block price, and its coverage starts on that payment.
- When coverage ends, the software keeps running and every covered version stays licensed at the capacity you bought.
Worked examples
| Workflows | Blocks | Capacity | Initial fee | Timely renewal |
|---|---|---|---|---|
| 75 | 1 | 75 | $250 | $125 |
| 100 | 2 | 100 | $500 | $250 |
| 300 | 10 | 300 | $2,500 | $1,250 |
How to buy
- 1
Order
Name the installation, the measured count and the blocks you need, with a self-attestation of the count and of the versions in production use. The Order states the price, the coverage end date and the renewal terms.
- 2
Screening
Each order is screened for sanctions, export controls and eligibility: the customer, its owners, the payer, the end users, the destination and the end use. Availability is not automatic.
- 3
Acceptance
Your authorised representative accepts the Customer Agreement with its Schedule 3, the Component Schedule. The Order identifies each text by its SHA-256 digest.
- 4
Payment in advance
Every fee is paid in advance. The permission and the coverage start on the day the payment is received.
- 5
Licence file
You receive a vendor-signed licence file for the installation, in the name agreed in the Order. The component reads it offline.
Documents
- Workflow documentation
- How the Workflow engine compares with other workflow engines
- Getting started with the Workflow engine
- Installing Stella Ops packages: the feed, versions, signatures and the offline archive
- Workflow packages: which package serves which role, and its licence
- Workflow licensing guide: counting workflows, the licence file and the notices
- Customer Agreement, Schedule 3: the Component Schedule
- Availability and sanctions notice →
