Hosted Redash shut down: what happened and the best alternatives in 2026

The hosted Redash service at app.redash.io shut down on November 30, 2021. That does not mean Redash itself vanished: the open-source project still exists and can be self-hosted. The distinction matters, because “Redash shut down” is only accurate when it refers to the managed cloud product.

If your team used hosted Redash, its closure forced a choice between running open-source Redash yourself, moving into Databricks, or adopting another hosted analytics product. This guide explains what changed and how to choose a replacement without confusing a discontinued service with an active open-source project.

What was hosted Redash?

Redash is a SQL-first analytics tool. Analysts connect data sources, write queries, visualize the results, and arrange charts into dashboards. Its deliberately simple model made it popular with technical teams:

• SQL queries are the primary authoring interface.
• Query results can become tables, charts, alerts, and dashboard tiles.
• Parameters let dashboard viewers change filters without editing the query.
• A single workspace brings query history, visualizations, and shared reporting together.

For many teams, hosted Redash supplied that workflow without the infrastructure work of operating it themselves.

Why did hosted Redash shut down?

Databricks acquired Redash in 2020. In its official end-of-life notice, the company said it would close app.redash.io on November 30, 2021 to focus on SQL-analyst experiences inside Databricks. It stopped new sign-ups and instructed existing customers to migrate their content before the deadline.

The same notice recommended two paths: Databricks SQL for customers already using Databricks, or self-hosted open-source Redash for customers needing other data sources. The hosted customer data was deleted after the service closed.

Is Redash still available?

Yes, but not as an official managed Redash cloud service. The open-source project remains available under a BSD 2-Clause license and has a community-led maintenance effort. That makes self-hosting an option, but it changes the ownership model: your team is now responsible for deployment, upgrades, backups, authentication, and security patches.

This is the key decision. Do you want to keep a SQL-first, self-hosted tool, or use a managed product that removes operational work and broadens access beyond SQL specialists?

What to look for in a hosted Redash alternative

• SQL should remain first-class. Analysts need an editor, saved queries, parameters, and an easy way to verify what a chart runs.
• Non-technical access should be deliberate. A dashboard viewer should not need to write SQL to answer a routine follow-up.
• Ownership should match your team. Self-hosting is sensible only when you have capacity for its operational work.
• Permissions should be specific. Data source credentials, dashboard sharing, and row-level access need review before you recreate reports.
• Answers should be reusable. The replacement should let a one-off analysis become a dashboard, alert, or scheduled delivery.

The best hosted Redash alternatives in 2026

1. Basedash: managed, AI-native BI with transparent SQL

Basedash is a strong replacement when you want to keep the directness of a SQL workflow but make analysis available to more people. Ask a question in plain English, review the generated SQL, refine it in an editor, and save the result as a chart or dashboard.

For former hosted Redash users, the practical advantages are:

• No BI infrastructure to deploy or maintain.
• Generated SQL stays visible and editable instead of becoming a black-box answer.
• Defined relationships, descriptions, and business terms provide context for analysis.
• Results can be shared through dashboards and alerts.
• Direct database connections plus 750+ SaaS sources cover more than a warehouse-only stack.

Best for: teams that want a managed SQL-and-AI analytics workflow rather than another self-hosted service.

2. Self-hosted Redash: preserve the familiar workflow

Self-hosting open-source Redash is the closest functional continuation for teams that already have deployment expertise and want to preserve existing habits. It is especially reasonable when the current dashboards are SQL-written, the audience is mostly technical, and the organization prefers to operate its own analytics software.

The trade-off is ongoing engineering ownership. Treat a self-hosted migration as an infrastructure project, not a free hosted-service replacement.

Best for: SQL-centric teams with clear self-hosting requirements and operational capacity.

3. Metabase: visual querying alongside SQL

Metabase gives analysts a native SQL editor while adding a visual query builder for less technical colleagues. It is available as a managed cloud service or self-hosted software, making it a flexible choice for teams that want to broaden dashboard authoring without abandoning SQL entirely.

Best for: teams that want a lighter transition from SQL-only reporting to broader self-service BI.

4. Apache Superset: configurable open-source analytics

Apache Superset is an enterprise-grade open-source option with SQL Lab, a large visualization catalog, and extensive database support. It can be a better fit than Redash for complex dashboard estates, but it has a larger deployment and administration footprint.

Best for: organizations that need a customizable, self-hosted platform at larger scale.

5. Databricks SQL: the intended path for Databricks teams

Databricks SQL is the natural successor if your data, identity, and governance already live in Databricks. It provides SQL warehousing, dashboards, and alerts in the same platform. It is less compelling as a reason to adopt Databricks from scratch solely to replace a lightweight dashboard tool.

Best for: existing Databricks customers.

Hosted Redash alternatives compared

How to migrate from hosted Redash

If you still have an export from the former hosted workspace, begin with queries rather than dashboard layouts. The SQL encodes business logic, join assumptions, and filters that may not be obvious from a chart title.

1. Export and classify saved queries, dashboards, alerts, parameters, and data-source settings.
2. Reconnect each source with scoped credentials rather than copying old broad credentials.
3. Run important queries against the new environment and reconcile totals before rebuilding visuals.
4. Recreate high-use dashboards and alerts first.
5. Decide which reports should remain analyst-authored and which can become self-service dashboards.

Do not assume every old query deserves migration. Retiring stale dashboards is often the fastest way to reduce future maintenance.

The takeaway

Hosted Redash is gone, but open-source Redash is not. Teams that miss the hosted service should decide whether they truly want to operate the open-source tool or whether the original appeal was simply fast, trustworthy access to data.

For teams that want the latter without infrastructure work, Basedash pairs natural-language analysis with visible SQL, governed context, dashboards, and alerts.

FAQs

Did Redash shut down completely?

No. Databricks shut down the hosted service at app.redash.io on November 30, 2021. The open-source Redash project continues separately and can be self-hosted. A post that says “Redash shut down” without this distinction is incomplete and can incorrectly imply that existing self-hosted deployments stopped working.

Why did the hosted Redash service close?

After acquiring Redash, Databricks said it was retiring the hosted service to focus on SQL-analyst experiences within Databricks. Its end-of-life notice directed Databricks customers toward Databricks SQL and customers with broader source requirements toward self-hosted open-source Redash.

Can I still create a new Redash Cloud account?

No. The former managed service stopped accepting new customers before its 2021 closure and no official Redash Cloud replacement is available. Teams that want Redash now need to run the open-source software themselves or choose another managed analytics product.

Is self-hosted Redash free?

The software is open source, but self-hosting is not cost-free. You still need infrastructure, a metadata database, authentication, backups, monitoring, upgrades, and someone responsible for security issues. Estimate those operational costs alongside licensing when comparing it with a managed tool.

What should SQL-first teams use instead of hosted Redash?

The best option depends on how much the team wants to operate. Self-hosted Redash preserves the most familiar interface. Databricks SQL is the most direct path for existing Databricks users. Basedash works well when a team wants to retain editable SQL while also letting colleagues begin analysis through natural-language questions and shared dashboards.