BoatMC is currently supporting a small number of approved private testers while we prepare the dedicated onboard appliance path. If BoatMC invited you or you already have a supported legacy beta install, continue normally. If you are new, message BoatMC on WhatsApp first so we can confirm your hardware and avoid a frustrating install.
Existing Cerbo/Signal K beta installs remain supported. Broad self-serve installs are intentionally not advertised as final yet.
You need a BoatMC account before the onboard monitor can report to us. If you just signed up, verify your email first. After signing in, use Install in the dashboard top bar to come right back here.
Sign in / Create accountBoatMC checks the hosted installer, this laptop, the selected boat, the install session, and the first live data check-in as you move through the install wizard.
Not seeing your boat? Add one in the dashboard first.
If your browser allows local HTTP probes, BoatMC can try the common marine endpoints. If not, use the Commander app for local discovery or skip straight to SSH if you already know the host IP.
Open Victron Remote Console at http://venus.local, paste the Cerbo installer, and let Venus OS handle the rest.
SSH to the Cerbo as root, then paste the Cerbo installer command.
For invited pilots with a known Signal K host. BoatMC support should confirm this path first.
Support-only beta path for known always-on Linux hosts. Not the default customer onboarding path.
For Cerbo GX installs, BoatMC needs the full Victron VRM Portal ID so it listens to the right local MQTT feed. Find it on the Cerbo at Settings › VRM online portal › Portal ID.
Paste the full 12-character value. Do not guess; copy it from the Cerbo screen.
Before you run the install command, verify these on your boat. Each one has caused real install failures we've seen.
Stuck on any of these? Use the install support box at the bottom of this page — it can use this install session's diagnostics when available.
We'll run a quick preflight (~30 seconds) before showing the install command, so we don't waste your time on a setup that's not ready.
Before you run the install command, let's verify your boat is ready. Each check should pass; if not, ask BoatMC support for one safe next step.
If you've completed setup manually and know everything is ready, you can skip preflight. The install command below will still try to validate before doing anything destructive.
BoatMC will refresh the device in place if it already has BoatMC, or install cleanly if it does not. It will not claim success until fresh boat data reaches BoatMC.
BoatMC Helper can open SSH from this laptop and run the installer on the target host for you.
BoatMC keeps these SSH credentials on this laptop only. They are not sent back to the BoatMC cloud.
Generating…
After install, BoatMC verifies the boat's outbound connection by waiting for the onboard monitor's first data check-in. If your boat firewall blocks outbound HTTPS to boatmc.com:443, the wizard will surface that automatically.
BoatMC is watching this install and will only call it done after fresh boat data arrives.
If this install gets stuck, BoatMC will check this install session and show one safe next step.
Approve safe stepUse this only if BoatMC support asks or you intentionally want to remove BoatMC after a test. It is safe by default: it stops BoatMC, removes BoatMC autostart, auto-detects Cerbo/Venus, Signal K, and generic Linux install locations, and moves BoatMC files into a timestamped backup folder. Your boat data is untouched.
BoatMC Helper can SSH from this laptop and run the safe remove command on one local device.
BoatMC keeps these SSH credentials on this laptop only. The command is allowlisted and cannot include purge options.
If BoatMC Helper is not running, copy the safe command below and run it over SSH or Remote Console on the device you want to clean up.
Generating…
Do not add purge options unless BoatMC support explicitly asks. The safe command below does not delete your boat data.
Stuck on a step? Ask anything about this private beta install. The goal is one safe next step, not risky guesswork or random commands.