Unit costs marked ✓ verified come from Oracle's published SuiteScript 2.1 governance tables. Record and search operation costs genuinely vary by record type and complexity — I've filled in commonly-cited typical values, marked "~typical," and left every cost editable so you can match your own script.
Map/Reduce scripts don't have a single deployment-wide limit — individual method invocations are governed separately, so this calculator doesn't apply to them the same way.
Add up your record loads, searches and API calls to see if you'll hit the 10,000-unit limit before it fails in production.
Compare the running total for a few different approaches before committing to one in code.
Sanity-check a script's governance footprint during a code review without instrumenting it live.
Directly from Oracle's SuiteScript 2.1 governance documentation — HTTP requests, email, file operations, config.load, currency.exchangeRate and action.executeBulk all have one published number regardless of context.
Oracle's own docs state these vary by record type and complexity rather than publishing one flat number. The defaults here are commonly-cited typical values — edit them to match your actual case.
No — it's a standalone calculator. Nothing here reads from or writes to a live NetSuite instance.