8 ms·

Xata – Database service for serverless apps

185 points by madmax108 5y ago

CaptainJustin 5y ago
Looks similar to Firestore - identity aware, serverless, pay as you use.
nkmnz 5y ago
Looks similar to supabase, plus analytics.
ryanjshaw 5y ago
Bitter tale of a serverless experience: Serverless is great until you spend weeks building something in Cloudflare Pages and Workers, then add it to Google and... Google claims your site doesn't exist. Search Console Live Test gives a vague 'General HTTP Error', Rich Results Test says the 'page is unavailable', Ad Words says 'Destination not working'. Bing indexes your site with no problems, and every device you and your friends own works fine, every uptime tester on the planet says you're good. Cloudflare shows no firewall events and logs are a 'contact us for pricing' Enterprise-only feature. So what do you do - if Google thinks your serverless site doesn't exist, and you can't debug it because it's all magic? You can't do anything. Back to conventional hosting you go.
- the_duke 5y ago
  You can use any external logging service that has an HTTP API. Not ideal, but it works fine. I'm doing this with Cloudflare workers by sending access logs to a self hosted Matomo analytics and error logs to Loggly. But in general, Cloudflare isn't really suitable yet for general app development. They need a lot of additional services for that to become viable, imo.
  - ryanjshaw 5y ago
    Are you thinking of Cloudflare Workers Sites? You can definitely do logging like that with Workers. But my understanding is that Workers Sites have been superseded [1] by Pages, and there are no logs for this new product other than at the Enterprise level. [1] Documentation for Workers Sites at https://workers.cloudflare.com/sites https://workers.cloudflare.com/sites redirects to Pages
    - the_duke 5y ago
      You can assign regular workers to your sites hosted with Pages. The workers act as a middleware. You can `fetch` the static content and then do any processing/logging you want.
- d4nt 5y ago
  I've also had the occasional issue with serverless platforms. Not to do with Google indexing, but I had a similar sensation: "well now we're just completely stuck". When something doesn't work the way it should, the whole premise of "you don't have to think about servers" quickly becomes "no, you're not allowed to see the servers" and its horrible. These days I try to make the case at work for targeting containers and using the cloud platforms' container hosting tools instead.
neximo64 5y ago
What is this exactly, a bit of a poor page/not developer friendly so who is the audience, people who use excel? Is it SQL? Key store? No examples just trying to get lots of catchy phrases/buzzwords on.
- tudorg 5y ago
  Yes, I admit the website is a bit high level. That is mostly because we're not yet quite ready to launch, we will have proper documentation once we do.
  - code_biologist 5y ago
    At risk of being a brusque, why are you posting this then? It's a waste of time. If you had posted rough technical details of your initial offering you could have gotten real feedback before the launch of the product itself.
    - tudorg 5y ago
      I understand. We didn't post this ourselves, however a Techcrunch article about our funding round was posted today, and then someone else has posted this to HN.
tudorg 5y ago
Hi everyone, I am Tudor, CTO at Xata. Thanks for posting the link! We’re not yet ready for you to try it out, so it is maybe a bit too early to show it to this community. We will probably do a proper Show HN post once we are ready. Nevertheless we are thrilled to be here! :) For a few more details, see also our first blog post: https://www.xata.io/blog/hello-world/ https://www.xata.io/blog/hello-world/ We’re building a database service that is extremely easy to use (think of Airtable and its rich data types), yet providing the usual guarantees offered by traditional databases (consistency, transactions, constraints). We also have a built-in analytics and search engine, so you no longer have to copy the data from the DB to the search engine. There are other features that we’re really excited about (native branches, easy-to-use joins, caching, security rules), but we’re going to be able to talk a lot more once we’re ready for users. We’d love your feedback and if you’d be interested to work with us, please don’t hesitate to reach out.
- karimf 5y ago
  Very excited to see someone is tackling this problem. With the rise of serverless, it's super easy for an average developer or a new developer to build a backend. It's also super easy to deploy a front-end with Vercel, Netlify, or GitHub Pages. But I believe there's no easy solution for the database part yet. For most people, the most common choice is to use Firebase. Firebase offers services that people can use to build a "full-stack" application, from front-end service, serverless function as a backend, and a database. It's very tempting to use Firebase for a new developer. Now we also see the rise of Supabase, that offers an alternative to Firebase, that's built on top of open source projects. I believe in the future, it should be the norm to include database to an application with just a single env variable, without worrying about anything else.
  - nicoburns 5y ago
    > I believe in the future, it should be the norm to include database to an application with just a single env variable, without worrying about anything else. I some how doubt it. Firebase (and these kind of proprietary services in general) are a complete nightmare for larger production apps: limited query power, doesn't actually scale like it claims it does, difficult to test locally, etc. A traditional backend with a Postgres database and plain REST APIs using hosted on something like Heroku is much simpler.
konradkpl 5y ago
Looks promising. Platforms such as Netlify have greatly simplified the development of web applications. Recently I tried Netlify forms - child's play, in 4 minutes I had a working form with e-mail notification. All I had to do was create the correct HTML code. If they simplify the use of the database in simple projects in a similar way, it will be a great success.
- tudorg 5y ago
  Thanks! That's indeed the idea.
topicseed 5y ago
Seems like a future alternative to Firestore with an analytics engine, and a Spreadsheet-like UI.
eloycoto 5y ago
I'm super excited about this!
dabeeeenster 5y ago
Looks interesting! What is a "connectionless api"? I have not heard that phrase before? Can I use this instead of DynamoDB global tables? Where does it sit RE CAP?
- tudorg 5y ago
  > What is a "connectionless api"? I have not heard that phrase before? It just means that we offer an HTTP based API, so you don't need to do connection pooling. This is convenient for serverless apps, because they can't hold onto a connection. > Can I use this instead of DynamoDB global tables? Where does it sit RE CAP? Yes, we do want to be an alternative to DynamoDB global tables, but with a more flexible data model. The in-region writes/reads are consistent, the replication to the analytics/search engine as well as replicating between regions are eventually consistent.
  - dabeeeenster 5y ago
    Thanks for the reply. Feedback would definitely be to include this sort of technical detail on the site! Would love to dive into the details of how you guys are doing DNS resolution (latency based routing?) how many regions you have, if we have control over how many regions we replicate to etc. We are building a global edge API for https://flagsmith.com/ https://flagsmith.com/ and this is a great candidate for a data platform for us.
sharmin123 5y ago
Your phone can never be hacked? Think again: https://www.hackerslist.co/your-phone-can-never-be-hacked-think-again/ https://www.hackerslist.co/your-phone-can-never-be-hacked-th...
munchor 5y ago
Nice to see more possibilities in this space, database branches look particularly interesting and useful for the JAMstack world! That's definitely something that's hard to manage in CI/CD for JAMstack apps. It's also interesting to see more database services support HTTP APIs. SingleStore recently launched support for an HTTP API as well (https://docs.singlestore.com/managed-service/en/reference/http-api.html https://docs.singlestore.com/managed-service/en/reference/ht...). I think most database services should follow suit due to how popular serverless frameworks are becoming, and the need to have connectionless pooling. I have some questions such as: * Will all these HTTP APIs support most authentication methods already used by these database services? Or will they likely only support some sort of API token based auth? * Could HTTP caching ever be useful for these? Or just internal database caching? * Is security a concern any more so than with regular TCP connections? * Will all your typical ORMs "just work"? I think the answer is "yes", but there are some more modern ORMs that I wouldn't be too sure about (e.g. Prisma). Disclaimer: I work at SingleStore, which is a database service for data-intensive apps as well.
mdtrooper 5y ago
Ok, amazon serverless, not the true serverless.
gigatexal 5y ago
Nice landing page but very little in terms of how this actually works. Also no pricing so I can't anticipate how much this might cost me. Speaking of pricing: any chance there wil lbe a free-forever tier?
asdev 5y ago
Why would anyone use this as opposed to the DB offerings provided within the respective serverless cloud platforms? I think cloud platforms also charge more for egress to 3rd party services as well
zerop 5y ago
I had recently come across postgrest.. API on postgre SQL. Is this on similar lines (obviously xata looks more robust, feature rich than postgrest, but are on the same lines?)
boomskats 5y ago
I know this is petty and arguably irrelevant, but I hope you find the feedback useful. The spacing and alignment on your some of your visuals is sloppy and distracted me from your otherwise well put together messaging. The row level security graphic is the one that stands out the most in this regard.
- tudorg 5y ago
  Thanks, definitely valuable feedback! I see what you mean about the security image, we're fixing it now.
elitan 5y ago
Maybe I'm in my bubbel since I'm the founder of another "database / backend" as a service company (https://nhost.io https://nhost.io) but it's been a lot of new startups in this space which is fun to see. - Firebase - Nhost - AppSync - Supabase - 8base - AppWrite - Xata I like your focus on workflow, PRs, branching etc. I think it's going to be key to solve end-to-end problems for developers in the future. Congratulation on the raise and I'm excited to test our your service once it's launched. Good Luck!
- rishav_sharan 5y ago
  Adding two more to the list; - FaunaDB - Macrometa
mellowhype 5y ago
I've been waiting for something like this since I discovered Publii CMS
mrweasel 5y ago
It’s a database, an analytics tool, a search engine and a spreadsheet. Sorry, I just felt like I was watching late night TV shopping. As a product this makes some sense, but as with most new products, on-prem is ignored. We’re moving more customers off public cloud than we help launch new product on cloud offerings. The current situation in the EU makes these SaaS offerings almost irrelevant. Companies and governments are very reluctant in picking any cloud services.
- nkmnz 5y ago
  I second the last paragraph. It’s a NIGHTMARE to sell SaaS to European Govs if it’s hosted with a US company (except, of course, you are one of said US companies. Then you can sell whatever you want. Yes, it’s really strange).
tluyben2 5y ago
How big is the market for this I wonder? I run a product like it for free for 15 years now and while it has 100000s users and 1000s of companies running off it, there are only a few who would not skip to self hosted/cloud hosted instead of paying us. We are fully free (no pricing page) but we talk to our users and some sponsor us (just send some money to PayPal willy nilly when they feel like it) ; most of them say they like our solution better than others however they would just pop their own server if we would charge. Seeing how much excitement this brings, I guess I should try adding a pricing page and calling their bluff.
- brightball 5y ago
  Better to have a few paying customers than unlimited free. Seems like you just need to define a free tier and figure out where the cutoff is for more serious use.
- bikamonki 5y ago
  I use Firebase. Most projects don't need more than the free tier. A few are on the paid tier; however, the monthly cost is covered by revenue and way below the cost of running our own infra. I would not switch services/host a backend just to save a few hundred bucks. Call their bluff.
- nkmnz 5y ago
  Would you mind proving a Link? I’d like to sign up before you introduce pricing :P
  - tluyben2 5y ago
    I did not want to take away from this 'launch' ; We are redoing the front-end (as it looks 15 y/o) and are almost done redoing it. We integrated a lot of to get a bit more modern in that version and we have an API now that allows x origin so it can serve serverless. For the API you will have to email: have 1000+ companies using it, however, I did not advertise it until the site has been redone. It is mobile unfriendly but it was never meant to do that. My main goal, because I use it for everything, is speed: entry speed, reaction speed etc. So apologies to xata, I do not see myself as a competitor, but here is the link [0]. Just email me for the new version, the api and cors. [0] https://flexlists.com https://flexlists.com
wizzard0 5y ago
Well, congrats with the launch! As for "too early" - well, yes. Sounds good in theory, except there's absolutely no detail from both a developer or a founder's perspective. That is, can't provide feedback when there's nothing apart from the landing page to evaluate :/ Some preliminary API docs maybe? Those should spark a discussion pretty well imho
bdcravens 5y ago
I think the spreadsheet view isn't that big as big a deal as its position on the page suggests. The branching however, is actually pretty awesome. On a 24" screen, the features are all below the fold. Above the fold is taken up by a huge hero section that looks nice, but is taken up by a huge animation and a header that's mostly buzzwords. You do have a paragraph with some good info, but really doesn't catch my eye. I literally had to scroll down 2-3 screen heights to get to the first feature that stood out to me (and that paragraph I mentioned didn't even feature it) Double down on what sets you apart.
tevon 5y ago
This seems awesome! I'm most excited about the support for "better" migrations and interaction via a GUI. While we're not strictly Jamstack, I could absolutely see us using this as an auxiliary to our primary production database, i.e. for prototyping or launching new features rapidly without having to migrate the full prod schema. To use this alongside our production dbs, my wishlist would be: 1. A way to "eject" to raw postgres/etc, gives me peace of mind that if things don't work out, I can still take my pg_dump and go home. 2. Maybe a Prisma.io integration?! Would allow it to play nicely with out non-serverless backend, while ALSO catering to serverless applications. Just some thoughts!

185 points by madmax108 5y ago

CaptainJustin 5y ago

Looks similar to Firestore - identity aware, serverless, pay as you use.

nkmnz 5y ago

Looks similar to supabase, plus analytics.

ryanjshaw 5y ago

Bitter tale of a serverless experience: Serverless is great until you spend weeks building something in Cloudflare Pages and Workers, then add it to Google and... Google claims your site doesn't exist. Search Console Live Test gives a vague 'General HTTP Error', Rich Results Test says the 'page is unavailable', Ad Words says 'Destination not working'. Bing indexes your site with no problems, and every device you and your friends own works fine, every uptime tester on the planet says you're good. Cloudflare shows no firewall events and logs are a 'contact us for pricing' Enterprise-only feature. So what do you do - if Google thinks your serverless site doesn't exist, and you can't debug it because it's all magic? You can't do anything. Back to conventional hosting you go.

the_duke 5y ago
You can use any external logging service that has an HTTP API. Not ideal, but it works fine. I'm doing this with Cloudflare workers by sending access logs to a self hosted Matomo analytics and error logs to Loggly. But in general, Cloudflare isn't really suitable yet for general app development. They need a lot of additional services for that to become viable, imo.
- ryanjshaw 5y ago
  Are you thinking of Cloudflare Workers Sites? You can definitely do logging like that with Workers. But my understanding is that Workers Sites have been superseded [1] by Pages, and there are no logs for this new product other than at the Enterprise level. [1] Documentation for Workers Sites at https://workers.cloudflare.com/sites https://workers.cloudflare.com/sites redirects to Pages
  - the_duke 5y ago
    You can assign regular workers to your sites hosted with Pages. The workers act as a middleware. You can `fetch` the static content and then do any processing/logging you want.
d4nt 5y ago
I've also had the occasional issue with serverless platforms. Not to do with Google indexing, but I had a similar sensation: "well now we're just completely stuck". When something doesn't work the way it should, the whole premise of "you don't have to think about servers" quickly becomes "no, you're not allowed to see the servers" and its horrible. These days I try to make the case at work for targeting containers and using the cloud platforms' container hosting tools instead.

neximo64 5y ago

What is this exactly, a bit of a poor page/not developer friendly so who is the audience, people who use excel? Is it SQL? Key store? No examples just trying to get lots of catchy phrases/buzzwords on.

tudorg 5y ago
Yes, I admit the website is a bit high level. That is mostly because we're not yet quite ready to launch, we will have proper documentation once we do.
- code_biologist 5y ago
  At risk of being a brusque, why are you posting this then? It's a waste of time. If you had posted rough technical details of your initial offering you could have gotten real feedback before the launch of the product itself.
  - tudorg 5y ago
    I understand. We didn't post this ourselves, however a Techcrunch article about our funding round was posted today, and then someone else has posted this to HN.

tudorg 5y ago

Hi everyone, I am Tudor, CTO at Xata. Thanks for posting the link! We’re not yet ready for you to try it out, so it is maybe a bit too early to show it to this community. We will probably do a proper Show HN post once we are ready. Nevertheless we are thrilled to be here! :) For a few more details, see also our first blog post: https://www.xata.io/blog/hello-world/ https://www.xata.io/blog/hello-world/ We’re building a database service that is extremely easy to use (think of Airtable and its rich data types), yet providing the usual guarantees offered by traditional databases (consistency, transactions, constraints). We also have a built-in analytics and search engine, so you no longer have to copy the data from the DB to the search engine. There are other features that we’re really excited about (native branches, easy-to-use joins, caching, security rules), but we’re going to be able to talk a lot more once we’re ready for users. We’d love your feedback and if you’d be interested to work with us, please don’t hesitate to reach out.

karimf 5y ago
Very excited to see someone is tackling this problem. With the rise of serverless, it's super easy for an average developer or a new developer to build a backend. It's also super easy to deploy a front-end with Vercel, Netlify, or GitHub Pages. But I believe there's no easy solution for the database part yet. For most people, the most common choice is to use Firebase. Firebase offers services that people can use to build a "full-stack" application, from front-end service, serverless function as a backend, and a database. It's very tempting to use Firebase for a new developer. Now we also see the rise of Supabase, that offers an alternative to Firebase, that's built on top of open source projects. I believe in the future, it should be the norm to include database to an application with just a single env variable, without worrying about anything else.
- nicoburns 5y ago
  > I believe in the future, it should be the norm to include database to an application with just a single env variable, without worrying about anything else. I some how doubt it. Firebase (and these kind of proprietary services in general) are a complete nightmare for larger production apps: limited query power, doesn't actually scale like it claims it does, difficult to test locally, etc. A traditional backend with a Postgres database and plain REST APIs using hosted on something like Heroku is much simpler.

konradkpl 5y ago

Looks promising. Platforms such as Netlify have greatly simplified the development of web applications. Recently I tried Netlify forms - child's play, in 4 minutes I had a working form with e-mail notification. All I had to do was create the correct HTML code. If they simplify the use of the database in simple projects in a similar way, it will be a great success.

tudorg 5y ago
Thanks! That's indeed the idea.

topicseed 5y ago

Seems like a future alternative to Firestore with an analytics engine, and a Spreadsheet-like UI.

eloycoto 5y ago

I'm super excited about this!

dabeeeenster 5y ago

Looks interesting! What is a "connectionless api"? I have not heard that phrase before? Can I use this instead of DynamoDB global tables? Where does it sit RE CAP?

tudorg 5y ago
> What is a "connectionless api"? I have not heard that phrase before? It just means that we offer an HTTP based API, so you don't need to do connection pooling. This is convenient for serverless apps, because they can't hold onto a connection. > Can I use this instead of DynamoDB global tables? Where does it sit RE CAP? Yes, we do want to be an alternative to DynamoDB global tables, but with a more flexible data model. The in-region writes/reads are consistent, the replication to the analytics/search engine as well as replicating between regions are eventually consistent.
- dabeeeenster 5y ago
  Thanks for the reply. Feedback would definitely be to include this sort of technical detail on the site! Would love to dive into the details of how you guys are doing DNS resolution (latency based routing?) how many regions you have, if we have control over how many regions we replicate to etc. We are building a global edge API for https://flagsmith.com/ https://flagsmith.com/ and this is a great candidate for a data platform for us.

sharmin123 5y ago

Your phone can never be hacked? Think again: https://www.hackerslist.co/your-phone-can-never-be-hacked-think-again/ https://www.hackerslist.co/your-phone-can-never-be-hacked-th...

munchor 5y ago

Nice to see more possibilities in this space, database branches look particularly interesting and useful for the JAMstack world! That's definitely something that's hard to manage in CI/CD for JAMstack apps. It's also interesting to see more database services support HTTP APIs. SingleStore recently launched support for an HTTP API as well (https://docs.singlestore.com/managed-service/en/reference/http-api.html https://docs.singlestore.com/managed-service/en/reference/ht...). I think most database services should follow suit due to how popular serverless frameworks are becoming, and the need to have connectionless pooling. I have some questions such as: * Will all these HTTP APIs support most authentication methods already used by these database services? Or will they likely only support some sort of API token based auth? * Could HTTP caching ever be useful for these? Or just internal database caching? * Is security a concern any more so than with regular TCP connections? * Will all your typical ORMs "just work"? I think the answer is "yes", but there are some more modern ORMs that I wouldn't be too sure about (e.g. Prisma). Disclaimer: I work at SingleStore, which is a database service for data-intensive apps as well.

mdtrooper 5y ago

Ok, amazon serverless, not the true serverless.

gigatexal 5y ago

Nice landing page but very little in terms of how this actually works. Also no pricing so I can't anticipate how much this might cost me. Speaking of pricing: any chance there wil lbe a free-forever tier?

asdev 5y ago

Why would anyone use this as opposed to the DB offerings provided within the respective serverless cloud platforms? I think cloud platforms also charge more for egress to 3rd party services as well

zerop 5y ago

I had recently come across postgrest.. API on postgre SQL. Is this on similar lines (obviously xata looks more robust, feature rich than postgrest, but are on the same lines?)

boomskats 5y ago

I know this is petty and arguably irrelevant, but I hope you find the feedback useful. The spacing and alignment on your some of your visuals is sloppy and distracted me from your otherwise well put together messaging. The row level security graphic is the one that stands out the most in this regard.

tudorg 5y ago
Thanks, definitely valuable feedback! I see what you mean about the security image, we're fixing it now.

elitan 5y ago

Maybe I'm in my bubbel since I'm the founder of another "database / backend" as a service company (https://nhost.io https://nhost.io) but it's been a lot of new startups in this space which is fun to see. - Firebase - Nhost - AppSync - Supabase - 8base - AppWrite - Xata I like your focus on workflow, PRs, branching etc. I think it's going to be key to solve end-to-end problems for developers in the future. Congratulation on the raise and I'm excited to test our your service once it's launched. Good Luck!

rishav_sharan 5y ago
Adding two more to the list; - FaunaDB - Macrometa

mellowhype 5y ago

I've been waiting for something like this since I discovered Publii CMS

mrweasel 5y ago

It’s a database, an analytics tool, a search engine and a spreadsheet. Sorry, I just felt like I was watching late night TV shopping. As a product this makes some sense, but as with most new products, on-prem is ignored. We’re moving more customers off public cloud than we help launch new product on cloud offerings. The current situation in the EU makes these SaaS offerings almost irrelevant. Companies and governments are very reluctant in picking any cloud services.

nkmnz 5y ago
I second the last paragraph. It’s a NIGHTMARE to sell SaaS to European Govs if it’s hosted with a US company (except, of course, you are one of said US companies. Then you can sell whatever you want. Yes, it’s really strange).

tluyben2 5y ago

How big is the market for this I wonder? I run a product like it for free for 15 years now and while it has 100000s users and 1000s of companies running off it, there are only a few who would not skip to self hosted/cloud hosted instead of paying us. We are fully free (no pricing page) but we talk to our users and some sponsor us (just send some money to PayPal willy nilly when they feel like it) ; most of them say they like our solution better than others however they would just pop their own server if we would charge. Seeing how much excitement this brings, I guess I should try adding a pricing page and calling their bluff.

brightball 5y ago
Better to have a few paying customers than unlimited free. Seems like you just need to define a free tier and figure out where the cutoff is for more serious use.
bikamonki 5y ago
I use Firebase. Most projects don't need more than the free tier. A few are on the paid tier; however, the monthly cost is covered by revenue and way below the cost of running our own infra. I would not switch services/host a backend just to save a few hundred bucks. Call their bluff.
nkmnz 5y ago
Would you mind proving a Link? I’d like to sign up before you introduce pricing :P
- tluyben2 5y ago
  I did not want to take away from this 'launch' ; We are redoing the front-end (as it looks 15 y/o) and are almost done redoing it. We integrated a lot of to get a bit more modern in that version and we have an API now that allows x origin so it can serve serverless. For the API you will have to email: have 1000+ companies using it, however, I did not advertise it until the site has been redone. It is mobile unfriendly but it was never meant to do that. My main goal, because I use it for everything, is speed: entry speed, reaction speed etc. So apologies to xata, I do not see myself as a competitor, but here is the link [0]. Just email me for the new version, the api and cors. [0] https://flexlists.com https://flexlists.com

wizzard0 5y ago

Well, congrats with the launch! As for "too early" - well, yes. Sounds good in theory, except there's absolutely no detail from both a developer or a founder's perspective. That is, can't provide feedback when there's nothing apart from the landing page to evaluate :/ Some preliminary API docs maybe? Those should spark a discussion pretty well imho

bdcravens 5y ago

I think the spreadsheet view isn't that big as big a deal as its position on the page suggests. The branching however, is actually pretty awesome. On a 24" screen, the features are all below the fold. Above the fold is taken up by a huge hero section that looks nice, but is taken up by a huge animation and a header that's mostly buzzwords. You do have a paragraph with some good info, but really doesn't catch my eye. I literally had to scroll down 2-3 screen heights to get to the first feature that stood out to me (and that paragraph I mentioned didn't even feature it) Double down on what sets you apart.

tevon 5y ago

This seems awesome! I'm most excited about the support for "better" migrations and interaction via a GUI. While we're not strictly Jamstack, I could absolutely see us using this as an auxiliary to our primary production database, i.e. for prototyping or launching new features rapidly without having to migrate the full prod schema. To use this alongside our production dbs, my wishlist would be: 1. A way to "eject" to raw postgres/etc, gives me peace of mind that if things don't work out, I can still take my pg_dump and go home. 2. Maybe a Prisma.io integration?! Would allow it to play nicely with out non-serverless backend, while ALSO catering to serverless applications. Just some thoughts!