We're putting together some better tutorials as BandLab has a lot of hidden complexity but let me address a couple of things here - there are some core misunderstandings.
1)
We already have embed - it's via the "Share" button on a post - it's only available for published posts right now, as it would not make sense to embed private revisions that no-one else can access!
2)
Projects that are on the "interweb" - more on collaboration in the next post, but it's important to understand how projects work on BandLab. Projects/Songs are made up of different revisions - e.g you don't "publish" a project, you publish a revision/mix from a Project. There are three different states of revisions in BandLab that are your choice:
- Private - the track is not visible by anybody, except those who have access to the project. If you don't collaborate with anyone, it's just you. If you have Collaborators, or are in a Band, then they can see private revisions.

- Public - if you publish a revision, but do not make it forkable - it's equivalent to uploading to a gallery or any audio-hosting site. People can listen, like, comment, add to Collections (our version of Playlists), share, embed but they can't access the multi-track files or anything more.

- Public + Forkable - if you publish a revision and make it forkable - you're someone who embraces the world of open source and want to inspire others, or to see what people can create with your music. You're accepting the fact that others can commercialize the results of forking the track and giving them license to do so - but it's your choice - if you're not into it, then don't make it forkable. The creator of the original revision is attributed on any subsequent track that is published on BandLab and it's always possible to "trace something back to the start" because of our version control tools.

Many of our professional musicians will not publish revisions or forkable revisions as they commercialize their own music, but use BandLab for the mix editor, idea capture, cross-platform workflow tools. Most of our younger beat producers who don't see publishing or album sales as a way to create a career as a musician give away free beats that are forkable, because the engagement from artists eventually turn into paying customers who buy or lease premium beats from them.
Open source is not for everyone, but please don't misunderstand that BandLab is only used that way. How one shares music varies between genres and demographics.
3)
Collaborating on BandLab - as mentioned above, the majority of our users make music solo and keep it private, only publishing their best revisions in a project. However, collaborating on BandLab is one of our best workflows, and there are three ways to make music socially on BandLab just like in real life:
- Via a Band - think Mick Jagger joining the Rolling Stones - by joining/creating a band, you decide to have a long term commitment with other Band members and as such you get some extra functions. There are Admin/Member permissions, and you get your own Band profile page, real-time group chat, notifications when your Band members start new projects, etc.
- Inviting Collaborators to a Project - think BB King x U2 on When Love Comes to Town - inviting collaborators is like having a guest star join in - you don't want the commitment of being in a group/Band together and is limited to that project only. You can invite other users to your solo projects or band projects. They don't automatically get to join in on your other projects unless you continue to invite them as a collaborator.
- Making your tracks Forkable - think Adele covering Make You Feel My Love - in our minds, this is still collaboration, even if you aren't actively working on the project together as you have inspired someone else with your song-writing and they have applied their own spin on it.
I get the question a lot about whether online collaboration is dangerous - the following comment from the post above is one of the most common and more frustrating misunderstandings about BandLab when someone hears that there is "online collaboration":
Collaborating on an original idea is even far more dangerous, because now it will be unclear as to who really did what, if the partnerships breakdown. I 100% agree that any collaboration and any partnership is dangerous if things breakdown (bands, joint-ventures, marriages), but this is true for offline song collaborations too -
if you walk into a room and walk out with a song, how do you know or prove who really did what? BandLab was built exactly to address some of these issues - the beauty of our version control system is that because it's tracked in the cloud and each revision backed-up like GitHub (in a non-destructive manner) -
you actually have a very clear picture of who really did what AND when, far clearer than an offline method.

Creation is non-destructive because you can always go back a couple of versions and take a different creative direction (see the branches) - as opposed to static file structures where you continually save over each other's work in a linear manner.
So in a situation where there was a dispute as to what one party actually contributed, it's possible to go into the Tree View/Revision History and actually pull it up.
-----
I know this is a super long post, but I hope it's helpful! There's far more to BandLab than meets the eye and I'm happy to answer more questions as necessary when I spot them :-) I'm showing pictures of the web client right now, but do remember that one of the most exciting things for users is the fact that they can start a multi-track project on their phone, open it straight up on their desktop via their browser or BandLab Assistant instead of worrying about file transfers and compatibility issues - more on this another time.
Inspiration is everywhere, you just need to get rid of the barriers in the way of capturing it :-) that's what we're here for!