Deploying and running
How a deploy works, where your bot runs, and how to check that it's healthy.
What a deploy does
Compile. Buildcord compiles every enabled flow into a blueprint.
Check. The blueprint goes through the shape and reference checks. Errors stop the deploy and tell you which flow and step to fix.
Register. Buildcord registers your slash commands with Discord.
Run. The new version starts taking new runs. Runs already underway finish on the version they started on.
Where a bot runs
| Bot kind | Where it runs |
|---|---|
| Commands only | On a shared runner. Discord delivers commands and button presses to it. |
| Gateway | On a machine of its own, connected to Discord, in the region you choose. |
See Plans for what each costs and which flows need the gateway.
Bot tokens are stored encrypted. Bots' own machines have no public address, so you check their health in the bot's status in the builder.
Adding the bot to a server
After a deploy, the builder shows an invite link that asks for exactly the permissions your flows use. Open it, choose a server, and approve.
Checking service status
Each Buildcord service answers GET /health with 200 while it's up.
| Service | Address |
|---|---|
| API | https://api.buildcord.dev/health |
| Telemetry | https://telemetry.buildcord.dev/health |
| Builder | https://app.buildcord.dev/health |
| Site | https://buildcord.dev/health |
The live status of every service is on the status page linked from the site's footer.