Recent submissions

Comment · 2 years ago
You can self-host here: https://retool.com/self-hosted. Most people deploy it as a docker container on an EC2 instance but there’s various options
Comment · 2 years ago
Comment · 2 years ago
Sorry just updated!
Comment · 2 years ago
Comment · 2 years ago
Here are the docs: https://docs.retool.com/apps/forms. Just added a link to them from the landing page. Agree we should also add a quick demo to the landing page
Comment · 2 years ago
Hi all, engineer who worked on forms @ Retool here. Excited to get HN’s feedback on a new product I’ve been working on: Retool Forms. There are a ton of form builders out there (e.g. Typeform, Google Forms, Airtable Forms, etc.) and honestly we weren’t really looking to build another one. But as a developer, I wanted my data in my database, not in another SaaS app (which probably has a shoddy API, like every example I listed above). Surprisingly, the only way to build a form on top of my database was by a) building my own backend (probably via node), and b) building my own frontend (probably via React, and then maybe via formik). There was no “one click” form-on-top-of-my-database tool available.

So we decided to build a form builder. It allows you to:

1. Send data directly to your database (Postgres in our case), your data warehouse, or wherever else you want it

2. Write JS almost anywhere on the front-end, including libraries like moment and lodash, for custom validations, conditional logic, and data parsing

3. Run any arbitrary code in form submission (or validation), via our Workflows product

4. Store it in our database (where we give you a connection string), or your own database

5. Self-host it in your own VPC

And it’s free with no arbitrary limits on the number of users, forms or submissions.

I’m hoping to ship a bunch more features like integration to any REST API, more styling options, etc. If you have any feedback please let me know!

Comment · 2 years ago
we'd love to make the migration as easy as possible and would definitely be open to building an import tool. In the meantime if you're migrating feel free to email me at jamie at retool.com and I'd be happy to help import
Comment · 3 years ago
Thanks for the feedback. We're currently working on customization with the url parser and trimming headers/etc makes a lot of sense. If you're able to share more about your use case (jamie AT retool DOT com), happy to get it tuned on your dataset
Comment · 3 years ago
Thanks! Yes agree this is very important. We do show references from Retool Vectors out of the box, so you can see what embeddings were used to generate a response. If it'd be helpful I can walk you through a few internal Q&A bot examples which display references - jamie AT retool DOT com
Comment · 3 years ago
Today we use a cosine similarity search but we're planning to integrate with more vector databases and allow you to customize the search logic soon. Is there a particular query method you're looking for?
Comment · 3 years ago
I checked in with an engineer who’s focussing on app performance. You're right that this screen should not be 6MB. One part of the bloat is due to our webpack configuration. In lighthouse, you can see that >50% of the app.js file is unused for login. Most of this is actually used for the app after login.

We’re working on getting this down significantly but, that being said, the login page isn’t our highest priority. It’s the first thing customers see, but >99% of the time, they’ll already be logged in and navigate straight to the apps page, or a specific Retool app. For these pages, we’ve:

1. re-written our core runtime to avoid excessive message passing with iframes (up to 75% faster page load for slowest apps)

2. parallelized resource fetching with JS execution

3. cached app graph information in IndexedDB

4. tweaked webpack chunking strategy to avoid very small JS/CSS chunks

5. optimized resource fetching to avoid over fetching

Hope that’s helpful context. Definitely let me know if you have thoughts/other ideas

Comment · 3 years ago
Yes working on adding llama2 and AWS bedrock support right now for open source models. But we also want to let users bring their own models - is there a specific model you're looking for?

Who knows longer-term I'd love to help users fine-tune their own models on llama2/gpt-3.5!

Comment · 3 years ago
Excited to already see some great open source projects in this space (Langchain, Llamaindex, Axilla, etc) many of which we're exploring using for this project.

Just to be clear Retool Vectors is completely free (we're even taking on the LLM costs). We put the embeddings in a free postgres DB (and soon other open source vector DB providers) and give you the connection string so you can take it anywhere

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton