Built for
the machine you are on
Every build is one file: the server, the CLI client and the MCP endpoint, with nothing else to install.
-
Download, run, done
No runtime, no installer, no dependencies to chase. It listens on
:9480the moment it starts. - Signed, with its checksum beside it Copy the SHA-256 from the card, or check the cosign signature.
- A service when you want one deb, rpm and msi install it under systemd or the Windows service manager.
curl -sSO https://dl.cameodb.com/mac/cameodb chmod +x ./cameodb && ./cameodb
curl -sSO https://dl.cameodb.com/linux/cameodb chmod +x ./cameodb && ./cameodb
37f3aeb4745a1c0d4a5135d78ddcf4cdc5f393c6be7c818aa6cb97de85536fb7curl.exe -sSO https://dl.cameodb.com/windows/cameodb.exe .\cameodb.exe
Every file
in this release
Built from commit 6ce9097 on 15 November 2026. Old versions leave the server when a new one lands, so whatever is here is the build to run.
- Every artifact signed Binaries, packages and SBOMs, each with a cosign bundle beside it.
-
One file of checksums
SHA256SUMScovers the whole release, forsha256sum -cin one go. -
A manifest to read first
MANIFEST.txtlists the commit, the build time and every artifact with its size.
deb, rpm and msi,
running as a service
Each one runs CameoDB as a service, restarted after any failure. Upgrading is installing the newer package, and config, data and logs stay put.
sudo dpkg -i cameodb_0.3.10_amd64.deb sudo rpm -i cameodb-0.3.10-1.x86_64.rpm msiexec /i cameodb-0.3.10-x64.msiWhere it puts things →
0216068fa857218544de9fc02bc399d7c6b793119e3a10927104dab787983ba60b7edfe16cd9a6bacb0b5e2fe9a5dea04642df68309d91fdf4b407a5fb008fb806b7da0191c0614e0e6483f9160e1e1f36b7e1569fdec21873b4c2117376416dOpen it up
to your network
The packaged config already listens on every interface, as profile internal. Switch keys on and it is ready for other machines.
-
Mint a key
keygenprints the key once, and the config entry that accepts it. -
Check, then reload
check-configconfirms the posture, and a reload takes the new keys without a restart. -
Or keep it to one machine
profile = "local"under[node],bind_address = "127.0.0.1"under[network.http].
cameodb keygen --role admin # add the printed [[security.api_keys]] entry to # /etc/cameodb/cameodb.toml, with enabled = true under [security] cameodb check-config -c /etc/cameodb/cameodb.toml sudo systemctl reload cameodb
cameodb check-config -c C:\ProgramData\CameoDB\cameodb.toml Restart-Service CameoDB New-NetFirewallRule -DisplayName "CameoDB" -Direction Inbound ` -Protocol TCP -LocalPort 9480 -Action AllowWhat each profile expects →
Check it before
you trust it
Everything a security review asks for is published with the release, with nothing to request.
-
A signature per file
cosign verify-blobagainstcosign.pubproves the file is the one the release built. -
Its checksum beside it
A
.sha256per artifact, forshasum -con macOS orsha256sum -con Linux. - Every dependency, listed SPDX 2.3 and CycloneDX 1.7 SBOMs, each naming the 595 components inside, signed the same way.
$ U=https://dl.cameodb.com $ curl -sSO "$U/{cosign.pub,mac/cameodb.bundle}" $ cosign verify-blob --key cosign.pub --bundle cameodb.bundle cameodb Verified OK
One engine,
three ways to run it
Every channel ships the same engine. Pick the one that matches how much of the running you want to hand over.
General availability
Latest stable, signed builds: macOS, Linux and Windows binaries, plus deb, rpm and msi packages.
Enterprise · supported
The public engine with a support agreement: long-lived release lines, fixes backported to them, and a team on call. Get in touch to be part of it.
Managed · on-prem or cloud
CameoDB run for you, in your data centre or the cloud, with upgrades and monitoring under an agreed service level. Get in touch to be part of it.