What benefit does this provide over an excellent API + MCP access?
I often find my users want to throw their Claude at it and have everything handled. Users have even developed their own local UIs using Claude Design. As long as they are within the bounds of the MCP I already provide access to, no problem. This also has the added benefit of using the AI subscription the org already pays for (or using the customers).
Edit: Congrats on the launch and thanks for open sourcing!
Great question! Honestly, not a lot. This is moreso for the rest of the population that does not even know Claude Code exists. A lot of our customers are vertical SaaS's that have tons of non-technical users using their product every day, and we want to bring them the power of claude code right inside their product.
I think you bring up a good point though on how consumption of software will evolve (and the possibility of Claude just being the entrance to everything), and I think this is soemthing we have been thinking a lot about as well.
As detailed as the user wants. We don't limit the user with things like pre-built components and so on, so they can let their creativity run wild. What we chose to focus on instead, is making sure that the things they create are sandboxed, accurately representing the data at hand, and feel native in the product.
What benefit does this provide over an excellent API + MCP access?
I often find my users want to throw their Claude at it and have everything handled. Users have even developed their own local UIs using Claude Design. As long as they are within the bounds of the MCP I already provide access to, no problem. This also has the added benefit of using the AI subscription the org already pays for (or using the customers).
Edit: Congrats on the launch and thanks for open sourcing!
Great question! Honestly, not a lot. This is moreso for the rest of the population that does not even know Claude Code exists. A lot of our customers are vertical SaaS's that have tons of non-technical users using their product every day, and we want to bring them the power of claude code right inside their product.
I think you bring up a good point though on how consumption of software will evolve (and the possibility of Claude just being the entrance to everything), and I think this is soemthing we have been thinking a lot about as well.
What is the extent of the customization of each dashboard type? How detailed can I get
As detailed as the user wants. We don't limit the user with things like pre-built components and so on, so they can let their creativity run wild. What we chose to focus on instead, is making sure that the things they create are sandboxed, accurately representing the data at hand, and feel native in the product.