Nice execution on the Google Sheets as backend angle — it's a much lower friction onboarding story than "set up a database." How are you handling concurrent writes when multiple users edit the sheet at the same time?

This is a great project, very cool, but it is actually insane to me that CRUD is so apparently hard that Google Sheets is the best solution

I put Google Sheets as a backend (in production) when i wanted a select non technical people to be able to see and modify the data without the cost of building a backend.

I really wish auth was easier to setup for services though, i see no reason google can't provide this out of the box

Don’t really get the purpose for this apart from throw away projects.

For vibe coders is it really “hours” setting up a database these days? GCP cloud sql + drizzle ORM is minutes and actually scales unlike a spreadsheet, heck Claude can even write you a deployment script and run it over GCP CLI.

Version-controllable, plaintext knowledge bases have a durability advantage that no SaaS tool can match. Your notes will outlive any company.

I like this idea, I wrote a tiny CRM-like thing for my mom a month or so ago (upgrade from a google sheet that I had previously upgraded from an Apple Note) and it uses Sheets as it's backend. She can always go back to the Sheet and lose nothing but the web interface she uses it tailored to exactly what she needs. I couldn't be happier with it and she loves it.

I'll have to remember this for my next little one-off tool.

Afaik Google Sheets comes with REST API endpoints by default.

How is this different?

Which scenarios do and which DO NOT require Sheet Ninja?

SQLite, SQLite + drizzle with WAL mode, push it to a VPS, do not waste your time on anything else :)

Thank me when things become super easy!

When things scale, SQLite will still be fine, will fit 99% of the vibe coders needs!

When they don't then migrate to what ever!

Hi all - a friend and I have been dabbling in the entrepreneur space for years, but we never really pulled the trigger because of our corporate jobs. We suffer from the same thing that plagues a lot of engineers: we know how to build products, but we are weak at distribution and marketing.

We feel that being able to build is becoming table stakes and the ability to actually get a product into people's hands is more important than ever. We built SheetNinja (https://sheetninja.io) to force ourselves to learn that side of the business from the ground up.

We chose a validated market (sheets-to-api) so we could focus on the "how to find users" problem rather than wondering if the category was useful. It also fits our current "vibe coding" workflow i.e. when we use LLMs or Replit to spin up an idea, a Google Sheet is often the fastest way to handle CRUD without the friction of setting up a traditional database.

We are looking for feedback on the tool itself and the landing page. We have a lot of visitors but a lower sign-up rate atm.

Thanks, in advance!

https://sheetninja.io

I'm not sure I see why this needs to be a paid service. Unless I understand incorrectly, you can get the same result for free, self contained, with freely available code like this: https://gist.github.com/richardblondet/ce87a397ef669d4d25dd2...