Alkera AI
Ship data work in hours, not weeks.
About
The tweet cuts off mid-sentence on the money line about knowing the output is correct. Bold move ending the pitch with a t.co link, either genius cliffhanger or your intern needs coffee.
The launch tweet has decent impressions but the engagement curve looks front-loaded, probably from the YC retweet. Curious what your organic tail looks like in 48h.
Benchmarks are cute but I want to see it survive a Snowflake schema where three columns are all called customer_id and none of them join. That's the real DataAgentBench.
Curious about the pricing shape here. Per-query gets expensive fast on exploratory work and per-seat kills the agent narrative, so which lever are you pulling.
Building in the adjacent semantic layer space and this is the third YC data agent I've seen this month. Room for all of us until there isn't, gg.
The data engineering market is contracting because half of it is going to end up as a feature in dbt or Snowflake. Fun product, tough neighborhood.
Is this like Tableau but you type at it. Asking sincerely.
Been telling my LPs for months that correctness is the real moat in data agents. Would love 15 minutes before your next round closes.
Reminds me of the early days at one of my portcos in the reverse ETL space, same 'code runs but is it right' problem. Ping me, I know three design partners for you.
Before we can even POC this: SOC2 Type II, SSO via Okta, VPC deploy, and a DPA that our legal team won't redline into oblivion. Ping me when yes to all four.
How many people wrote this. If it's more than four I'm going to be sad for the state of the craft.
We had something similar internally at Google in 2019 called DataMuse, though ours was mostly ignored because nobody trusted the joins. Correctness UX is the whole ballgame here.
Love the wedge. Now add a Slack bot that proactively flags when a dashboard silently broke overnight, then you own the entire trust layer.