The Full Story

Product overview

Excelerant runs the Excel workbooks your business relies on as production software: in the browser, behind an API, or from Excel itself. The people who built the workbook keep maintaining it, and IT keeps control.

  1. How it works
  2. Calculation
  3. Version management
  4. Browser, API or Excel
  5. Dashboards
  6. Scale and automation
  7. Governance
  8. Access and privacy
  9. Deployment and licensing

How it works

From workbook to working application in about five minutes.

  1. Upload your workbook to Excelerant.
  2. Set it up in a short wizard: choose how users see it (the full workbook, certain sheets or a web form), click the cells that are inputs and outputs, mark the cells that hold personal data, and decide who may use it. This usually takes about five minutes.
  3. Use it in the browser, call it from your other systems, or run it from Excel.
  4. Release new versions from test to production, with every run logged.

Optional: to make large VBA runs faster, you can mark loops that may run in parallel with a one-line comment in the VBA. The workbook keeps working in Excel as before.

Calculation

Your workbook, calculated without Excel.

  • Formulas and Power Query run as they are, with nothing for you to rewrite.
  • More than 500 Excel functions are supported, including newer ones such as LAMBDA and LET.
  • VBA runs too, not just the formulas, so models built around macros work as written.
  • The results are the same as in Excel, Goal Seek included.
  • Workbooks can pull in live data from databases, files and market data feeds, including through Excel’s RTD function.

Version management

Every change is a new version, and every version is kept, so any figure can be reproduced.

  • Check a workbook out, change it in Excel and check it in again with a comment. The previous version stays exactly as it was.
  • Choose which version is live and from which date, and roll back to an earlier version in one step.
  • Compare two versions to see which sheets, cells, formulas and VBA changed, and download the differences as a report.
  • Versioning is bi-temporal: see which version applied on any date. Every calculation records the version that produced it, so any past result can be reproduced.

Browser, API or Excel

One workbook, several ways to use it.

  • In the browser: the workbook as an application for the users you allow.
  • Through the REST API: your other systems call the workbook like any other web service.
  • From Excel: while you work on a workbook, the add-in runs it on the server, including your latest changes, and puts the results back in your sheet.

Dashboards

Results from several workbooks, together on one screen.

  • Combine live results from different workbooks side by side, for example for management.
  • The dashboard updates as the workbooks behind it change, so it can stay open on a screen all day.
  • Each viewer sees only what they are allowed to see.
  • Viewers can try their own inputs in a private copy, without affecting anyone else.

Scale and automation

Large runs, short waits.

  • Batch runs over thousands of input sets, and bulk tests of a new version against the old one.
  • Large runs use every processor core, where Excel runs VBA on a single one, and can be spread over several servers.
  • Scheduled runs, such as a daily report at market close.

Governance

A full audit trail, without slowing the business down.

  • Every calculation is logged with who ran it, when, and with which version.
  • Saved calculations keep their inputs and outputs, and can be replayed.
  • Building a model is separate from using it: users run the released version while modellers work on the next one.
  • Working copies: many people each fill in their own copy of one master workbook.

Access and privacy

Each person sees what they should, and nothing more.

  • Roles decide who can view, run, change or manage each workbook.
  • Access rules go down to a sheet or a range of cells, even when several people share a live workbook.
  • Personal data is marked once and masked in downloads.

Deployment and licensing

Your environment, and no charge per calculation.

  • On-premise, in a dedicated hosted environment in the region you choose, or on Microsoft Azure.
  • Not metered: you don’t pay per calculation, so running a model more often doesn’t cost more.
  • Sign-in with Microsoft Entra ID. A hosted environment can use your own Entra tenant, so users keep their existing accounts.