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.
See it live at memex.meshweaver.cloud — try the portal and read the full documentation 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 memex/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 memex/aspire/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.MonolithThe 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. The default (local-build) path needs a checkout, so the CLI runs straight from it:
./deploy/homebrew/bin/memex-local up
# …or symlink it onto your PATH: ln -s "$PWD/deploy/homebrew/bin/memex-local" ~/.local/bin/memex-localOpens at https://memex.localhost:8443. A Homebrew install (via a local tap) is
also supported — see deploy/homebrew for details.
Production deployment recipes live under deploy/:
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)
These are recipes, not the configuration of any running service. Point them at your own
infrastructure: copy deploy/aks/envs/example 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 over the REST API — read, search, mutate, compile, and mirror nodes from the shell:
dotnet tool install -g MeshWeaver.Cli --prerelease
memex login mw_yourtoken --base-url https://memex.meshweaver.cloud
memex search "nodeType:Agent"See src/MeshWeaver.Cli for the full command reference.
The framework ships as MeshWeaver.* packages on nuget.org — use them to build your own modules, node types, and agents against the mesh.
Join our Discord to discuss features, report issues, or get help. Licensed under MIT.