11–20 of 39 posts
The landing page doesn't show a link to your GitHub. Despite mentioning "self-hostable", I genuinely thought it was closed-sourced. I doubt first-time users will trust a random tool and grant it database-level access with a curl command.
> 2. BI dashboards(we removed spend on tableau, retool and appsmith) Can you explain this in more detail? You saying that DeepSQL can create BI dashboards that makes Tableau and friends redundant -- are you talking about analytics dashboards consumed by business teams or more like db ops dashboards used by backend teams? Does the user prompt the agent for them, or does it build dashboards that it infers are needed?
Where does this number come from? It feels completely arbitrary.
> cut database costs by 40% Where does this number come from? It feels completely arbitrary.
We worked with 6 YC companies who are running on Aurora postgres and worked through the inefficiencies of workloads - too many indexes (in some cases almost every column is indexed), over indexing significantly increases I/O ops (writes), this hidden costs are enormous for fully managed services like Aurora. In all these cases, we could safely come up with a plan to cut down their DB spend by more than 40%.
Is this an open source tool? Is it something we have to pay for? The site really doesn't tell me what I should be expecting.
I am happy to get connected over email venkat@deepsql.ai and share more details on pricing and deployment help.
> cut database costs by 40% Where does this number come from? It feels completely arbitrary.
We did cut our overall DB spend by more than 3x. Our $9K spend drops to $3k - indexes not kicking in, rapid growth of log tables and schema bloat were the culprits. Also, we removed the retool and appsmith licenses, another $2k savings. We worked with 6 YC companies who are running on Aurora postgres and worked through the inefficiencies of workloads - too many indexes (in some cases almost every column is indexed),…
Personally, I will instantly distrust a new product claiming an exact number of 40% savings -- not even "up to 40%" or "over 40%", which would still be misleading, but less weird than claiming exactly 40%. Especially in the second line of the homepage, without any supporting link or information.
> we removed the retool and appsmith licenses, another $2k savings.
These aren't DB-specific tools though? Why would this count towards the savings?
> 6 YC companies [...] in some cases almost every column is indexed
If your savings math is based on very early-stage startups who made horrendously bad indexing mistakes, honestly that would reduce my trust even further. That said, I'm definitely not the audience for your product.
Earlier quoted context omitted.
We did cut our overall DB spend by more than 3x. Our $9K spend drops to $3k - indexes not kicking in, rapid growth of log tables and schema bloat were the culprits. Also, we removed the retool and appsmith licenses, another $2k savings. We worked with 6 YC companies who are running on Aurora postgres and worked through the inefficiencies of workloads - too many indexes (in some cases almost every column is indexed),…
My point is that the number will entirely vary for each user, depending on how many poor DB-related infra decisions they've made. Some users may save 99%, others may save almost nothing, right? So why say 40% here? Where did this number come from? Personally, I will instantly distrust a new product claiming an exact number of 40% savings -- not even "up to 40%" or "over 40%", which would still be misleading, but less…
Our goal was to tell a convincing story with case studies. However, you are right on many dimensions that this number means nothing for many optimized scenarios.
This is an interesting product. Any comparison with other DBA tools? There are many tools can fix the slow queries, based on rule+statistics.
Deepsql doesn't require any predefined rules + stats, nor you need a DBA to operate it. It's an autonomous agent, that learns your business context, schema, join relationships and creates a mental map of everything (just like a DBA who joined your team). This we call it deepsql brain init stage. Once the init is done, it will then look at all slow queries workload, comes up with comprehensive suggestions of indexes,…
printf " ${DIM}This install is using DeepSQL's shared managed Azure OpenAI key, so your${RESET}\n" printf " ${DIM}schema and queries are processed through DeepSQL's shared LLM resource.${RESET}\n"
also, it requires docker.