Been using Riza for the past few months at our startup for executing code generated by GPT4.
We use it for local dev, running prompt eval, and running code in prod.
- It was very fast to setup - it took us just a few minutes to execute our first function call.
- Multiple languages support - we use both JS and Python for code generated by LLM , Riza works great with both languages out of the box.
- No cold start - this is important because latency matters in our product.
- No infra management - even if we use AWS lambda or similar serverless product we felt like we still needed to a bunch of setup to make sure its fast + secure.
Been using Riza for the past few months at our startup for executing code generated by GPT4.
We use it for local dev, running model eval (when changing prompts), in CI and production work loads.
- It's the easiest to setup. It took us just a few minutes to execute our first function call.
- Multiple languages support - we use both JS and Python for code generated by LLM , Riza works great with both out of the box.
- No cold start - this is important because latency matters in our product.
- No infra management - even if we use AWS lambda or similar serverless product we felt like we still needed to a bunch of setup to make sure its fast + secure.
My team has been using this in production for the past 6 months - this is the best way to write Graphql server in Typescript by far and I have tried it all
Like my sibling said, probably as a next_public environmental variable.
They probably were doing fetch requests for the dashboard client side. I wonder if they had the entire db url stored as a next_public_db_url. If that’s really irresponsible, and pretty easy to catch in development, at least for the pages router stuff. Maybe a little less so obvious for ssr pages.
I haven’t tried a lot of the new app_router, maybe there’s a lot more mixing of client and server side stuff there. Regardless, you should be auditing your environmental variables!
I have no inside info, but it sounds like the key was inadvertently bundled into the client-side code. This could happen when using web frameworks that do both client-side and server-side rendering, if one of your client-side files imports something from a file that is supposed to be server-only, and contains the API key environment variable.
Some frameworks automatically detect this and fail to build if you do it, but apparently not all of them.
Google tables is similar to Airtable, they are proprietary databases. You cannot query them and interface with them easily from another application like a regular database.
Retool Database has that friendly table UI but also give you the full query capability via SQL (we even give you the Postgres connection string that let you connect to it externally with your favorite tool).
For self-hosted customers, Retool Database operates more like a front-end for your own DB (though we do require specific versions of Postgres for it all to work smoothly). Docs here: https://docs.retool.com/docs/retool-database-self-hosted
Spreadsheets are often used as “poor man’s databases”—they’re quick to get started, but fall apart when you need data integrity, validation, and the ability to query/filter data.
This is why I am so excited about this launch - Retool Database gives you the power of Postgres with the “getting started” speed of a spreadsheet. No setup required.
We've also spent a lot of time on the UI for interacting with the database as well. You can create and edit tables, columns, and rows quickly without writing SQL. You should be able to get the same speed of iteration as spreadsheets, but you are also starting from the get-go that can handle the increasing complexity of your data and scale much better with app development.
We’re giving you 5GB free storage for the first year + connection strings so you can access your data outside Retool.
Lots of learnings as we built this—happy to answer any question you have!
I just tried using this, and I'm afraid I don't think it's as easy as a spreadsheet. I don't even understand it!
I started things off, just kept clicking "yes, yes", made a database called "shopping", and now...
I just seem to have an empty page? There is 'id' and 'created_at'.
I can "Add row", which just let's me specify "id", which has to be a number.
There is a button marked "fields", which tells me my fields are "id" and "created_at", but doesn't seem to have any way to add new fields.
I then, at my last guess, tried doing "import CSV". It asks me to choose a field for each column. I don't have any fields yet. I want to make some. Why can't I pick "this should be a new field"?
Anyway, import CSV just tells me 'Syntax error at or near ")"' when I try running it. There are no close brackets in my CSV, so no idea where that is coming from.
thanks, I've been looking at all the spreadsheet-over-a-database projects i can find, and hadn't discovered APITable yet! I have a very specific requirement (app where I want a few views to be collaborative spreadsheets and the rest more freeform html based pages reading from the same tables) and so far none of the popular projects has been quite suitable. (basetool might have but it's dead :()
We agree! The UI can be really helpful to make quick changes to schema, data, etc. You can’t run the UI without a Retool account though. We have a self-hosted Retool that works with your own Postgres database that you connect to Retool. Docs here: https://docs.retool.com/docs/retool-database-self-hosted
We don't do anything automatic like that (yet?), you will have to add indexes manually.
But I would have to say - modern day databases are so fast that you probably won't notice the performance of adding indexes until at least 100k+ rows in a table and/or you have very high read throughput on that particular table.
You'll see a performance benefit way before 100k rows depending on the size of each row, especially with sorting. It might save you guys a ton of CPU hosting wise, depending on how this all works, to track slow queries and auto add indexes. Way worth the write overhead in most cases.
It’s likely that most of their customers would only have a few hundred or thousand rows where indexing may not actually matter after all. Otherwise I’m sure they would’ve prioritized it.
Historically, Retool has been known as a fast way to build frontend UIs for your existing internal backends and APIs.
However, if you don’t already have a place to store your application data, you’d have to set that up elsewhere (AWS/Heroku) before you can leverage Retool’s UI builder—which introduces a lot of friction for you to get started building on Retool.
Because of this, we believe that a lot of internal tools aren’t built because there isn’t a fast way to store data for them. So today, we’re excited to announce the first product that lets you store and edit your app data inside retool: Retool Database. It is backed by the battle-tested PostgreSQL database and comes with an easy-to-use spreadsheet UI for managing its schema and data.
With Retool Database, you can:
- Create full stack apps in Retool in less than 2 minutes
- Build your internal tools on top of a SQL database right away, not Google Sheets
- Augment your production data with a secondary database that is used only for internal tools
Historically, Retool has been known as a fast way to build frontend UIs for your existing internal backends and APIs.
However, if you don’t already have a place to store your application data, you’d have to set that up elsewhere (AWS/Heroku) before you can leverage Retool’s UI builder—which introduces a lot of friction for you to get started building on Retool.
Because of this, we believe that a lot of internal tools aren’t built because there isn’t a fast way to store data for them. So today, we’re excited to announce the first product that lets you store and edit your app data inside retool: Retool Database. It is backed by the battle-tested PostgreSQL database and comes with an easy-to-use spreadsheet UI for managing its schema and data.
With Retool Database, you can:
- Create full stack apps in Retool in less than 2 minutes
- Build your internal tools on top of a SQL database right away, not Google Sheets
- Augment your production data with a secondary database that is used only for internal tools
We use it for local dev, running prompt eval, and running code in prod.
- It was very fast to setup - it took us just a few minutes to execute our first function call.
- Multiple languages support - we use both JS and Python for code generated by LLM , Riza works great with both languages out of the box.
- No cold start - this is important because latency matters in our product.
- No infra management - even if we use AWS lambda or similar serverless product we felt like we still needed to a bunch of setup to make sure its fast + secure.
Congrats on launching!