Downloads
This page provides operator downloads for Vexillum releases, including prebuilt binaries and example configuration files.
Use these files when setting up a new Vexillum reflector or updating an existing deployment.
Current release - development x.x.1x
Section titled “Current release - development x.x.1x”Codename: [arias]
Section titled “Codename: [arias]”During the development cycle, only 64-bit Linux amd64 binaries are provided.
Section titled “During the development cycle, only 64-bit Linux amd64 binaries are provided.”| File | Distribution | SHA256 Checksum |
|---|---|---|
| vexillum-linux-amd64 | Linux amd64 | 4538304f5cb11b8d3699f0f650dcc29057b0a109097dc2ccc140c9837048d3ca |
| vexillum.toml Example | All |
Vexillum binary
Section titled “Vexillum binary”The Vexillum binary contains the reflector runtime.
After downloading, make the binary executable:
Check that it runs:
Start Vexillum:
Optionally, start Vexillum with a specific configuration file:
Example TOML configuration
Section titled “Example TOML configuration”The example vexillum.toml.example file provides a starting point for
configuring a Vexillum deployment.
It includes settings for:
- Runtime name
- Logging
- Database storage
- Admin web listener
- Public API listener (including CORS and rate limiting)
- Metrics listener
Download the example configuration and edit it before starting Vexillum:
Do not blindly run the example configuration on a public server without reviewing listener addresses, exposed ports, and bootstrap credentials. That is not deployment, that is feeding the internet.
Basic installation layout
Section titled “Basic installation layout”A simple Linux installation can use /opt/vexillum:
Create a dedicated service user:
First start
Section titled “First start”Before the first start, set a bootstrap admin password:
Then start Vexillum:
The admin interface is usually available at:
The metrics listener is usually available at:
Default listeners
Section titled “Default listeners”A Vexillum installation uses these as the defaults for listeners:
| Service | Default listener |
|---|---|
| Admin web | 127.0.0.1:8080 |
| Public API | 127.0.0.1:8081 |
| Metrics | 127.0.0.1:9090 |
| D-Star DExtra | 0.0.0.0:30001 |
| DMR | 0.0.0.0:62031 |
| M17 | 0.0.0.0:17000 |
| NXDN | 0.0.0.0:41400 |
| P25 | 0.0.0.0:41000 |
| YSF | 0.0.0.0:42000 |
| VAFM UDP | 0.0.0.0:43000 |
| VAFM TCP | 0.0.0.0:43000 |
| VAFM TLS | 0.0.0.0:43443 |
| VAFM DTLS | 0.0.0.0:43443 |
Only expose the protocol ports required for the modes you actually run.
Keep the admin and metrics listeners private unless you have intentionally placed them behind a reverse proxy, VPN, firewall rule, or other access control.
Recommended verification
Section titled “Recommended verification”After starting Vexillum, confirm the service is listening:
Check the admin health endpoint:
Check the metrics listener:
Review logs if running under systemd:
Running as a systemd service
Section titled “Running as a systemd service”A basic systemd service can look like this:
Install it as:
Check status:
After the bootstrap password has been rotated, remove the bootstrap password from the service environment if it is no longer needed.
Upgrade notes
Section titled “Upgrade notes”Before replacing an existing Vexillum binary:
- Read the release notes.
- Back up the TOML configuration file.
- Back up the SQLite database or configured storage.
- Stop the service.
- Replace the binary.
- Start the service.
- Check logs.
- Confirm the admin interface, metrics listener, and enabled modes are working.
Example:
Checksums
Section titled “Checksums”Checksums are provided, verify downloads before running them.
Example:
Compare the output against the published checksum for the release.
Skipping checksum verification is technically faster, in the same way driving with your eyes closed is technically less visually distracting.
Next steps
Section titled “Next steps”After downloading and starting Vexillum:
- Rotate the bootstrap password.
- Create named admin users.
- Review the example configuration.
- Enable only the modes you plan to run.
- Configure firewall and NAT rules.
- Keep the admin and metrics listeners private.