Spreadsheets are a backend

Finds sheets run our corner of the internet. Why a Google Sheet works as a free backend, and where it stops.

Engineering2 min read

Our corner of the internet runs on Google Sheets. The finds sheets shoppers pass around list thousands of products each, with pictures, prices and links, kept up to date by people who don't write code.

A sheet is a program

In a spreadsheet, the row you see is the record and the column header is the schema. Editing the data and editing the screen are the same edit.

Formulas make it programmable. Each cell is a function call, and the sheet recalculates whenever an input changes. Google Sheets has functions like QUERY for SQL-like queries over a range, IMPORTXML to pull values off a web page, and IMAGE to show a picture in a cell.

A tab becomes an API

Every Google Sheet comes with Apps Script: JavaScript attached to the file, free with a Google account. Add a doGet function, deploy the script as a web app, and the sheet answers web requests at its own address:

JavaScript
function doGet() {
  const rows = SpreadsheetApp.getActive()
    .getSheetByName("Finds")
    .getDataRange()
    .getValues()
  return ContentService
    .createTextOutput(JSON.stringify(rows))
    .setMimeType(ContentService.MimeType.JSON)
}

Triggers run scripts on a schedule or on every edit, and the Sheets API lets other programs read and write the grid. One spreadsheet holds up to 20 million cells. There is no server to run.

Quotas are per user

A script runs for up to 6 minutes at a time. A personal account gets 20,000 outside web requests a day, or 100,000 on Google Workspace. The Sheets API allows 300 reads a minute per project.

Apps Script quotas belong to the person running the script. A template copied by ten thousand people runs on ten thousand sets of quota, and a web app set to run as the visitor spends the visitor's quota, not yours. Opening a shared sheet costs its author nothing. So a sheet scales sideways: more users bring more capacity.

Where it stops

A spreadsheet isn't a database. There are no transactions, two editors can overwrite each other, and deleting a row can break a formula three tabs away. The quotas are real too, and Google has said it plans to charge for going over the Sheets API's request limits later in 2026.

That's why orders, payments and wallets at NinjaBuy live in a real database. Sheets are where shoppers and creators already work.

What we do with them

Paste a finds sheet's link into NinjaBuy and every product link in it becomes a product you can buy, next to the author's own picture, name and price. If you make finds sheets, the finds sheet standard shows the layout we read best: one product per row, a clickable link, the picture in the cell.

Keep reading