Nao is an AI powered data IDE for analysts, engineers, and scientists to write SQL, Python, or dbt workflows, preview changes, catch issues early, and deploy confidently. It connects directly to your warehouse and understands your schema so you can build faster, fix fewer bugs, and maintain trust in your data. Build data pipelines, launch quality checks, run analytics, and collaborate across teams without context switching. Think of it as your AI teammate built specifically for modern data work.
Free Options
Launch Team / Built With
Hello @claire_gouze @bleff - Any plan to squeeze the whole set of .naorules into a single folder? Having multiple naorules files on the root directory of a repo with hundreds of dbt models and yml files looks suboptimal to us
nao
heyyy @_aneema , this is a great question! At the moment we have a single .naorules in the root folder, but as rules are growing in size we are considering moving everything inside a single folder with easy to use selectors.
Just to be sure would you like to have a single folder at the top with selectors or would you prefer being able to add .naorules in subfolders of your dbt project?
nao
@_aneema for now you can use one single .naorules so that it's just one file at the root of your folder. But we have on our roadmap to have the agent understand multiple files of .md in your repo!
@claire_gouze @bleff Thanks for getting back to me.
I think Nao rules should live in /.naorules (place in the root directory) with extension specific sub-rules. For example, /.naorules/sql-rules.txt stores formatting rules for .sql files, /.naorules/python-rules.txt for Python files, etc. (.txt is a placeholder, not the actual extension I would assign).
I also think this could save a nontrivial amount of tokens in API calls: when processing only .sql files, Nao passes only sql-rules.txt to the LLM instead of the entire generic .naorules file containing rules for all extensions. More manageable for data teams: analytics engineers maintain rules for their files, data engineers maintain rules for theirs, data scientists their, etc
Hope it makes sense, happy to help if you have any further questions :)
nao
@bleff @_aneema yes that's similar to what we have in mind. We'll keep you updated when we put this in place!
nao
@vouchy I would say it depends the task you're asking to nao because nao is able to pull the context you need when it's needed. In addition to this what we discovered is that schema > preview > business definitions > documentation is kinda what's important for the AI
nao
@gavin_edgley of course it does! You can connect to Databricks in nao, directly query it there and work with the agent on your databricks warehouse.
For now haven't tried gravity - and we focus on specializing the experience to data people which generalist code editors don't do
Hello8
nao
@garysz Thanks Gary, yes definitely what we needed for data teams!
nao
Hey! I'm Stan, founding engineer at nao Labs.
Glad to be working on this beautiful product. We've come a long way since last year.
With nao, you can connect your data, visualize it, interact with it, and build powerful data pipelines, all with the help of AI and IDE tools we all love.
We're just getting started. We have so much more coming out soon.
Stay tuned and happy data vibing!
nao
@stan_dlc yes what a long ride in a year ! 🏎️
Collective.work
I really think this idea is brilliant 🔥 Developers use cursor, you can do many great things with it, but data work is way more specific, and clearly lacking tooling on this part - and it's much more than just generate me this SQL query
I'm super eager to see where all this will lead, but clearly the industry needs more specialised tools, and I think you're nailing it! Will definitely push in my team :)
nao
@paul_vidal thank you! Yes for sure, we need to finally have tools made for data work. Let's smash it!! 💥
Strapi
Let's goooo! Awesome product, amazing team, we didn't find the way to give it a try until now but it's on our radar for a long time, this new version looks freaking cool, we cannot wait to use Nao 🙌
nao
@aureliengeorget thank you for your support, hope you'll try it soon 😉