MeshWeaver is an open-source framework for building data meshes: documents, data, code, AI agents, and UI live together as addressable nodes on a mesh — versioned, collaboratively editable, vector-searchable, and processed by an actor-model message hub with a reactive Blazor UI. Memex, the portal application included in this repository, is a knowledge portal built on it where people and AI agents work on the same content.
Read the full documentation online at memex.meshweaver.cloud/Doc. The same docs are in this repo under src/MeshWeaver.Documentation/Data/.
git clone https://github.com/Systemorph/MeshWeaver.git
cd MeshWeaver
dotnet run --project ../MeshWeaver.Plugins/src/Memex.Portal.MonolithOpens at https://localhost:7122. Single process, no Docker — if you are unsure which setup to pick, pick this one.
For the microservices setup orchestrated with .NET Aspire (requires Docker):
dotnet run --project ../MeshWeaver.Plugins/src/Memex.AppHostPortal at https://localhost:7202, with PostgreSQL persistence and the Aspire dashboard.
dotnet new install MeshWeaver.MemexTemplate
dotnet new meshweaver-memex -n MyPortal
cd MyPortal
dotnet run --project MyPortal.Portal.Monolith
⚠️ The template is not on nuget.org right now — see the NuGet section below.
The template contains the complete Memex portal solution (Blazor Server monolith + Aspire microservices, Graph + AI integration), renamed to your project name.
A prod-like stack on Colima k3s, run by memex-local — which lives with the Helm chart in the
public MeshWeaver.Deploy repository. Check it out
beside this one (the local-build path finds ../MeshWeaver on its own) and run:
../MeshWeaver.Deploy/deploy/homebrew/bin/memex-local up
# …or install it: brew tap systemorph/memex && brew install memex-localOpens at https://memex.localhost:8443.
Production deployment recipes live in the public MeshWeaver.Deploy repository:
deploy/helm— generic Kubernetes/Helm chart (Azure-free self-host)deploy/aks— production-grade AKS sample (private cluster, P2S VPN, ACR, pgBackRest PITR)deploy/aca— Azure Container Apps (Bicep)deploy/compose·deploy/compose-ha— Docker Compose (single-node / HA)deploy/ocr·deploy/ollama·deploy/whisper·deploy/s1-extract— the optional service images an instance runs beside its portal
These are recipes, not the configuration of any running service. Point them at your own
infrastructure: copy the example environment (deployments/aks/example/ in the private Systemorph/Memex
deployments repository; it left this repository with the core-slimming carve) to your own environment
folder and fill in your values. The files that carry real per-environment values —
values.<env>.yaml, secretproviderclass.yaml — are git-ignored and never committed here.
The AKS material is deliberately written as a worked example rather than an abstraction, so parts of it name the cluster and hosts it was first proven on. Read those as illustration; they are not config you inherit, and nothing in this repo is authoritative about a live installation.
If you are self-hosting, the recipes above plus your own values are the whole story.
If you are operating an installation Systemorph runs, its per-environment configuration and the record of what runs where live in the private Systemorph/Memex repo. Start there.
The memex CLI operates any portal's mesh from the shell — its mesh commands are generated at run
time from the connected instance's MCP tool catalog — and builds plugins inside the platform image.
It is a dotnet tool, MeshWeaver.Cli, with its own version. Its first stable release, 3.1.0, is
not on nuget.org yet — see
NuGet Package Retirement §1a;
once it is:
dotnet tool install -g MeshWeaver.Cli
memex login mw_yourtoken --base-url https://portal.example.com
memex search "nodeType:Agent"Its source and its publish lane live in Systemorph/MeshWeaver.Plugins (src/MeshWeaver.Cli,
published together with the Aspire integration). In CI the same verbs come from the
mw-plugin-test container image, which is what every pipeline here actually runs.
MeshWeaver publishes exactly two packages, and they are the two you start from:
| Package | What it does |
|---|---|
MeshWeaver.MemexTemplate |
dotnet new install MeshWeaver.MemexTemplate — scaffolds a portal solution |
MeshWeaver.Aspire.Hosting.Memex |
builder.AddMemex() — the Aspire integration that runs the portal, its database and its migration |
⚠️ MeshWeaver.MemexTemplateis not resolvable right now. Its last published version is3.0.0-rc7and every version of it is unlisted, sodotnet new install MeshWeaver.MemexTemplatecannot find it. Two reasons: its pack target was broken (it never passed the generator the platform checkout it requires — now fixed), and republishing it is blocked on an open decision, because the template can only be generated together with a UI project that currently lives in a private repository (#3653 and NuGet Package Retirement). Until that is answered, generate the template from a checkout —tools/generate-memex-template.csin MeshWeaver.Plugins.
The framework itself is not distributed as libraries. It ships as a container image: your mesh
content compiles against the running portal, plugins ship as module bundles, and startup
configuration is expressed as options on the Aspire integration rather than as package references.
The forty-three MeshWeaver.* library packages published up to 3.0.0-rc13 are retired and unlisted
— existing exact-version pins keep resolving, but nothing new is published under them. See
NuGet Package Retirement.
Licensed under MIT.