Tldraw's default version of nesting is embedding another full canvas. The benefit would be that the embedded canvas is fully live.
Nestable enables nesting at page management level and encourages deep links to connect things between canvases. This approach has proven to be much more scalable in all of my workflows
1. Tldraw support of embedded canvases it not great when you are power using
2. You can open the sidebar from clicking the page name in the center top of the canvas
3. Initially I had the sidebar be a side component that pushes the canvas to the right but the change in aspect ratio was jarring because I was constantly opening and closing the sidebar
4. Made with tldraw is mentioned on the right bottom of the canvas. I am not trying to hide it in any way.
Nestable approach with canvas management is more similar to notion than muse.
Nestable also has deep linking across the app so that you can leave hyperlinks to other pages or shapes from anywhere to enable better organisation and management.
Canvases aren't generally used as knowledge bases because more often than not, it gets really hard navigating them and nestable wishes to solve that.
In terms of making a business of out nestable, I have no plans for it. This is fully local and the only charge I incur would be for hosting which is very minimal.
Zooming in to reveal things will only make it more ambiguous since the right depth at which we hide away content will vary based on the content.
We can more intuitively build this with nestable using deep links. Each layer/level can be shown in one canvas and a deeplink to another canvas that captures a more granular level of any of the components would be a much scalable and generic approach.
https://github.com/tursodatabase/agentfs