Decube Reviews

My main use for Decube is data observability and data quality monitoring. I use it to monitor data pipelines, detect data issues, track data quality, and ensure reliable data across systems.

One example is when a daily data pipeline failed to update a company reporting dashboard on time. I used Decube to monitor the pipeline, identify the data freshness issues, and check where the delay occurred. This helped me investigate the problem faster and ensure the dashboard received updated data.

I use Decube as part of my regular workflow to keep track of data quality and pipeline health. It makes it easier to spot unusual changes, catch issues early, and avoid problems with reports. I appreciate having everything monitored in one place instead of manually checking everything.

Decube has helped us save time, catch data issues earlier, reduce manual monitoring, and maintain more reliable reporting across our daily operations.

While we haven't tracked exact metrics, Decube has helped us reduce manual monitoring and identify data issues faster. It saves several hours of troubleshooting and helps keep our daily reports more reliable.

What I like most about Decube are the data quality monitoring, pipeline monitoring, and alerting features. It makes it easier to spot issues early, track data freshness, and understand what's going wrong without having to manually check everything.

The alerting features in Decube are really helpful because I don't have to keep checking everything manually. If a pipeline fails, data is delayed, or something unusual happens, Decube notifies me so I can look into it quickly. It saves time and helps me catch small issues before they affect our reports or daily work.

Decube brings useful monitoring tools together, saves manual effort, and makes it easier to maintain reliable data pipelines with fewer surprises.

Decube could improve by offering more customizable alerts, a simpler dashboard, faster setup, and clearer troubleshooting suggestions when pipeline issues occur.

I would appreciate seeing more detailed error explanations, flexible alert settings, and better dashboard customization. These improvements would make daily monitoring easier and save even more time.

I would also like to see better integration with more data platforms, smarter root cause analysis, customizable dashboards, and clearer recommendations for fixing data issues. This would make Decube even more useful in everyday work.

I have been using Decube for a few months.

Decube is stable.

Decube seems scalable for growing data needs. It provides useful visibility into data pipelines and quality as workloads increase. I would appreciate seeing even more flexibility when handling very large data sets.

The customer support experience has been good overall. Responses are helpful and the team is supportive when issues come up. Faster response times and more detailed troubleshooting guidance would make it even better.

I rate the customer support eight out of ten.

We previously relied more on manual monitoring and basic data quality checks. We switched to Decube because it offers centralized monitoring, faster issues detection, and better visibility into data pipelines.

We have seen a positive return, mainly through time saving and reduced manual monitoring. It helps us identify issues faster and avoid reporting delays. We haven't calculated exact financial savings yet, but it has improved our team efficiency.

The pricing felt reasonable for the value offered. Setup was fairly straightforward, and the licensing was easy to understand. I would still appreciate more flexible plans and clearer pricing as usage grows.

We briefly considered other data observability tools.

Decube stood out because of its pipeline monitoring, data quality checks, and alerting features.

I rate Decube nine out of ten.

I gave Decube a nine because it makes data monitoring easier, helps us catch issues early, saves time, and keeps our reporting reliable. There is still some room for improvement, but overall, it has been a really useful tool.

The AI capabilities of Decube should provide good governance and security through controlled data access and clearer monitoring. I would appreciate seeing more transparency around data usage, permissions, and how sensitive information is protected.

I find Decube's output generally useful and reliable for identifying data issues. However, I still prefer to verify important results before making decisions, especially when accuracy matters.

We use Decube in a public cloud environment because it makes deployment, accessibility, and day-to-day data monitoring easier for our team. We use AWS for our public cloud deployment.

I would recommend giving Decube a try if you want better visibility into your data pipelines and quality. Start with a few important workflows, explore the alerting features, and see how well it fits your team's needs.

My main use case for Decube centers around ensuring data quality in my daily work. Decube serves as my end-to-end data observability and trust platform, used to monitor the health and integrity of data pipelines in real-time. I rely on automated monitoring templates across five key pillars: schema drift, freshness, timeliness, volume anomalies, field health, and custom SQL rules by continuously scanning metadata, schema modifications, and row-level statistics in data warehouses like Snowflake or BigQuery. This allows me to catch data quality defects before bad data propagates in executive dashboards or ML models.

One concrete problem Decube helped me solve was a silent pipeline failure involving upstream schema drift where duplicate records were being generated during the automated ingestion process.

Decube's key value lies in its ability to seamlessly bridge the gap between data engineering, cataloging, and governance. It tracks column-level lineage from the source database through transformation tools like dbt down to BI dashboards in Tableau or Power BI, employing automated sensitive data discovery, simple rule-based access control management, and feeding continuous quality scores into data catalogs to allow business users to verify that data sets are trustworthy and updated before running critical reports.

Decube has positively impacted my organization through data reductions and resolutions leveraging automated observability and column-level lineage, which engaged my engineering team to cut problem resolution times by 50% to 80%. Issues that previously took 9 to 15 hours to debug are now routinely resolved in under an hour, with a significant drop in data downtime.

Continuous ML-driven monitoring of freshness, volume, and schema drift has reduced downstream spending on broken or missing pipeline data by 80%, leading to direct cost savings with ROI typically between $200,000 and $70,000 annually. This has also improved engineering productivity and reporting accuracy.

The best features Decube offers include automated data observability and column-level end-to-end lineage, which automatically processes query logs and transformation code to trace column-level connections. This integrates pipelines and warehouse transformations with reporting tools into a single visual graph, along with a unified data catalog discovery that allows me to manage automated metadata indexing, business glossaries, and tags management for easy searching and understanding of data context.

The single most valuable feature in Decube for my team is the automated column-level data lineage combined with root cause analysis. In a complex environment where data flows through multiple ingestions, dbt transformations, and BI tools like Tableau or Power BI, pinpointing why a downstream metric suddenly looks wrong can take hours of manual query auditing. With column-level lineage, when a freshness schema alert fires, the system traces issues back to the exact upstream table or source system transformation that broke while simultaneously mapping the downstream blast radius, showing which executive dashboard or data production is affected.

Beyond root cause analysis, two other features that significantly impact my daily operations are automated sensitive data discovery and PII tagging. Instead of manually invoking new tables and tagging sensitive customer fields, Decube continuously scans incoming schema and automatically classifies PII and sensitive data assets. Additionally, no-code monitoring and dynamic thresholds track normal volume, freshness, and distribution patterns without writing dozens of custom SQL tests for every single table.

Regarding Decube's AI capabilities, its approach to governance and security is particularly strong in enterprise environments, focusing on authority governance and security while ensuring adequate privacy architecture through metadata processing to comply with enterprise standards. Its accuracy and reliability relate to the trust AI engine's automated metadata tagging, which relies on a solid foundation of metadata checks and guardrails, although there are some limitations and accuracy gaps based on initial metadata quality.

While Decube is already strong in data observability and cataloging, several key updates would make it significantly better, including streamlined onboarding setup, deeper customer alerting, granular roles, broader integration capabilities, API monitoring, automated remediation actions, and improved support documentation.

The user interface and integration capabilities highlight two key areas where Decube can deliver even greater value. Enhancing the UI/UX for customizable observational dashboards while providing solid visual lineage and monitoring overviews would allow me to build personalized drag-and-drop dashboards and simplify navigation through complex dbt modules. Additionally, improving search UX with faster autocomplete, context-aware suggestions, and bulk tagging capabilities would accelerate data discovery and streamline large data queries. Expanding the integration ecosystem capabilities deeper into CI/CD for broader DevOps connections would also be beneficial.

I rate Decube a nine because the last point comes down to a few operational frictions, including initial startup onboarding issues, alert noise, and complex UI graph navigation.

Decube is being used to build a data glossary, data catalog, lineage, data monitoring, and observability. After using Decube for three to four months, I believe it looks good now. It operates at the SaaS level, so you simply connect the data sources and it builds a catalog with observability and schema drift detection. The tool provides all of that functionality in a seamless manner.

The data lineage chart is definitely helpful because it allows us to traverse how data flows from the source to the report layer, providing full visibility of how the system works.

Regarding automation, automated data health checks are valuable. If there is any drift, data quality issue, data over-range issue, or missing data, the tool detects it and sends notifications to the concerned team. Alerting mechanisms are available through multiple channels including email.

Decube generates reports regarding what has happened. Through the API capabilities, I can build monitors, glossaries, and linked assets, which has been very helpful. The API capability is supporting a lot of functionality.

Regarding data governance, Decube does help improve it in the company. Once it is fully available, it will definitely help the whole team by providing visibility into which data is coming from where and by addressing any reporting or data quality issues.

There are a few drawbacks to the product. If I delete any record, it is not immediate and does not allow me to create the assets again. The system indicates that the asset is already available. We are checking with the team to understand what the problem is.

Another issue is that if there are system-level monitors, there is no way to update them through the API, so API support is needed for them.

I have been working on Decube for the last three to four months.

I did not see any stability problems as of now because we are not yet in production. In the development environment, everything looks good.

Regarding scalability, it should be scalable since it is on Kubernetes.

I have dealt with technical support from Decube. Regarding the effectiveness of technical support, they are helpful and doing a good job. If I would rate support from zero to ten points, I would give them seven. They connect us through email and Teams chat. We get responses, though there is some delay, but at least we receive responses, so I would rate them at six or seven.

Positive

I have worked with Collibra previously, but I am currently working on Decube. I have been in the data governance and IT products sphere for three to four years and have worked with Ranger and other tools.

Regarding the installation of the product, I do not have experience with it as it is a DevOps activity. Decube is Kubernetes-based, and both Decube and our DevOps team support it.

I work as an integrator.

Regarding ROI, it is yet to be proven. We are exploring the tool for the last three months and are yet to be in production, so only then will we know what benefit we are providing to the client.

I am currently using Decube for data governance. I have worked with Collibra previously, but I am now working on Decube.

Currently, I work with other tools on various data governance activities. For data governance specifically, Decube is the only tool I am dealing with.