Vector Stream Systems logoVector Stream Systems

Model-Based Systems Engineering · AI-native · Human-in-the-Loop

Model-Based Systems Engineering, Accelerated by AI

VectorMBE connects your SysML models, signal databases, and spec documents into a living digital thread — formal traceability, hybrid graph and vector retrieval, and tool integration so requirements, architecture, and verification evidence stay in one governed graph for engineer review and approval.

What is MBSE?

Replace documents with linked, queryable models

Traditional engineering relies on Word docs, spreadsheets, and slide decks to capture requirements, architecture, and verification. MBSE replaces those static artifacts with formal digital models (requirements, architecture, behavior, and interfaces) linked together in a graph you can query, diff, and validate.

The result: less ambiguity, better traceability, and a single source of truth that scales with system complexity.

Why MBSE matters

  • 01 Reduces ambiguity from narrative-only specifications
  • 02 Improves traceability from intent to evidence
  • 03 Scales better for aerospace, automotive, and defense
  • 04 Enables automated validation and impact analysis

Why VectorMBE?

The autonomous layer your toolchain is missing

Semantic retrieval

Traditional MBSE tools are purely symbolic. VectorMBE adds embeddings so you can query by meaning, like "find subsystems similar to this performance envelope," not just by ID.

Agent-ready context

Coding agents need structured context, not PDF exports. VectorMBE exposes the graph via Model Context Protocol so agents reason over the same model humans review.

Hard constraints

When AI suggests a design change, CI gates verify design changes against safety margins and policy limits before they reach production. No silent violations.

Documents vs Models vs VectorMBE

CapabilityDocumentsTraditional MBSEVectorMBE
TraceabilityManual cross-referencesLinked model elementsQueryable graph + vectors
AI readinessNoneLow (symbolic only)Native (MCP + embeddings)
ValidationManual reviewStatic constraintsFormal constraints + CI gates
Version controlSharePoint / emailTool-specific exportsGit-native ontology diffs
Similarity searchNoneNoneVector ANN over designs

Install

Install VectorMBE

VectorMBE will be open source. The repository is currently private while we finalize the public release. GitHub Sponsors receive immediate repo access and can clone, build, and run locally today.

Docker (quickest, no build required)

Pulls the pre-built image radsilent/vectormbe:latest from Docker Hub. No Rust tool chain or source code needed. Includes Caddy reverse proxy. Pick your platform:

macOS

git clone https://github.com/radsilent/vectormbe-deploy.git vectormbe
cd vectormbe
cp .env.example .env
# Edit .env and set VECTORMBE_LICENSE_KEY
docker compose up -d

Requires Docker Desktop for Mac.

Windows

git clone https://github.com/radsilent/vectormbe-deploy.git vectormbe
cd vectormbe
cp .env.example .env
# Edit .env and set VECTORMBE_LICENSE_KEY
docker compose up -d

Requires Docker Desktop (WSL2 backend recommended) or WSL2 with Docker Engine.

Linux

git clone https://github.com/radsilent/vectormbe-deploy.git vectormbe
cd vectormbe
cp .env.example .env
# Edit .env and set VECTORMBE_LICENSE_KEY
docker compose up -d

Requires Docker Engine + Docker Compose.

VectorMBE Desktop (Tauri)

The desktop app bundles the server, web UI, and system tray into a single native application. Requires Tauri prerequisites (Rust, Node.js, WebKit/GTK).

1. Clone & build server sidecar

git clone https://github.com/radsilent/VectorMBE.git
cd VectorMBE
cargo build --release -p vectormbed

# Stage sidecar for the desktop bundle
mkdir -p src-tauri/binaries src-tauri/binaries/lib
cp target/release/vectormbed \
  src-tauri/binaries/vectormbed-x86_64-unknown-linux-gnu

Requires Rust 1.75+. CPU-only mode works without a GPU.

2. Build the desktop app

# Move into the cloned directory if you aren't already there
cd VectorMBE

# Install Tauri CLI if you haven't
cargo install tauri-cli

# Build the desktop app
cargo tauri build

Produces .deb, .rpm, and .AppImage under target/release/bundle/.

3. Run VectorMBE Desktop

VECTORMBE_LICENSE_KEY=<your-key> \
  VECTORMBE_REQUIRE_TORCH_GPU=false \
  ./target/release/vectormbe-desktop

A valid license key is required at startup. Contact Vector Stream Systems or visit pricing to obtain one.

Self-hosted server

Run the headless API server and web UI separately for remote access or CI integration.

Build & run the server

# CPU-only (no GPU required)
VECTORMBE_REQUIRE_TORCH_GPU=false \
  cargo run -p vectormbed

# GPU-enabled (auto-detects CUDA)
cargo run -p vectormbed

Default port is 8080. Override with VECTORMBE_PORT=<port>.

License key (required)

export VECTORMBE_LICENSE_KEY="your-license-key"

# Keys are generated per subscription and validated at startup.
# Contact [email protected] to obtain a key.

The server will not start without a valid license. Contact us or visit pricing.

MCP server setup

# Add to ~/.cursor/mcp.json or Claude Desktop config
{
  "mcpServers": {
    "vectormbe-runtime": {
      "type": "stdio",
      "command": "vectormbe-mcp",
      "args": [],
      "env": {
        "VECTORMBE_LOG_LEVEL": "info"
      }
    }
  }
}

See MCP setup docs for full config.

Verify

curl http://localhost:8080/openapi.json

You should see the OpenAPI spec. The UI dev server runs separately on port 5173.

Import formats

VectorMBE natively imports models from standard engineering interchange formats. Upload via the API or drop files into the import directory.

SysML v1 XMI · v2 / KerML XMI
UML 2.x XMI · Ecore / EMOF
Semantic Web RDF/XML · Turtle · N-Triples
Requirements ReqIF · CSV triples · JSON

Workflow

From zero to governed graph in 4 steps

1

Model your system in OWL

Define classes, individuals, and relationships. Start with requirements and architecture; add behavior and interfaces as you go.

2

Ingest evidence

Load simulation results, telemetry, and documents into the vector layer. Link them to ontology nodes for retrieval.

3

Define constraints

Encode hard constraints like temperature limits, stress bounds, and policy gates so no design ships without proof.

4

Connect your toolchain

Register VectorMBE MCP servers in Claude, Cursor, or your own host. Agents now reason over the same graph your team reviews.