We've been quiet for a month. Here's what we were building

A few weeks after launching @Velo , we noticed something interesting.

People weren't using it alone.

They'd clone a voice, generate a few videos, then immediately ask:
"Can my co-founder use this too?"
"Can my editor access these assets?"
"Can the whole team share credits?"

At first, we thought they were edge cases.

They weren't.

The more people used Velo, the more obvious it became that content creation wasn't an individual workflow anymore.

The AI could move at incredible speed.

The bottleneck was collaboration.

Assets lived in different accounts.
Brand kits got recreated.
Teams shared logins.
The same voice clone got uploaded again and again.

The technology was solving creation.
It wasn't solving coordination.

So for the last month, that's what we've been focused on.

Today we're rolling out Velo for Teams

• Shared workspaces for brand kits, resources, and pooled credits

• Clone your voice and face once, then make them available to the whole team

• Shared libraries to organise videos and assets in one place

• Admin controls and member roles without the usual account-sharing headaches

One person sets it up.

The whole team can start creating minutes later.

We're doing a bigger launch push next week, but the Product Hunt community has supported us since day one, so I wanted to share it here first.

Curious - if you had a shared AI video workspace for your team, what's the first thing you'd use it for?

Watch our demo