Official channels

The official repo, package path, and binary status — in one place.

This page only lists official MarlinSpike distribution surfaces with real links. You should be able to find the repository, source snapshots, deployment path, and the current binary status without guessing which channels are public yet.

Official repository

The canonical code and documentation surfaces.

These are the main public places to browse code, installation notes, and release history.

Official repo

Source repository

The public GitHub repository is the canonical source code surface for MarlinSpike, including the license, issues, and code history.

Open repository

Documentation

Docs and wiki

Product docs, deployment guidance, architecture notes, and release references.

Open wiki

Official doc

Install guide

Repository-side installation notes for operators who want the checked-in setup and environment details.

Read install guide

Official doc

Version history

Engine and web UI release notes are tracked in the repository until tagged binary releases are published.

Read release notes

Source downloads

Real source archives and related open-source components.

If you want MarlinSpike right now without waiting for packaged installers, these are the official source-level download surfaces and component repos that resolve today.

Download

Main branch zip archive

Download the current main branch as a zip snapshot when you want the source tree directly.

Download zip

Download

Main branch tarball

Grab the current main branch as a tar.gz source archive for Unix-friendly environments and scripted fetches.

Download tar.gz

Related source

Standalone DPI engine source

The packet-facing Rust DPI engine is published separately as marlinspike-dpi for teams that want that parser surface on its own.

Open DPI repo

Official packages

The supported deployment package path today.

MarlinSpike is not pretending to ship native package-manager artifacts yet. The official package surface today is the checked-in Docker deployment path and the files that back it.

Official path

Docker Compose deployment

The currently supported package and install path is source plus Docker Compose for server and lab deployments.

Open deployment docs

Manifest

docker-compose.yml

Review the checked-in Compose manifest used as the baseline deployment for the web application and PostgreSQL.

View compose file

Build file

Docker build recipe

Inspect the multi-stage Docker build that compiles the protected Python modules and assembles the runtime image.

View Dockerfile

Not published

Package registries

There are no official Homebrew, apt, yum, winget, Chocolatey, MSI, or similar package registry artifacts published right now.

Official binaries

Where binary releases will live, and what is not published yet.

The releases surface is real and public, but binary artifacts are not published there yet. This section makes the official binary channel explicit without implying installers, checksums, or release assets that do not exist.

Official channel

GitHub releases page

The official release surface already exists on GitHub, but it does not currently contain tagged binary artifacts.

Open releases page

Not published

Standalone binaries

No public Linux, macOS, or Windows standalone binaries are published today. The public install path remains source plus Docker.

Not published

OS installers and packages

There are no signed desktop installers or OS-native packages published yet for direct host installation.

Not published

Checksums and signatures

Checksum and signature files are not published yet because there are no public binary release artifacts to verify.

Official install path

Docker Compose is the published package path today

MarlinSpike is a shared web workbench, so the supported install story is still a Git clone plus Docker Compose on a field host, temporary VM, lab server, or internal staging system behind a reverse proxy.

$ git clone https://github.com/eris-ot/marlinspike.git
$ cd marlinspike
$ cp .env.example .env
$ docker compose up -d --build

Current public state

What you can and cannot get right now

The repo, source archives, docs, and Docker deployment path are all live. Tagged binaries, native package registries, and signed installers are not published yet.

Official repo is live
Zip + tarball archives are live
Docker path is official
Releases page is real
No binary assets yet
No native package-manager artifacts yet

More context?

Deployment, architecture, and the report contract live in the wiki.

The wiki covers deployment, architecture, the report artifact contract, and the broader project structure.

Open Wiki Official repo GitHub Releases