Yes, that is our target market too. We don't think people will be building airbnb.com (say) in Retool, but not all software is like that. (In fact, we think most software is probably just CRUD apps, haha.)
We don't manage the database for customers; we instead connect to your data (whether it's behind an API or database). That was one of the first decisions we made — as a developer, if my data is already in postgres, I certainly wouldn't want to have to ETL / sync it anywhere. :)
Use cases: probably our most common use case is a CRM for a consumer company (e.g. Doordash). The reason that is so popular is because if you have (say) 1M orders a day, you aren't able to put that data in Salesforce anymore. And so the only way for you to manage all that stuff is by building custom software (instead of buying anything off the shelf). Retool is good at that: you can build CRUD-y screens very quickly. Retool, today, is not good at making everything pixel perfect (e.g. we have a grid layout engine, and you can't break out of the grid), but a CRM doesn't need to be pixel perfect.
Salesforce has a limitation of 50,000 records for any operation. 1,000,000 records for read-only operations.
If you go beyond that, you talk to Salesforce about it, because they can make adjustments for you - and you can likely afford it.
Salesforce will bend over backwards and make internal engineering changes for large customers, including adjusting governor limits, dedicating hardware and running backend queries directly for the customer.
Having any object / table in Salesforce > 1M rows is somewhat exceptional; doing that daily (using standard Salesforce capabilities) is off the charts -- just moving amount of data into Salesforce within a 24 hr window is questionable. Its built for B2B, where the data volumes are much lower, and conversely the kinds of operations / workflows you want to do on that data are typically more complex.
We don't manage the database for customers; we instead connect to your data (whether it's behind an API or database). That was one of the first decisions we made — as a developer, if my data is already in postgres, I certainly wouldn't want to have to ETL / sync it anywhere. :)
Use cases: probably our most common use case is a CRM for a consumer company (e.g. Doordash). The reason that is so popular is because if you have (say) 1M orders a day, you aren't able to put that data in Salesforce anymore. And so the only way for you to manage all that stuff is by building custom software (instead of buying anything off the shelf). Retool is good at that: you can build CRUD-y screens very quickly. Retool, today, is not good at making everything pixel perfect (e.g. we have a grid layout engine, and you can't break out of the grid), but a CRM doesn't need to be pixel perfect.