Pricing
Why the bill counts workflows
The meter is the workflow: one run that lands one outcome. Here is what counts as one, what never counts, and where the warnings sit.
Sean Wilson6 minute read
Braille meters the workflow: one run that lands one outcome in a system you already use. This is how that works, in full, including the parts that cost nothing.
The unit
| Completed run | Counts as |
|---|---|
| Standard workflow: reads the document, fills the schema, delivers the result | half a workflow |
| App-workflow: matches against or writes records in a connected app | one workflow |
A run is an app-workflow when any step of it touches records in a connected app: looking the vendor up, creating the bill. Everything else is a standard workflow, including delivering a file into a storage app and matching against Braille-native entities, the lists you keep inside Braille.
The builder shows a workflow's classification before you switch it on, so the price of a run is known before the first one happens. Sub-workflows classify on their own steps, and a helper that only ever serves one parent belongs inside that parent as a supporting action, which is free.
What one workflow is
The definition has to be bounded, or one enormous workflow swallows the account:
- A workspace contains workflows.
- One workflow produces one output: the single business outcome it exists to land, such as an invoice in QuickBooks or a filled assessment in the system that holds them.
- Supporting actions are free. The writes needed to make this run's output possible, like creating the vendor so the bill can exist, cost nothing.
- Workflows can call workflows. A sub-workflow call is a run of that sub-workflow and burns its own allowance.
Allowances, and what happens past them
| Plan | Included each month | Then, per app-workflow |
|---|---|---|
| Solo, $49 | 200 workflows, or 100 app-workflows | $1 |
| Team, $199 | 1,000 workflows, or 500 app-workflows | 50¢ |
| Business, $999 | 6,000 workflows, or 3,000 app-workflows | 35¢ |
| Enterprise | Custom | Price on application |
Standard runs bill at half the plan's rate, matching their half weight: 50¢ on Solo, 25¢ on Team, 17.5¢ on Business.
Allowances burn in a fixed order. The monthly allowance resets and burns first. Purchased runs and the credits that come with a guided build never expire and burn last. Past both, overage bills at the plan's published rate, and the rate is always printed directly under the allowance it applies to.
Overage rates fall as plans rise, which is deliberate. Heavy use on a small plan crosses the next plan's price early: Solo at 250 app-workflows a month costs the same as Team, and Team's included volume run on Solo would cost $449 against Team's $199. Overage is there to absorb a spike, and the upgrade is the answer to a new normal.
Duplicates never bill
Every input set is hashed. Same hash and same workflow, and the run is never billed twice, whether the file was forwarded twice, posted twice by a webhook, or uploaded by two people who both thought they were the one doing it.
Change the input or change the schema and the hash changes, which makes a new run, and that one bills. So a corrected re-run costs you, and an accidental duplicate does not.
Failures split by fault
A run that fails because of Braille, a system error or a mis-routed document, is free. We fix it and re-run it at our cost.
A run that fails on its own inputs bills at a heavy discount. The exact rate, and the precise line between a failed run and a run that finished with results you did not like, are still being settled. Both will be published before either applies to a bill.
You see the meter before it bills
Every usage meter warns at 80% of its allowance, before a cent of overage. That covers workflows and it covers entities, the records Braille embeds from each connected app so it can match against them.
The structural parts of a plan behave differently on purpose. Connections, concurrent runs and the file-size cap are capacity rather than usage, so each one can be raised a la carte up to the next plan's included level and no further. Workflows and entities stay uncapped meters that absorb a spike at a published rate.
Rosetta has its own meter
Rosetta, the whole-pile engine, is a separate product with separate bands: S at $1,199 a month for 25 runs, M at $3,999 for 100, L custom, or $60 for a single run. Up to 250 MB zipped per run, never billed per page, and Rosetta runs never touch your workflow allowance.
Annual, monthly, and the way out
Prices above are the effective monthly rate on annual billing. Month to month is the annual rate times 12/10, so $59, $239 and $1,200, which makes annual two months free.
Annual contracts carry the 90-Day Walkaway. Cancel in writing inside the first 90 days, pay only for the quarter you used, and keep every schema Braille filled for you. Your data is deleted on request. It applies once per customer, and it exists because asking for a year up front should put the risk on us.
The full grid, every allowance with its overage rate under it, is on the pricing page.