Built for
the machine you are on

Every build is a single binary with the server, the CLI client and the MCP server, nothing else to install. Pick a platform if we guessed wrong.

curl -sSO https://dl.cameodb.com/mac/cameodb
chmod +x ./cameodb && ./cameodb

curl -sSO https://dl.cameodb.com/linux/cameodb
chmod +x ./cameodb && ./cameodb

curl.exe -sSO https://dl.cameodb.com/windows/cameodb.exe
.\cameodb.exe

Everything in this release

Built from commit f791b99 on 25 October 2026. Each artifact is cosign-signed and its SHA-256 is published.

deb, rpm and msi

Each one installs CameoDB as a service, so the node comes up under your init system or the Windows service manager rather than a terminal you have to keep open. Run the msi as an administrator: it installs the service and starts it.

# Debian / Ubuntu
curl -sSO https://dl.cameodb.com/linux/cameodb_0.3.8_amd64.deb
sudo dpkg -i cameodb_0.3.8_amd64.deb

# RHEL / Fedora / SUSE
curl -sSO https://dl.cameodb.com/linux/cameodb-0.3.8-1.x86_64.rpm
sudo rpm -i cameodb-0.3.8-1.x86_64.rpm
sudo systemctl enable --now cameodb

# Windows (PowerShell, run as Administrator)
curl.exe -sSO https://dl.cameodb.com/windows/cameodb-0.3.8-x64.msi
msiexec /i cameodb-0.3.8-x64.msi

Where it puts things

Get-Service CameoDB
Stop-Service CameoDB        # the same graceful shutdown as Ctrl+C
Start-Service CameoDB       # returns once the node is listening
Get-Content C:\ProgramData\CameoDB\logs\cameodb.$(Get-Date -Format yyyy-MM-dd).log -Wait

# silent install, with a log of its own
msiexec /i cameodb-0.3.8-x64.msi /qn /l*v cameodb-install.log

Every service restarts itself after a failure. Upgrading is installing the newer package: it stops the service, replaces the program and starts it again, and your config, data and logs stay where they are. Getting disk back after a large delete is on the Operate page.

Open it up
to your network

The packaged config is ready to listen on every interface. Mint a key, switch security on, check the config and reload, and the node is ready for other machines.

cameodb keygen --role admin         # prints the key once, and the config that accepts it
# add the printed [[security.api_keys]] entry to /etc/cameodb/cameodb.toml
# and set enabled = true under [security]
cameodb check-config -c /etc/cameodb/cameodb.toml
sudo systemctl reload cameodb       # new keys, no restart

cameodb check-config -c C:\ProgramData\CameoDB\cameodb.toml
Restart-Service CameoDB
New-NetFirewallRule -DisplayName "CameoDB" -Direction Inbound -Protocol TCP -LocalPort 9480 -Action Allow

To keep a node to one machine instead, set profile = "local" under [node] and bind_address = "127.0.0.1" under [network.http]. The security profiles explain what each posture expects.

Check it before
you trust it

Everything a security review asks for is published with the release. Nothing here needs to be requested.

curl -sSO https://dl.cameodb.com/cosign.pub
curl -sSO https://dl.cameodb.com/mac/cameodb.bundle
curl -sSO https://dl.cameodb.com/mac/cameodb.sha256

# beside the cameodb you downloaded
cosign verify-blob --key cosign.pub \
  --bundle cameodb.bundle cameodb

shasum -a 256 -c cameodb.sha256

# Linux: use linux/ in the URLs and sha256sum -c

Pick a channel

The same engine in every channel. Pick how you’d like to run it.