Rendered at 14:05:51 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
heyitsaamir 27 seconds ago [-]
This is excellent! Now I don’t need to build it. Excited to use it for things I build fully my wife and parents
Raed667 1 hours ago [-]
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
riffraff 1 hours ago [-]
You can auth with Google auth after you configure an app, what are you thinking of that would be simpler?
Raed667 1 hours ago [-]
I meant to authenticate a service (that is not running on GCP) to access the sheet, it requires a service account and felt more convoluted than what it needs to be
afferi300rina 53 minutes ago [-]
Completely agree. Managing service account JSON keys and configuring IAM roles just to access a single sheet feels like a huge overhead for simple projects.
robotswantdata 2 hours ago [-]
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.
misiek08 2 hours ago [-]
Cloud SQL costs gazillions, sheet is free (other than selling your data)
gruez 1 hours ago [-]
>sheet is free (other than selling your data)
Except the sheets-to-api SaaS charges $9/month if you want more than 250 requests.
robotswantdata 2 hours ago [-]
Cloud sql lowest tier is pennies a day, this ninja platform is also not free.
A spreadsheet is a misclick away from corruption, why not spend another prompt on getting Claude to configure a db?
n_e 1 hours ago [-]
> Cloud sql lowest tier is pennies a day
Unless things have improved it's also hideously slow, like trivial queries on a small table taking tens of milliseconds. Though I guess that if the alternative is google sheets that's not really a concern.
kevcampb 2 hours ago [-]
Which works out at $100 USD / year. You might think that's trivial, but when you start provisioning multiple environments over multiple projects it starts to add up.
It's a shame that Google haven't managed to come up with a scale to zero option or serverless alternative that's compatible.
Yokohiii 1 hours ago [-]
Sheet Ninja is 108 USD / year and has tiny capacities for every metric. SQLite is free and would stomp this in every aspect on low budget hosting. Even a tiny API that stores CSV would be magnitudes more efficient.
But what would scare me the most, is that google can easily shut this thing down.
robotswantdata 1 hours ago [-]
setup a DB project , use same cloud sql instance for all DBs. Did that for years on non prod or experimental projects.
$100 is a bargain for what you get in terms of resiliency
rvz 2 hours ago [-]
It is trivial to set up a database on GCP given that you know what you are doing and I would pay Google for that stability and support for setting up multi-tenancy and region.
Using Google spreadsheets as a backend will just cause them to charge everyone later.
Sheet Ninja isn't free. Even on their side, "free" does not mean what you think it means.
bercini 30 minutes ago [-]
You can fire up a burstable postgres for about $20/mo
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!
mettamage 1 hours ago [-]
This requires technical skill
threatofrain 49 minutes ago [-]
If Claude can do it reasonably well then there’s another tier of technical skill that can reach.
rvz 1 hours ago [-]
> When things scale, SQLite will still be fine, will fit 99% of the vibe coders needs!
No it won't. SQLite is a poor choice at handling this, period. With all those hacks it still doesn't make any sense over something like PostgresSQL which is designed for that use case.
Yet another reason why I dismiss this nonsense of vibe coding.
rsafaya 2 hours ago [-]
Really good project for a quick data back end.
One feature suggestion: webhook support for row changes:
If my Sheet updates (say, a new waitlist signup), I'd want to trigger for e.g. a Slack notification. Supabase has something similar with their database webhooks. I use that extensively for kicking off signup workflows.
snoopen 2 hours ago [-]
You can do this now directly in the Google environment. Should be trivial to vibe code Google Apps Script to hit a Slack endpoint. You'd probably use an 'on edit' trigger to run the code.
sxa001 2 hours ago [-]
That's a great suggestion, thank you
For your signup workflows, how sensitive would you be to latency? Would a 30 to 60 second delay be a dealbreaker, or are you looking for something that hits Slack the instant the row is created?
(The challenge with Google Sheets is we'd have to poll for changes)
odest 2 hours ago [-]
I really like the idea of using Google Sheets for quick prototyping and maybe "vibe coding" without the friction of setting up a traditional DB.
I haven’t noticed a scrolling issues, btw
tyleo 2 hours ago [-]
This site is pretty broken. The project seems cool but I’d recommend a more static landing page. I bounced very quickly. Didn’t even make it to the bottom with all the distracting animations.
curbits 2 hours ago [-]
I have done this for my own projects for years it’s great for projects that are only for me and gives me a very good db editor also. Cool project though the only risk I see is that if the target audience are vibe coders they will you known just vibe code an integration
sxa001 1 hours ago [-]
Thank you! The idea of our target audience just vibe coding this themselves definitely gave us pause for thought while we were building it :)
We're thinking of playing around with the pricing right now to make sure it is cheaper to just use this than to spend the time and tokens recreating the logic. We will see how it plays out.
sxa001 2 hours ago [-]
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.
This is really helpful thanks. I've just pushed a build to disable the scroll-jacking - ETA 5-10 mins!
evanbabaallos 2 hours ago [-]
Is this meant to replace databases?
0xbrad 2 hours ago [-]
Awesome！
_joel 2 hours ago [-]
"Ship now, pay later" you're not wrong.
smrtinsert 2 hours ago [-]
Do vibe coders need an api for an api? Sounds like something solvable with a skill
Imustaskforhelp 2 hours ago [-]
Good project but I wish something like this can exist for proton mail, I have made some puppeteer scripts which can hook up to proton docs.
But Proton is really doing some great disservice to not having a public api for their docs.
I can imagine it being used for anonymous comments page for webpages etc.
I am not sure if there is something that you can do about it though given that the fundamental issue of this is caused by proton not having an api whereas I think google docs does have API.
I really wish auth was easier to setup for services though, i see no reason google can't provide this out of the box
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.
Except the sheets-to-api SaaS charges $9/month if you want more than 250 requests.
A spreadsheet is a misclick away from corruption, why not spend another prompt on getting Claude to configure a db?
Unless things have improved it's also hideously slow, like trivial queries on a small table taking tens of milliseconds. Though I guess that if the alternative is google sheets that's not really a concern.
It's a shame that Google haven't managed to come up with a scale to zero option or serverless alternative that's compatible.
But what would scare me the most, is that google can easily shut this thing down.
Using Google spreadsheets as a backend will just cause them to charge everyone later.
Sheet Ninja isn't free. Even on their side, "free" does not mean what you think it means.
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!
No it won't. SQLite is a poor choice at handling this, period. With all those hacks it still doesn't make any sense over something like PostgresSQL which is designed for that use case.
Yet another reason why I dismiss this nonsense of vibe coding.
One feature suggestion: webhook support for row changes:
If my Sheet updates (say, a new waitlist signup), I'd want to trigger for e.g. a Slack notification. Supabase has something similar with their database webhooks. I use that extensively for kicking off signup workflows.
For your signup workflows, how sensitive would you be to latency? Would a 30 to 60 second delay be a dealbreaker, or are you looking for something that hits Slack the instant the row is created?
(The challenge with Google Sheets is we'd have to poll for changes)
I haven’t noticed a scrolling issues, btw
We're thinking of playing around with the pricing right now to make sure it is cheaper to just use this than to spend the time and tokens recreating the logic. We will see how it plays out.
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
But Proton is really doing some great disservice to not having a public api for their docs.
I can imagine it being used for anonymous comments page for webpages etc.
I am not sure if there is something that you can do about it though given that the fundamental issue of this is caused by proton not having an api whereas I think google docs does have API.
It's more a message to proton if anything.