tpt-boxcar
RustTPT Boxcar — a monorepo of five open-source tools for the full app lifecycle: local sandbox (OCI + Wasm), state/connection proxy, eBPF observability, automated image distiller with LLM analysis, and a Wasm-native edge service mesh & API gateway.
Languages
TPT Boxcar
An open-source, unified cloud-native tooling suite — from local development to the edge.
Overview
TPT Boxcar provides five integrated products that cover the full application lifecycle:
| Product | Description | Stack |
|---|---|---|
| TPT Origin | Unified local sandbox — OCI containers + Wasm side by side | Rust, containerd, Wasmtime, eBPF, Tauri |
| TPT Tether | State & connection proxy for Wasm workloads | Rust (Tokio), WIT, Go control plane |
| TPT Scope | Hybrid eBPF observability — zero-code distributed tracing | Rust/Go eBPF, OTel, ClickHouse, React |
| TPT Chisel | Automated image distiller & Wasm migrator | Rust, AI/LLM analysis (Ollama, Claude, OpenAI) |
| TPT Frontier | Wasm-native edge service mesh & API gateway | Rust (Hyper, Tokio), Wasmtime, Go xDS |
Quick Start
git clone https://github.com/tpt-solutions/tpt-boxcar.git && cd tpt-boxcar
cargo build --workspace # Origin, Chisel, Tether/Frontier data-plane libs
go build ./... # Tether, Scope, Frontier control planes
That builds everything, but doesn't run anything yet. Pick a product below and follow its 5-minute quickstart — each is independently runnable:
| Product | Try it in 5 minutes | What it demos |
|---|---|---|
| Origin | cargo build -p tpt-origin && tpt origin init --dir demo && cd demo && tpt origin up | Spin up a local sandbox mixing OCI containers and Wasm modules from one manifest |
| Chisel | cargo build -p tpt-chisel && chisel analyze <image-dir> && chisel distill <image-dir> --dockerfile | Distill a container image into a minimal, Wasm-migration-aware image with SBOM + CVE scan; chisel migrate/chisel audit add LLM-generated migration/security plans |
| Frontier | go run ./frontier/control-plane then curl in a route/upstream from frontier/examples/getting-started/ | Configure an edge gateway route through REST/gRPC |
| Tether | go run ./tether/control-plane then curl in a backend/route from tether/examples/ | Register a DB backend + route for the Wasm-facing connection proxy |
| Scope | go run ./scope/backend/cmd/ingest + cmd/backend, then send an OTLP trace | Query traces/metrics/logs ingested from a running service |
We deliberately don't ship a Docker/docker-compose quickstart — Origin's whole point is replacing container tooling with containerd + Wasmtime directly, so bootstrapping the demo through Docker would undercut the pitch. Instead, examples/demo-stack/manifest.yaml brings up Scope's ingest/query API and Frontier's control plane together as real child processes through Origin itself:
cargo build -p tpt-origin
# requires a ClickHouse server at 127.0.0.1:9000 — Origin's OCI runtime doesn't spawn one yet (see origin/README.md)
./target/debug/tpt origin up --manifest examples/demo-stack/manifest.yaml
This works today because Origin's type: process service kind spawns and tears down real OS processes (unlike type: oci/type: wasm, which are still bookkeeping-only pending containerd/Wasmtime integration).
AI agent integration (MCP)
mcp-server/ exposes all five products as MCP tools over stdio, so an AI agent (Claude Code, Claude Desktop, etc.) can drive them directly — start a sandbox, distill an image, configure a gateway route, query traces — instead of a human running curl/CLI commands by hand.
cd mcp-server && go build -o mcp-server .
Then point your MCP client's config at the built binary. See mcp-server/README.md for the full tool list and configuration options.
Products
| Product | Description | Docs |
|---|---|---|
| Origin | Unified local sandbox — OCI containers + Wasm side by side | origin/README.md |
| Tether | State & connection proxy for Wasm workloads | tether/README.md |
| Scope | Hybrid eBPF observability — zero-code distributed tracing | scope/README.md |
| Chisel | Automated image distiller & Wasm migrator | chisel/README.md |
| Frontier | Wasm-native edge service mesh & API gateway | frontier/README.md |
Monorepo Structure
tpt-boxcar/
├── origin/ # TPT Origin — local development sandbox
│ ├── core/ # Rust core engine
│ ├── cli/ # CLI binary
│ └── gui/ # Tauri desktop GUI
├── tether/ # TPT Tether — state & connection proxy
│ ├── proxy/ # Rust data plane (Tokio)
│ └── control-plane/ # Go control plane
├── scope/ # TPT Scope — observability
│ ├── agent/ # Rust eBPF collection agent
│ ├── backend/ # Go query API + ClickHouse
│ └── dashboard/ # React + TypeScript frontend
├── chisel/ # TPT Chisel — image distiller & Wasm migrator
│ ├── core/ # Rust core engine (analysis, distillation, AI orchestration)
│ └── cli/ # CLI binary
├── frontier/ # TPT Frontier — edge service mesh
│ ├── proxy/ # Rust data plane
│ └── plugin-sdk/ # Plugin SDK crate
├── mcp-server/ # MCP server exposing all 5 products as AI agent tools
├── examples/ # Cross-product examples (e.g. demo-stack/ for Origin-driven demos)
└── docs/ # Documentation site (Docusaurus)
License
Apache 2.0 — see LICENSE.