A Show HN submission titled around Google Sheets as a back end for web pages and AI agents reportedly points to SheetRelay. Going by that title alone, SheetRelay presents itself as a way to use a spreadsheet as the data layer behind a page or an agent.
The SheetRelay Google Sheets back end pitch is worth examining because spreadsheets are where much small-scale data already lives, and agents need somewhere to read and write. The material available holds no pricing, ownership, security details, limits or usage figures, so this is a pitch to evaluate, not a product to adopt.
What does SheetRelay say it offers?
Google Sheets as a back end for web pages and AI agents, and nothing beyond that. The only evidence is the title of one submission and a link to sheetrelay.com. The title may be the submitter’s own wording, not SheetRelay’s text.
The submission carries no engagement figures and no page text, and we describe no community reaction. We cannot say how SheetRelay works technically, who runs it, when it appeared or whether anyone uses it.
What is a back end, and why would a spreadsheet be one?
A back end is the part of a website or app that stores data and responds to requests from the front end, the page a visitor sees. Without one, a page can display information but cannot easily save or retrieve it.
Google Sheets is a spreadsheet service where data sits in rows and columns that people can edit directly. Using it as a back end means a page or agent reads and writes those rows instead of using a conventional database.
The appeal is easy to see. People already keep data in spreadsheets, little setup is needed, and a non-programmer can inspect and fix records by hand. For small projects that can be a real advantage. This is general background and BriefFlash analysis, not a finding about SheetRelay.
Where does a spreadsheet back end tend to fall short?
Typically when data grows, when many users write at once, or when records must stay strictly consistent. Conventional databases are usually preferred in those cases. We state no Google Sheets limits here, because none appears in the material.
Sensitive data is the other concern. A spreadsheet that suits a prototype may not suit a product with many users, and the material does not say where SheetRelay’s own limits lie.
The comparison above sets the little the title states against what remains open. The gaps are not evidence of a problem; they are the questions a builder would ask first.
What changes when an AI agent is the one using the sheet?
Speed, repetition and permissions matter more. AI agents act on a user’s behalf by calling other software, and an agent that must remember things, log results or read a task list needs somewhere to keep that data. That is the role a back end plays.
A person clicking through a sheet makes occasional edits. An agent can read and write rows automatically and repeatedly, so a mistaken instruction, an overly broad permission or a flood of writes can do more damage, faster. We think that makes access scoping and rate limits central questions, though the material says nothing on how SheetRelay handles either.
Connecting any tool to a sheet also means granting it some access to the data inside. Who runs the connecting service, and what access it asks for, therefore matter. That is a general property of such connections, not a claim about SheetRelay.
How can you judge a tool like SheetRelay?
Ask five questions before connecting anything, and put the same ones to any tool of this kind.
- Who runs it? An identifiable operator shows who is accountable if something goes wrong.
- How is access to the sheet handled? Look for what permissions it requests and whether they can be limited or revoked.
- What does it cost? That includes free tiers and what happens when they run out.
- What limits apply? Volume, speed and size limits decide whether it survives past a prototype.
- What traction does it show? Usage, example projects and a track record separate a pitch from something people rely on.
For SheetRelay, the material answers none of the five. That is the most useful thing we can report on this little evidence.
Similar needs are often met by a simple hosted database or a form tool, which are analogies only. Nothing says SheetRelay works like either.
What should builders do next?
Read SheetRelay’s own site, the only source for what it says about itself, and look for answers to the five questions before pointing it at real data. If you try it, start with a sheet holding nothing sensitive, and give any agent the narrowest access that works.
Frequently asked questions
What is SheetRelay?
SheetRelay presents itself as a way to use Google Sheets as a back end for web pages and AI agents, according to the title of a Show HN submission that links to its site. That title is the only evidence available. The material holds no information on who runs it, what it costs or how it works.
Can Google Sheets really work as a back end for a web page?
In general, a spreadsheet can serve as a simple data store: a page or agent reads and writes rows instead of using a database. That tends to suit small projects. Large datasets, heavy simultaneous writes and strict consistency usually favor conventional databases. This is general background, not a finding about SheetRelay.
Is a spreadsheet a good data store for an AI agent?
It can work for light tasks such as logging results or reading a task list, and a person can inspect the rows by hand. Agents write quickly and repeatedly, so permissions, mistakes and rate limits matter more than for a human user. Whether it suits you depends on your volume and data.
Is it safe to connect a spreadsheet to a third-party tool?
Not automatically. Connecting a tool means granting it some access to the data in the sheet, so who runs the service and what access it requests matter. The material available does not say how SheetRelay handles access, so test with non-sensitive data and grant the narrowest permissions.
How can I judge a tool like SheetRelay before using it?
Ask five questions: who runs it, how access to the sheet is handled, what it costs, what limits apply and what traction it shows. Clear answers to all five are a reasonable sign. For SheetRelay, none is answered in the material available, so check its own site before connecting real data.
