LivChart
Local-first AI dashboards. Your data stays on your device.
Every BI tool we tried — Power BI, Tableau, Looker — wanted our data on their servers. Financial reports, HR data, strategic plans. All going to Microsoft, Salesforce, AWS.
For our clients under GDPR and KVKK, that wasn't acceptable. We looked for something that keeps data local but still has AI. Nothing existed.
So we built LivChart.
What it does:
- Build dashboards from Excel, CSV, or SQL databases
- AI generates charts — all on your device, no API calls
- DAX formulas (same as Power BI, runs locally)
- ETL pipeline built-in
- PDF report export
- Connect Ollama models for on-device AI
What it doesn't do:
- Upload your data anywhere
- Require internet
- Send anything to third-party servers
We work with finance teams, HR departments, healthcare orgs. When data stays on your machine, compliance is simple. No cross-border transfer, no third-party access.
Where we are now: live on livchart.com, bootstrapped, no external funding. Two Medium articles published, DEV.to series running, Ollama models available.
Built by Liv Yazılım.
Would love feedback from fellow makers — what would you do differently on positioning and go-to-market?
7 Comments
I'm curious what happened first.
Did clients start asking for local-first AI and that led to LivChart?
Or did LivChart exist first and the compliance angle become the strongest story afterward?
Honestly, it started with client needs.
We do ERP consulting (Canias ERP) and our clients kept hitting the same wall. Power BI and similar tools required IT support for every report. Managers wanted to build their own dashboards but couldn't — too complex, needed IT tickets, waited days for simple charts. On top of that, their data was going to cloud servers. Financial reports, HR data — sensitive stuff. GDPR and KVKK made it worse.
So the idea was: give them something where they can build their own reports without IT, and their data stays on their machine. AI handles the hard part — chart selection, data mapping, DAX formulas.
User just describes what they want. The compliance angle wasn't the starting point. It was the natural result of keeping everything local. Clients loved it because it solved both problems at once — no IT dependency, no data leaving the building.
Interesting.
The reason I asked is that those two origin stories can end up looking very similar from the outside while creating very different pressures underneath.
Probably more than I'd try to unpack properly in a thread though.
Happy to continue by email if useful.
Good question. It was 100% client-driven. We're ERP consultants first — our clients were hitting two walls at the same time: IT dependency for every report and data leaving their infrastructure. LivChart was our answer to both. The local-first part wasn't a feature we added later, it was the reason we started building. Happy to chat more if you're interested.
I am.
A couple things stood out to me reading that, but they're probably easier to discuss outside the thread.
Feel free to drop your email if you'd like to continue.
Sounds good. You can reach me at rtulunay [at] livyazilim [dot] com — looking forward to it.
Just sent you a note.