We have a custom-built reporting data lake in PostgreSQL that synchronizes data from multiple sources every day. NLSQL sits on top of this data lake as a self-service AI analytics tool, with a conversational user interface (TUI) available in MS Teams. This setup provides non-technical users access to insights without granting them SQL access to the data lake database.
Self-service analytics has empowered non-technical teams and drives consistent data decisions
What is our primary use case?
How has it helped my organization?
It helps people across the organization make data-driven decisions faster. Non-technical employees can validate their improvement ideas quickly and create PowerPoint presentations backed by real numbers, rather than relying on assumptions alone.
What is most valuable?
NLSQL includes an embedded knowledge graph built around your company’s ontology, configured specifically for your organization based on your data governance documentation and database schema. This enables users to work with the business indicators and terminology they are already familiar with. Moreover, these indicators are calculated consistently according to the agreed business definitions. This builds trust among key stakeholders and ensures that everyone gets the same answer to the same business question.
What needs improvement?
Building the ontology layer requires some manual configuration, which depends on the internal team’s understanding of the organization’s terminology, vocabulary, and KPIs.
For how long have I used the solution?
I have been using the solution for 1 year.
What do I think about the stability of the solution?
It is deployed as ECS with CloudFront ssl encrypted messaging endpoint. The resource is healthy now
What do I think about the scalability of the solution?
NLSQL can scale fast but we don't have thousands of users now
How are customer service and support?
Brilliant
Which solution did I use previously and why did I switch?
I used PowerBI, but we still use it in parallel as the main dashboard tool. The NLSQL bot is capable of sending URLs to dashboards as well.
How was the initial setup?
Initial setup is complex as it requires prerequisites for building ontology layer specifically for our company
What about the implementation team?
We didn't use this ones
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
The free trial is a great way to prove NLSQL's value before making any commitment.
Which other solutions did I evaluate?
Thoughtspot
What other advice do I have?
Running NLSQL in the customer’s own AWS cloud means data stays within the company AWS ecosystem, which makes it much easier to approach from an IT and security perspective.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
