Enterprise spreadsheet applications, with the model still in Excel
Enterprise spreadsheet applications, built from the workbooks your business already depends on. No rebuilding the logic, no exposing the file, and none of the version sprawl that made those workbooks a risk in the first place.
Already running inside organisations like these
Manufacturers, reinsurers, hotel groups, publishers and public bodies, several of them for more than a decade.
More in customers.
The spreadsheet is not the problem. The copies are.
Critical models tend to end up as attachments: redundant files, inconsistent versions, no permissions and no record of who changed what. That is an end-user computing risk long before it is an IT problem.
Nobody touches the file
Users interact with a web interface bound to cells. The workbook stays server-side, so the model, the pricing assumptions and the intellectual property inside it are never downloaded and never visible to the people using the application.
Submissions become records
Transactional data is written to a structured database rather than back into the workbook. One source of truth, queryable, exportable, with full record history and per-record permissions instead of a folder of near-identical files.
Changes are controlled and logged
Workbook versioning, transaction history, and migration between environments make an update a controlled release rather than a file swap. Every transaction is captured and traceable, which is what regulated functions need to evidence.
Security model and permissions are documented in the security guide, and release handling in application lifecycle management.
What enterprise deployments include
Private Cloud and server licences carry the entire capability set. Solver, Goal Seek, Power Query and DbConnect all run here, and the limits published on the public cloud tier do not apply.
All 501 Excel functions
The same engine on every deployment. All 501 run here, and the 15 that do not are named individually with the reason. Coverage is measured against Microsoft’s own function categories rather than a list of our own.
No workbook size ceiling
Enterprise tiers lift the file size limit entirely, and it matters more often than people expect. We have customers running complex models of 80 MB and beyond, calculated server-side, so nothing depends on what a user’s laptop can open or how long it takes to recalculate on the desktop.
Single sign-on and your identity provider
Microsoft Entra, Okta and Auth0. Users, groups and roles are managed centrally, and access to each application is governed by your own directory rather than a separate password list.
Where your model and your data actually go
The two questions procurement asks first, answered plainly.
Your workbooks are never shared with LLMs
We do not send your spreadsheets to large language models and we do not use them to train any model. The logic your business has spent years refining is not an input to somebody else’s product.
The engine is ours, and it runs where you put it
Calculation happens on a proprietary engine we have built and maintained since 2006. There is no external calculation service and no round trip to a spreadsheet API. On a server licence nothing leaves your perimeter at all.
Two deployment models, both quoted
Which one you need is usually settled by where the data is allowed to sit, not by what the application has to do.
Private Cloud
A dedicated, single-tenant instance on Microsoft Azure, managed by us, under your own domain.
- Deployed in the Azure region you choose
- Dedicated resources, no shared tenancy
- Custom domain and interface branding
- Unmetered application access and API calls
- Backups and scaling handled by us
Server licence
Installed on your own infrastructure, on premises or on a cloud instance you control.
- Full data sovereignty, nothing leaves your network
- Direct integration with internal systems and databases
- Your own security configuration and hardening
- Air-gapped deployment possible
- Unlimited applications on every tier
Server requirements are published in the deployment documentation. We will review them with you before anything is signed.
At this scale, already
Six organisations that put a business-critical model in front of a large population of users.
Southern Risk deploys new programs to underwriters and 1,300 broker agents in days
Read the case studyIHG saved around $30,000 per property on document generation
Read the case studySEIU 521 models wage changes across complex contract negotiations
Read the case studyReinsurance Management Associates built quoting software with no programming
Read the case studyCAR Financial Services moved dealership financing to real-time information exchange
Read the case studyNew Jersey City University built interactive enrollment dashboards
Read the case studyDozens more case studies are published across insurance, engineering, energy, education and government.
Start with the requirements, not the file
Tell us what the model has to do, who needs access, and where the data is allowed to sit. We will tell you which deployment that points to and what, if anything, needs attention. Technical review happens under NDA, and nothing needs to be shared before one is in place. If another approach fits better, we will say so.