Vantage

Privacy-first business dashboard. Get vantage on your shop, your business, your life — across the services you already use, with the data staying on your hardware.

Vantage by Seglamater Services LLC.

Status

Pre-alpha. The architecture, contracts, and first connectors are landing now. See docs/ARCHITECTURE.md for the design and Plane → VANTAGE for the roadmap.

The privacy story

Vantage encrypts your business data client-side. Connectors pull from the services you already use (Stripe, Google Workspace, Wave, Plane), encrypt each record on your own device with keys derived from your passphrase, and hand the hub only opaque ciphertext. The hub stores and quota-meters blobs it can never read. See docs/ARCHITECTURE.md for the full design and docs/BRAND.md for the positioning and the claims-discipline that keeps the privacy guarantee truthful.

Repository layout

vantage/
├── apps/
│   ├── vantage-hub/              # FastAPI backend — encrypted blob storage
│   ├── vantage-keys/             # Rust crate — client-side cryptography
│   ├── vantage-connector-sdk/    # Rust crate — connector framework
│   ├── vantage-connector-stripe/ # Stripe data feed
│   ├── vantage-connector-google/ # Gmail + Calendar data feed
│   ├── vantage-connector-wave/   # Wave accounting data feed
│   ├── vantage-connector-plane/  # Plane tickets data feed
│   ├── vantage-desktop/          # Tauri 2 dashboard app
│   ├── vantage-cockpit/          # Internal operator cockpit (server-reads, NOT E2EE)
│   └── vantage-marketing/        # getvantage.app static site
├── docs/                         # ARCHITECTURE.md, BRAND.md, etc.
├── vendor/
│   └── substrate-connector/      # Hash-pinned snapshot of the shared Connector primitive
└── scripts/                      # Vendored-crate drift checker + leak scan

vantage-cockpit is the internal operator cockpit, not the customer product. It reads on the server and is not end-to-end encrypted. Do not treat it as a template for customer-facing work.

Quick start (developers)

Requires Rust 1.75+, Python 3.11+, and Node with pnpm. Everything below runs from a fresh clone with no sibling checkouts and no network fetch of internal crates.

# Rust workspace — connector SDK, connectors, crypto crate
cargo build --workspace
cargo test --workspace

# Hub backend (FastAPI)
cd apps/vantage-hub
python3 -m venv .venv && .venv/bin/pip install -e ".[dev]"
.venv/bin/pytest

# Desktop dashboard (Tauri 2 + SvelteKit)
cd apps/vantage-desktop
pnpm install
pnpm test
pnpm build

On pnpm 10 and later, pnpm install installs everything but then exits non-zero with ERR_PNPM_IGNORED_BUILDS because esbuild has an unapproved build script. Run pnpm approve-builds once to clear it, or invoke the tools directly (./node_modules/.bin/vitest run, ./node_modules/.bin/vite build). The lockfile predates that policy; re-locking under current pnpm is tracked separately.

Verify the vendored shared crate has not drifted from its pinned upstream:

python3 scripts/check-vendor-substrate-connector.py check
python3 scripts/check-vendor-leakscan.py

Both exit non-zero on drift. vendor/substrate-connector/ is a distribution artifact, never a fork — edit the crate upstream and re-vendor through the reviewed procedure in docs/ARCHITECTURE.md.

License

AGPL-3.0-only, the license for all Seglamater products. See the LICENSE file at the repository root.

AGPL rather than GPL is deliberate: it closes the network-use gap. A party running a modified copy as a hosted service must publish their source — which is exactly the exposure for a self-hosted product someone could otherwise run as a competing SaaS. GPL-3.0 does not cover that case.

Declared once in [workspace.package]; every member crate inherits it via license.workspace = true, and vantage-hub and vantage-cockpit declare it in their pyproject.toml. vendor/substrate-connector remains independently MIT — vendoring it here does not relicense it, and MIT is compatible with an AGPL-3.0-only work.