SpreadsheetWeb

What SpreadsheetWeb is

SpreadsheetWeb is an application builder for people whose logic already lives in an Excel workbook. The company's headline is "SpreadsheetWeb runs your Excel formulas as a web application": you upload a workbook, and it builds a web application around the formulas you already wrote. In its words, "the interface, data, documents, and API are configuration rather than code." The site says it has been doing this since 2006, and the home page counts 10,000+ applications built and 20 years in the business.

The reader it fits is an analyst, engineer, actuary or operations owner who has a model that works and needs other people to use it, without a developer rewriting it in another language. The site names manufacturers, insurers, hotel groups, consultancies and city governments as companies running on it, some with a single calculator and some with dozens of applications across several departments. The pages do not say where the company is based.

What you build and how

The mechanism is spelled out in 6 steps on the home page, and it is the part that decides whether the product fits your project.

First, the workbook is read, not converted. The platform opens the .xlsx and keeps the formulas as formulas, so there is no porting step and no second copy of the logic to keep in sync with the original. Second, calculation runs on what the company calls a proprietary engine it has built and maintained since 2006, "not a third-party library and not a copy of Excel running on a server," and it handles the cross-sheet references and layered formulas a real workbook relies on. Third, the file never leaves the platform: it is uploaded once, stays server-side, is never sent to the browser, never handed to an outside service and never exposed to the people using the application. On Private Cloud and server licenses it stays inside your own environment.

Fourth, you point controls at cells. In an Excel-like grid you pick input and output cells and bind controls to them, with no named ranges to define first, no mapping code and no rebuild. Fifth, the data lives in a database, not the file. Everything people submit is written to a structured database as its own record, never back into the workbook, so you can filter, export, track full record history and set permissions per record. Updating the calculation does not disturb anything already collected. Sixth, updating means re-uploading: you revise the model in Excel, upload it, and the application uses the new logic.

The site lists live applications built from ordinary workbooks that you can open and test. A mortgage loan calculator uses PMT, an amortization schedule and a chart driven from the workbook. A wind load analysis is an engineering calculation with dozens of inputs running the original structural model. Startup financials is a multi-year projection with output grids. An HR dashboard aggregates and charts collected records rather than a static sheet. Hurricane route maps use a map control fed by latitude and longitude columns, animated across a timeline. A security questionnaire is scored, with conditional sections and a saved record per response.

The "What people build" list gives the same range in categories: online calculators, sales quoting and CPQ, scored questionnaires, timesheet applications, search applications and reporting applications. Those cover the practical reasons a spreadsheet gets promoted to an application: a client needs a calculator on a website, a sales team needs consistent quotes, or a department wants a structured questionnaire that scores itself. A separate gallery and a features page hold the control library, document generation and API details that the home page only summarizes.

The home page is direct about what does not run. Coverage is 501 Excel functions, counted against Microsoft's own list so you can check it, and 15 functions do not run. Each of the 15 is named individually with the reason, and the coverage table downloads as a CSV with no form in front of it. VBA does not execute. Interface macros are usually replaced by configuration rather than rewritten, and calculation macros convert to LAMBDA or to the built-in Simulation event. The company says both cases are documented end to end.

If you are unsure whether your model will run, the site invites you to send the workbook: it will check it against the supported function list and report what needs attention, "including when the honest answer is that another tool fits better." You can also set up a call with presales.

Plans, pricing and claims on the site

The home page makes concrete claims about cost and terms. A free tier costs $0 and needs no card, and the site calls it free forever. The company says prices are on the page rather than behind a form, and that what each plan can and cannot run is written where you would be about to pay. Deployment options are named as Hub, Private Cloud and Server, under the line "Your model, your data." A separate Enterprise page and developer documentation are linked for regulated environments and large teams.

On data handling the site states: "We do not send your spreadsheets to large language models, and we do not use them to train any model." It adds that the calculation stays in-house, with no external calculation service, no round trip to a spreadsheet API and nothing that requires your file to be copied somewhere else to get an answer.

The home page carries customer testimonials. One principal at Abenaki Analytics says it was "incredibly easy to convert the tool into a web application" and that he had a working application "in the matter of a couple of days." Another customer says that before choosing SpreadsheetWeb they compared other solutions and got a quote of around $80,000 for a custom-coded app. These are testimonials the company chose to publish, so read them as its own selection.

The company's blog also has an article on no-code vendor lock-in, written for enterprise buyers. It lists business continuity, experience with enterprise customers, support, software bugs, feature limitations and price adjustments as the risks to weigh. Its suggested protections include a source code escrow agreement, deploying the platform on your own infrastructure, a detailed service level agreement with penalties, and a long-term contract that caps annual price increases. That is a vendor's argument for how to evaluate vendors, and it is consistent with the Private Cloud and Server options the home page offers.

Who it suits and who it does not

SpreadsheetWeb suits teams where the spreadsheet is the asset: a pricing model, a loan or insurance calculation, an engineering check or a financial projection that took years to get right and that nobody wants to rebuild. Because the formulas are kept as formulas and the file stays on the server, the person who owns the logic keeps maintaining it in Excel. Organizations that need the model to stay in their own environment have a Private Cloud or server option to look at.

It is a worse fit when the workbook leans on features the platform does not run. VBA does not execute, 15 Excel functions are not supported, and a model built around macros will need rework. It is also a narrower tool than a general app builder: the pages describe calculators, quoting, questionnaires, timesheets, search and reporting built around a model, not a general-purpose database app with arbitrary screens. If you have no existing workbook and are starting from a blank page, the product's central idea does not apply to you. The honest first step, as the site itself suggests, is to send your workbook and see what it says.