datalens
DataLens is an open-source business intelligence and data visualization platform originally developed at Yandex. It provides dashboards, reporting, and SQL-based analytics through a Docker-deployable system with modular services (UI, backend, auth, metadata storage).
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | datalens-tech/datalens |
| Owner | datalens-tech |
| Primary language | PLpgSQL |
| License | Apache-2.0 — OSI-approved |
| Stars | 1.7k |
| Forks | 114 |
| Open issues | 50 |
| Latest release | v2.9.0 (2026-02-19) |
| Last updated | 2026-06-14 |
| Source | https://github.com/datalens-tech/datalens |
What datalens is
DataLens comprises a Node.js/React UI, Python backend for query generation and data processing, PostgreSQL-backed metadata storage (UnitedStorage), and a separate auth service. It supports multiple data sources, formula calculations, and visualization types (Highcharts-based by default, with D3.js fallback).
Get the datalens source
Clone the repository and explore it locally.
git clone https://github.com/datalens-tech/datalens.gitcd datalens# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Docker Compose v2 or legacy v1.29.0+ required; verify version compatibility before deployment.
- Production deployments mandate RSA key generation (auth tokens, temporal, UI/backend auth) using provided init.sh script; keys must be securely stored in .env or Kubernetes secrets.
- PostgreSQL is core dependency for metadata and user settings; ensure high-availability setup and backup strategy for production use.
- Highcharts licensing must be explicitly reviewed if HC=1 is enabled; D3.js fallback available but visualization types are currently limited.
- All user settings, connections, and dashboard objects persist in PostgreSQL volumes; design disaster recovery and data migration strategy.
When to avoid it — and what to weigh
- Minimal DevOps capability — Setup requires Docker Compose knowledge, Kubernetes familiarity for production, and manual RSA key generation. No managed cloud offering or one-click SaaS deployment.
- Strict licensing constraints around proprietary visualizations — Highcharts (enabled via HC=1 flag) is proprietary and requires separate compliance review. Users must either accept Highcharts licensing or rely on limited D3.js alternatives.
- Need for extensive pre-built integrations — Data source connectivity and third-party integrations are not enumerated in available documentation. Requires custom connector development or review of separate backend repository.
- Low tolerance for immature projects — Project created September 2023 with 1,691 stars and 50 open issues. Smaller community compared to mature BI tools; fewer public case studies or vetted enterprise deployments.
License & commercial use
Apache License 2.0 (Apache-2.0). Permissive OSI-compliant license allowing commercial use, modification, and distribution with attribution and liability disclaimer. Proprietary Highcharts visualization library may impose additional licensing constraints if enabled.
Apache-2.0 permits commercial deployment and modification. However, if Highcharts visualization library is enabled (HC=1), separate commercial licensing from Highcharts must be obtained and verified per their terms. Review Highcharts license at https://github.com/highcharts/highcharts/blob/master/license.txt before production use. No commercial support SLA or vendor indemnification detailed in provided data.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Needs review |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | High |
No security audit, penetration test results, or CVE history provided. Key considerations: (1) Auth service uses RSA keys for token generation—secure key storage and rotation practices required; (2) Default admin credentials (admin/admin) must be immediately changed in any deployment; (3) PostgreSQL is core dependency—network isolation and credential management critical; (4) No details on encryption at rest, in transit, or access control audit logging. Requires threat modeling and security review before production enterprise use.
Alternatives to consider
Metabase
Open-source, single-binary deployment, lower operational overhead, broader community. Requires less infrastructure expertise but less customization than DataLens.
Grafana
Lighter-weight, strong monitoring focus, simpler Kubernetes adoption, larger ecosystem of data source plugins. Better fit for observability-first use cases.
Apache Superset
Python-based OSS BI, easier for Python shops, no proprietary visualization dependencies by default, active Apache community. Comparable feature scope with fewer licensing caveats.
Build on datalens with DEV.co software developers
Our engineers can assess deployment architecture, licensing implications (especially Highcharts), Kubernetes operationalization, and integration with your data sources. Contact us for a technical review and proof-of-concept.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
datalens FAQ
Do I need a license fee to run DataLens?
Can I use DataLens without Docker?
What databases does DataLens connect to?
How do I secure DataLens for enterprise use?
Software development & web development with DEV.co
Need help beyond evaluating datalens? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source databases integrations — and maintain them long-term.
Ready to evaluate DataLens for your analytics stack?
Our engineers can assess deployment architecture, licensing implications (especially Highcharts), Kubernetes operationalization, and integration with your data sources. Contact us for a technical review and proof-of-concept.