---
title: "Dashboarding Apps"
slug: "dashboarding-apps"
description: "Connect your data directly to dashboarding apps with Dataddo without the need for a data warehouse or database. No limits on the data amount for quick reports."
updated: 2026-01-26T14:39:17Z
published: 2026-01-26T14:39:17Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataddo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboarding Apps: A Technical Overview

Directly integrating with dashboarding applications like [Databox](/docs/databox){target="_blank"}, [Looker Studio](/docs/looker-studio){target="_blank"}, [PowerBI](/docs/power-bi){target="_blank"}, or [Tableau](/docs/tableau){target="_blank"} provides a streamlined solution for simple data visualization tasks within Dataddo.

This method is particularly **suitable for smaller datasets** as it facilitates direct data transfer from your ***{{glossary.data source}}*** to visualization platforms, eliminating the need for an intermediary data warehouse. However, for larger data volumes or more intricate processes, considering a data warehouse is advisable.

## Architecture Considerations

Direct data delivery to dashboarding apps removes the requirement for an intermediary data warehouse or database. This is enabled by our embedded **SmartCache** storage system, making it an ideal choice for tasks not demanding high data volume or complex data transformations.

![Core Concept - Dashboarding Apps](https://cdn.document360.io/084ed225-3f99-4644-a2da-39ca0cd5ef45/Images/Documentation/Core%20Concepts%20-%20Dashboarding%20App%281%29.png){height="" width=""}

However, it's essential to note that **SmartCache is not a substitute for a data warehouse**. If your data volume surpasses 100,000 rows or if you require advanced operations beyond simple joins like [data blending](/docs/data-blending){target="_blank"} and [data union](/docs/data-union){target="_blank"}, a [data warehouse solution](/docs/data-storages) is recommended.

## Smart Cache
[Data Residency](/docs/dashboarding-apps#data-residency-in-smartcache)
[Ensuring Data Security](/docs/dashboarding-apps#ensuring-data-security-with-smartcache)
[Handling Large Data Volumes](/docs/dashboarding-apps#handling-large-data-volumes)
[Storage Modes](/docs/dashboarding-apps#storage-modes)

### Data Residency in SmartCache
With Dataddo's **SmartCache**, your data is stored on our servers, eliminating the need for an external data warehouse or database. You retain control over your data's physical location. Dataddo currently supports 16 global storage locations. Set your preferred data residency in [**Account Details**](https://app.dataddo.com/settings/account-details){target=`_blank`} to guarantee data stays within a specific jurisdiction or region.

### Ensuring Data Security with SmartCache
For a comprehensive overview of our security measures, refer to our [Technical & Organizational Security Measures](/docs/security){target="_blank"}.

#### Data Encryption at Rest
Dataddo ensures the security of your data at rest through automated encryption using **Advanced Encryption Standard (AES) 256**. This strong encryption method secures your data on our storage volumes.

For enhanced control and security, you can opt to provide and use your own encryption keys which safeguarded by a third-party **Hardware Security Module (HSM)**-backed key management service.

#### Data Encryption in Transit

Dataddo ensures data security during transit. All network traffic, including data directed to dashboards and other apps, is encrypted using **Transport Layer Security (TLS)**, emphasizing our commitment to data safety. This robust protocol ensures that your data remains secure and intact during transmission.

### Handling Large Data Volumes
Dashboarding apps might experience slower performance when processing large data volumes. If your dataset exceeds 100,000 rows per source, integrating an external storage solution ensures better performance.

### Storage Modes
To optimize the data management process, Dataddo offers two storage modes (also called [**snapshot keeping policy**](/docs/extraction#snapshot-keeping-policy) or simply **snapshotting policy**): **Append** and **Replace**. These modes determine how new data is handled during synchronization, offering users flexibility in data management.

* **Append**: This mode retains data in the SmartCache with each sync, adding new data to existing sets. It's ideal for tracking historical data as it accumulates and maintains a comprehensive history of your data over time.

* **Replace**: This mode overwrites existing data in the SmartCache with fresh data during each sync. Replace storage mode is suitable when having the most recent data {{glossary.snapshot}} is a priority.

## Estimating Required Data Flows

If you need to add more than one [***{{glossary.data source}}***](/docs/overview-sources){target="_blank"} to your dashboard, there are two possibilities:

1. **One flow**: Data from different sources can be joined in one table via
    1. [Data blending](/docs/data-blending){target="_blank"}: Data blending is done through a join key and is possible for max 2 ***data sources***.
    2. [Data union](/docs/data-union){target="_blank"}: Data union is possible for more than 2 ***data sources***, however, all table [schemas](/docs/schema){target=`_blank`} have to be the same.
2. **Multiple flows**: If ***data sources*** lack a join key or have different table schemas, create a separate flow for each source.

***

## Troubleshooting
### Addressing Data Duplicates
Data duplication in dashboards can arise due to:
1. **Inappropriate source snapshotting**: Review the [snapshotting policy](/docs/dashboarding-apps#storage-modes) of your ***data sources***. If historical data isn't a priority, switch to the **replace** storage mode.
2. **Data overlaps**: If you your snapshot keeping policy is set to **append** and you notice data overlaps with each extraction, you can
    1. Modify your [dynamic date range](/docs/setting-date-range#dynamic-date-range){target="_blank"} configuration.
    2. Switch the snapshot keeping policy to **replace**.
