Use Redash as basis for an application vs. embedding


#1

Correct me if I am wrong, but it seems Redash (and other tools like Metabase or Apache Superset) is tailored for the scenario where Redash lives on its own, as its own separate application.

So, if you are a developer and you want to build an app that among other tasks allows for rich analytical views, the way I see things now is that you would have to build your custom business app that does xyz tasks, and then to have the analytics section that Redash brings, you end up having what amounts to a second app just for Redash. (Please correct me if this is interpretation is invalid.)

Is there a nicer way to handle this challenge? Can you build your app entirely with Redash as the base, and add your business app material to it? Or does trying to embed Redash views into your app make sense (wouldn’t maintaining permissions be a nightmare across two different apps)?

Guidance or experience on this topic would be appreciated.