A business rules engine, or simply a spreadsheet?

A business rules engine is built for large rule sets with versioning, approvals and audit. Many teams need less: prices, tiers, scores and eligibility rules that a specialist keeps as formulas in a spreadsheet. SpreadAPI publishes that spreadsheet as an API, so your systems call the rules as one step.

The rules in the spreadsheeta discount rule
CriterionValueDiscount
Quantityfrom 1005 %
Quantityfrom 5008 %
Customer groupPartner+ 3 %
Term24 months+ 2 %
Discount500 units, partner, 24 months13 %

The person who owns the price list reads and changes it. A new rule is a new row and a formula that looks it up.

The rules as one callfrom your system
POST /api/v1/services/{serviceId}/execute

{ "inputs": { "quantity": 500, "group": "Partner", "term": 24 } }
{ "outputs": [ { "name": "discount", "title": "Discount", "value": 0.13 } ] }

Your application sends the values and gets the decision back. It sees inputs and results, never the formulas.

Three steps, no rule language to learn.

The rules stay in the format most people in a company can already read.

Step 1

Write the rules as formulas

Tiers, lookups in two dimensions, weights, exceptions. Bring an Excel file or build the workbook in the browser.

Step 2

Mark what goes in and out

Inputs can be limited to a range or to allowed values; a call outside them is refused before anything is calculated. Test with known cases before you publish.

Step 3

Call them as one step

Over REST from your application, from n8n, Zapier, Make or Power Automate, or from an AI assistant over MCP. To change a rule, edit the workbook and publish again.

What teams keep in the spreadsheet.

Prices and discounts

Quantity tiers, customer groups, term discounts. Sales changes the price list; the shop and the CRM get the new price after the next publish.

Scores and eligibility

Points per criterion, thresholds, a result such as A, B or C, or "eligible" and the reason. The specialist tunes the weights.

Fees and commission

Rates by product and target attainment, minimums, caps. Many cases go through one batch call.

Where a spreadsheet is enough, and where it is not.

If rule changes have to be approved, versioned and audited, you need a real rules engine. If the rules fit into a spreadsheet and one person or team owns them, this is the shorter way.

A good fit

  • Rules a specialist can read and maintain as formulas
  • Prices, scores, tiers, fees, eligibility
  • Rules that change more often than the software around them
  • One owner or one team per rule set

Not a rules engine

  • No version history with rollback
  • No approval workflow before a change goes live
  • No audit trail of who changed which rule
  • The values of a call are not recorded
  • It calculates; it does not start or route anything itself

What is a business rules engine?

Software that keeps business rules apart from application code, so they can change without a release. Full systems (BRMS) add a rule repository, versioning, approvals and audit. A spreadsheet covers the first part: rules outside the code, readable by the people who own them.

Guide: decision tables as an API →

Questions before you decide

Is SpreadAPI a business rules engine?

No. SpreadAPI publishes a spreadsheet as an API. The rules are formulas in the workbook; there is no rule repository, no version history with rollback, no approval workflow and no audit trail of who changed which rule. It suits rule sets that a specialist can keep in a spreadsheet.

How do I change a rule?

Edit the workbook, save and publish again. Until you publish again, callers keep getting the published version.

Can I test a change before it goes live?

Yes. The test panel calculates on the draft in your browser. Nothing changes for callers until you publish.

Can I go back to an earlier version of the rules?

Not inside SpreadAPI. Keep earlier versions of the Excel file yourself, for example in your version control or document storage, and import the one you need again.

Can I see who called the rules and what was decided?

The usage pages show when a service was called, over which channel, by which token or AI connection and whether the call worked. Input and result values are not recorded. If you need a complete record of decisions, keep it on the calling side.

What does it cost?

The Basic plan is free: one published service of up to 250 KB and 1,000 calls a month; drafts of any size up to 5 MB can be built and tested. Pro costs €99 a month: unlimited published services of up to 5 MB each, 10 MB for your published services and 10,000 calls a month.

Keep the rules where the people who know them can change them.