An audio node, not another music bot.

Separate audio processing from your Discord bot. Plan the client connection, credentials and resource use together.

Two components, two allocations

Your bot handles commands and Discord logic; Lavalink handles audio. If both run on Botkeep, each is a workload with its own share of the same plan. One free slot is not a free audio node on top of the plan.

Connect intentionally

A compatible client needs a host, port, password and matching TLS settings. The downloadable example binds to localhost and contains no usable password. Production endpoints must be issued and restricted by the future backend.

Sources and plugins are not automatic

Review source support and rights before use. The sample disables YouTube, arbitrary HTTP and local sources; YouTube support requires a separately reviewed plugin. Do not treat every URL as a permitted input.

Test concurrent audio

Player count, filters and encoding affect CPU and memory. No song count or audio-quality guarantee follows from a vCore allocation. Keep configuration backed up and cap log growth; tracks are not a permanent media library.

A community music setup

Discord bot → Lavalink client
                    ↓ authenticated connection
                Lavalink node

Two workloads → one shared resource budget

The configuration pack contains application.yml and a connection worksheet, not the binary or a music bot.

Plan your resources

Try a concrete starting point

Services

Lavalink

A guided audio-node configuration, separate from the Discord bot that uses it.

6 files · instructions includedExplore project

Bots

discord.js · /ping

A working slash-command bot with explicit registration and clean shutdown.

7 files · instructions includedExplore project

Enabled profiles can be deployed from the panel. Configure addresses and HTTPS in Domains; a custom domain requires DNS verification. No performance or availability guarantee is implied.