Powered by Looker Feedback

  • 10 June 2016
  • 5 replies

Userlevel 2

At Stitch Labs, I’m starting a project and considering using Powered by Looker. Currently, we only use Looker within Looker or via email for internal reporting. We’re not exploring embedding it within our application for our customers (retailers).

I’m hoping to connect with anyone who used it (or chose not to use it) and get your feedback on what worked well, what didn’t and anything you wish you had known or done differently.

5 replies

Hi Bridge,

we’re developing powered-by-looker with embedding, happy to share experience.

Hi John, I’d love to learn more about your experience embedding powered by as well.



Hi Trevor,

feel free to hit me up at

We are in the process of developing an offering for our customers that makes use of Looker via embedding within our product. It’s relatively straightforward but the authentication and permissions need to be understood (we are in this stage now). I’d appreciate hearing about anyone’s experience and would love to share more information about our experience so far.

We’re far down the road with embedding (Powered by Looker) in our Rails app, which is our primary use for the product - we run a business with a separate copy of a (synchronized) schema for all of our customers. I feel like we deeply exercise the product in this way, as well as have customer users who have ‘self-service’ access (access via the Looker UI to their schema, with branding on the UI). We’ve really pushed the limits, and I’m happy to share our experiences.

As you can imagine, there are good and bad pieces. One thing I can say, though, is that the Looker technical team is EXCEPTIONALLY helpful, and the experience overall has been fantastic, with solid response from product development in areas where our use case exceeds the products ‘easements’ and gets into some unusual patterns. Definitely feel like we made the right choice, and even though a more ‘coupled’ product (and we examined many) could have reduced some of our implementation complexities, they would have cost us far more in other ways.