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.
I don't know - I think these Vendo guys are onto something here. Businesses will absolutely need to do this.
As a data point, our users are going a step further. We gave away our desktop software as OSS and our users fork and vibe code on top with the entire stack. They get the benefit of not having JavaScript powering a media heavy app since we wrote it in Rust. Now we have users making their own tutorials about it.
I think non experts will appreciate engineers solving for smoothness, distributed systems, and all the hard parts that can back them into corners. They want to fill in the UX / workflow pieces themselves.
I think these "hard part" pillars will endure for a while longer.
But you're going to have to give away more than you've ever given away before. Treat your users as junior engineers on your team. That's the new normal.
And for full disclosure, none of our users have software backgrounds whatsoever. They're just heavy into Claude Code as complete software newbies. It's really awesome to watch them building really neat workflows.
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.
[delayed]
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.
I don't know - I think these Vendo guys are onto something here. Businesses will absolutely need to do this.
As a data point, our users are going a step further. We gave away our desktop software as OSS and our users fork and vibe code on top with the entire stack. They get the benefit of not having JavaScript powering a media heavy app since we wrote it in Rust. Now we have users making their own tutorials about it.
I think non experts will appreciate engineers solving for smoothness, distributed systems, and all the hard parts that can back them into corners. They want to fill in the UX / workflow pieces themselves.
I think these "hard part" pillars will endure for a while longer.
But you're going to have to give away more than you've ever given away before. Treat your users as junior engineers on your team. That's the new normal.
And for full disclosure, none of our users have software backgrounds whatsoever. They're just heavy into Claude Code as complete software newbies. It's really awesome to watch them building really neat workflows.
That's really interesting. Would love to learn more about what type of customizations/features you have seen your users create?
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.