BeatJam runs on our own decentralized compute.

Most AI music tools rent GPUs from one hyperscaler. We do not. We built and run our own chute on Bittensor subnet 64 - our model, our container, our weights - so BeatJam music is generated on decentralized, confidential compute that settles in TAO. The infrastructure is ours and it is running. What we are building now is the community around it.

Our own chute on subnet 64

A chute is a serverless GPU deployment on Chutes, the compute subnet of the Bittensor network. We are not reselling somebody else’s music API. We built our own deployment: our model, our container, our weights baked into the image so there is no cold download. It renders a full track in roughly 30 to 50 seconds once warm.

That makes us an operator on the network rather than a customer of one. We pin the exact model version you hear, roll it forward on our own schedule, and nobody can deprecate the endpoint out from under a song you are halfway through making.

Why we run it this way

Chutes runs on GPUs inside trusted execution environments. The prompt you type and the lyrics you write are processed in an enclave rather than sitting in plain view on a shared box - which matters if you are writing something you have not released yet.

The second reason is boring and more important: price discovery. Compute on an open network is bid for in the open. When a rail gets cheaper we can move to it without renegotiating a contract, and that shows up as cheaper plans rather than as somebody’s margin.

TAO-native from wallet to GPU

The whole chain can be crypto. Sign in with a Bittensor wallet instead of an email address, top up in crypto, and the compute itself settles in TAO, because Chutes bills in TAO. There is no point in the flow where you are forced to hand over a card.

Already in the ecosystem? The Bittensor music generator page covers wallet sign-in, and crypto checkout covers paying without a card.

The infrastructure is built. Now we are building the community.

The hard engineering is done: the chute exists, it is ours, and it makes music. What a subnet actually needs in order to prove itself is demand from people who are not in crypto - and that is the part we are building now. BeatJam is a consumer music app. People show up because they want a song for a video, not because they hold a token, and every one of those is ordinary demand landing on Bittensor.

Creators, miners, validators and subnet builders who want in on that are on the community board.

FAQ

What is a chute?

A chute is a serverless GPU deployment on Chutes, the compute subnet of the Bittensor network. You give it a container and a model, and it runs on demand across the network’s GPUs instead of on a machine you rent by the hour. BeatJam operates one.

Do you run your own deployment, or resell somebody else’s API?

Our own. We built the container, baked the model weights into the image and deployed it to Chutes on Bittensor subnet 64. That makes us an operator on the network rather than a customer of a music API.

Do I need TAO or a crypto wallet to use BeatJam?

No. Email sign-in and card payment work exactly as normal, and most people use those. Wallet sign-in and crypto checkout are there for the people who prefer them.

Is my prompt private?

The chute runs on GPUs inside trusted execution environments, so prompts and lyrics are processed in an enclave rather than in the clear on a shared machine. We also do not sell your prompts or train a public model on your tracks.

What is Bittensor subnet 64?

Subnet 64 is Chutes, the subnet of the Bittensor network that provides serverless GPU compute. Operators deploy containers to it and pay in TAO. BeatJam is one of those operators.