Deployments
Launch a deployment and join its server
A deployment runs a build on a temporary Minecraft server for testing. Buildryn provisions the environment and installs the selected project’s build artifact. Each deployment runs for a limited time.
Before deployment
Section titled “Before deployment”- Resolve generated-change review and save manual edits.
- Produce a successful build containing the changes you want to test.
- Check required plugin dependencies.
- Check the remaining deployment allowance.
- Set your Minecraft Java username in Settings → Account.
- Prepare a client matching the project’s Minecraft version.
You need owner or editor access for server-management actions. Viewers cannot launch, extend, restart, or stop a session.
Start a deployment
Section titled “Start a deployment”- Open the project’s deployment controls.
- Choose Deploy now, or select
/deploymentin the chat command picker. - Wait while the status shows provisioning/deploying.
- Open the new deployment’s details.
- Wait for Online and a usable server address.
Deployment uses the latest available artifact. If you changed source after its build, build again first. Paper deployment checks required dependencies and can report missing optional integrations.
Expected result: an online dashboard showing the software, artifact, address, and time remaining.
Read the dashboard
Section titled “Read the dashboard”| Field or section | What it tells you |
|---|---|
| Status | Provisioning, online, stopping, stopped, or failure state. |
| IP address | The connection address once provisioning finishes. |
| Software | Server platform used by this session. |
| Artifact | The packaged build being tested. |
| Time left | Remaining session time. |
| Whitelist | Whether only allowed players can join. |
| Console | Live log output, commands, and metrics. |
| Files | Allowed runtime files and configuration. |
| Players | Connected/known players and access actions. |
| Worlds | World/dimension information and testing controls. |
Before testing a repair, check that the artifact field shows the build containing your fix.
Join from Minecraft
Section titled “Join from Minecraft”- Copy the server address using its copy control.
- Launch Minecraft Java Edition with the matching version.
- Open Multiplayer and choose Add Server or Direct Connection.
- Paste the full displayed address, including a port if shown.
- Connect and test the behavior you built in the project.
If access is blocked by the whitelist, check the exact Java username and allowed-player state. See players and worlds. To join, you need the required project access and an allowed Minecraft identity.
Deployment allowance and duration
Section titled “Deployment allowance and duration”The maximum initial deployment duration is 45 minutes on every plan.
Each launch counts toward the applicable plan allowance. Basic and Pro include deployments each month, including with annual billing. Free includes one deployment as a one-time allowance. Deployments use no credits.
Extend a session
Section titled “Extend a session”Extensions require eligible paid access.
- While the deployment is running, choose Add 15 minutes.
- Wait for confirmation and inspect the new expiration/time-left value.
- Continue testing within the displayed remaining time.
Check the updated countdown after the extension. A permitted extension can take the session beyond the plan’s initial duration.
Restart
Section titled “Restart”Choose Restart and confirm. A restart disconnects players until the server returns online. Reconnect and inspect startup output.
Restart is useful for testing persistence or configuration that loads on startup. It restarts the existing deployment; it does not compile or install newer project source, and it does not reset the session’s expiration.
Shut down and expiration
Section titled “Shut down and expiration”Choose Shut down, confirm, and wait for the stopped state. This disconnects online players and ends runtime. Closing a browser tab does not shut down the server.
Buildryn stops and cleans up the session when time expires. Save any configuration or logs you need before it ends, and keep persistent servers and worlds elsewhere.
History and logs
Section titled “History and logs”Open deployment history to inspect past sessions, states, dates, and artifacts. Use the log-download action for an entry when logs are available. A stopped session may offer captured logs even though it no longer accepts commands.
Before ending a problematic session, download relevant logs and record the deployment number. If provisioning fails, read the displayed failure and check the deployment allowance, artifact readiness, and required dependencies before retrying.
Continue with console and monitoring, players and worlds, and server files.