PLOMID for macOS, Windows, and Linux — plus Docker and source. These are the free Community edition builds: take the file below, check its checksum, or install with one command.
One tab per platform, all on v0.1.0-beta.1 unless
you pick another release. Your tab opens automatically; the file
detection picked carries the copper mark.
macOS
2 packagesDisk images. Pick silicon or Intel.
.dmg
macOS · Apple silicon
arm64 · macOS 12 and newer
Universal macOS build, Apple silicon path. Drag to Applications.
Prefer a package manager? Homebrew, apt and winget repositories are published on the
releases page, alongside the SHA256 checksum for every file above.
Every button here resolves to the newest published release; older ones live in the
version archives below.
Version archives
Every release, from GitHub.
Every published release, newest first — files, checksums, and notes.
Reading releases from GitHub…
No published releases yet — files appear here the moment one ships.
Watch the repository →
Every artefact ships with a SHA256 checksum on the releases page. Hash what you received
and compare — if the two differ, do not install it.
01
Download + checksum
Every file on the releases page ships with its SHA256 checksum beside it. Keep both.
02
Check before you run
Hash the file you received and compare it with the published value. If they differ, do not run it.
03
Install
Only then open the installer or unpack the archive. The first-run steps below take it from there.
macOS · check the fileverify.shshell
shasum -a 256 <file>
Linux · check the fileverify.shshell
sha256sum <file>
System requirements
Platform
Minimum
Artefact
macOS
12+ · Apple silicon
arm64 · .dmg
macOS
11+ · Intel
x64 · .dmg
Windows
10+ · 64 bit
x64 · .exe / .zip
Linux
Debian · Ubuntu / RHEL · Fedora · SUSE / any distro, x64 or ARM
x64 · .deb / .rpm / .tar.gz · arm64 · .tar.gz
Docker
Any host with Docker
image
Client
Any Postgres client
psql or driver
Checksums for every file ship in SHA256SUMS.txt on the release. See all downloads →
First run
From install to first query.
One binary, one process. Start it, connect any Postgres client, and
read the docs for flags and connection details.
01 · plomid-server
Start
Starts in the foreground with built-in defaults. Flags and PLOMID_* variables override them — the docs list every one.
02 · psql
Connect
Connect with any Postgres client. Connection strings and client examples live in the docs.
03 · --data ./live
Keep your data
Storage and the write-ahead log live under --data. Point it somewhere durable; the docs carry the full flag matrix.
Prefer the command line? The install methods above
cover the shell script and Docker; the
playground runs the same statements in your
browser, useful for checking the query surface before installing anything.
Questions
Which file, and what if it is wrong.
The short answers. Longer ones live in the docs and on the releases page, which is the
source of truth for versions and checksums.
Take the card this page highlighted for you: Apple silicon or Intel on macOS, the signed .exe on Windows, .deb for Debian/Ubuntu, .rpm for RHEL/Fedora/SUSE, or .tar.gz anywhere else on 64-bit Linux. Unsure? The matrix above lists every file with its OS and architecture.
Each release publishes a SHA256 checksum beside every file. Run shasum -a 256 <file> on macOS or sha256sum <file> on Linux and compare the two values. If they differ, delete the file and download again.
Homebrew, apt and winget repositories are published alongside the artefacts on the releases page. The direct files on this page are the same release line, versioned together.
The binary is the fastest path on your own machine; Docker is the fastest path anywhere else — same release line, same query surface. Connection details and client examples live in the docs.
This release line ships 64-bit Intel builds for Linux and Windows, both silicon paths for macOS, and a static ARM tarball for Linux. Windows ARM has no native package yet — run the Docker image or build from source. The system requirements table above states the minimum OS for each file.
Beyond the binary
Running it in production.
Self hosted production deployments, with residency as declared policy, enterprise support
and integration with the systems your business runs, start with a conversation. Managed,
operated deployments are on the roadmap and shaped with those same partners.
Residency as policy Enterprise support Integration help