Install from Source

Building from source is for advanced users and contributors. The MIT core is the part you can audit; the Pro binary has additional compiled components. Both can be built from source.

Requirements

Python 3.11+
Rust 1.75+ (for the graph engine)
Git
4 GB RAM (for the Nuitka build — optional for development)

Clone the repository

git clone https://github.com/yadu9989/memstrata.git
cd memstrata

The repository structure:

memstrata/
├── core/          # MIT-licensed Python core (MCP server, dashboard, telemetry)
├── engine/        # Rust graph engine (MIT-licensed)
├── harness/       # Pro-only harness proxy (compiled separately)
├── extensions/    # VS Code and browser extensions
└── scripts/       # Build scripts

Build the MIT core (free tier)

cd core
pip install -e ".[dev]"
memstrata init
memstrata serve

The [dev] extras include the test suite and linting tools.

Build the Rust engine

The graph engine is a separate Rust crate that the Python core calls via PyO3 bindings:

cd engine
cargo build --release
# The built library goes to engine/target/release/
# Copy it to core/memstrata/engine/ for use with the Python package
cp target/release/libmemstrata_engine.so ../core/memstrata/engine/   # Linux
cp target/release/libmemstrata_engine.dylib ../core/memstrata/engine/ # macOS
copy target\release\memstrata_engine.dll ..\core\memstrata\engine\   # Windows

Build the Pro binary (Nuitka)

The Pro distribution is compiled with Nuitka for performance and EV signing. You need Nuitka and the Pro license:

pip install nuitka
cd core
python -m nuitka \
  --standalone \
  --include-package=memstrata \
  --output-dir=dist/ \
  memstrata/__main__.py

The Nuitka build produces a self-contained binary that doesn’t require Python to be installed.

EV signing (for distribution) is done in CI. If you’re building for personal use, you can skip signing.

Running tests

cd core
pytest tests/           # Unit tests
pytest tests/integration/  # Integration tests (requires a running harness)

The integration tests spin up a local harness on port 18080 to avoid colliding with a production instance.

Contributing

Pull requests are welcome for the MIT core and Rust engine. See CONTRIBUTING.md in the repository for the PR process, code style requirements, and which parts of the codebase are open for contributions.

The harness/ directory is not open to external PRs (it’s the Pro-only component), but bug reports are welcome.