PointSav Design System
Español

Install

Self-host

app-privategit-design is the same engine that runs design.pointsav.com. Build the binary and point it at your own vault directory. It then serves your design system's token gallery, component docs, Writing/Paper content, and an on-prem MCP endpoint directly from your own infrastructure. Your tokens, your change history, your perimeter — a small VM, a spare rack unit, or a laptop repurposed as a server. No cloud dependency, no managed database, no account rep to call.

Quickstart

Build the binary, point it at a vault directory, and it's running.

There is no installer wizard and no license-key activation step. The binary reads three environment variables and starts serving.

Terminalbash
$ git clone https://github.com/pointsav/pointsav-design-system.git
$ git clone https://github.com/pointsav/pointsav-monorepo.git
$ cd pointsav-monorepo && cargo build --release -p app-privategit-design
$ DESIGN_VAULT_DIR=../pointsav-design-system/dtcg-vault \
  DESIGN_BIND=127.0.0.1:9094 \
  DESIGN_SITE_ORIGIN=https://design.example.com \
  ./target/release/app-privategit-design
# serving on 127.0.0.1:9094
# Tokens, Components, Writing, Paper + on-prem MCP endpoint, all from this process
Why one binary

One binary replaces the database, cache, and per-seat meter.

A typical hosted design-system platform asks a short-staffed team to run a second stack alongside the actual design work.

Typical stack vs. this server
Typical hosted platform
  • Managed Postgres instance to provision and back up
  • Redis (or similar) for sessions/cache
  • Per-seat monthly meter
  • Design data lives on a vendor's infrastructure
  • An AI agent query travels to a third party's servers for an answer
app-privategit-design
  • No Postgres — state lives in the vault's own Git-tracked files
  • No Redis
  • No per-seat meter for the FSL-1.1-ALv2 source
  • One binary, your own infrastructure
  • On-prem MCP endpoint — agent queries stay on your own network

Comparing typical hosted-platform architecture in general terms; verified against this crate's own Cargo.toml — no database or cache driver dependency exists in the real dependency tree.

What it takes to run

Modest hardware, real licensing terms.

Hardware footprint: a single Rust binary with no database or cache process to run alongside it — the dependency tree carries no Postgres/Redis driver. No GPU or cluster is required to serve the design-system content itself.

License: the source ships under FSL-1.1-ALv2, converting automatically to Apache-2.0 two years after each release. Design tokens are licensed separately, under Apache-2.0. See the full licensing breakdown for the commercial tier and what FSL does and doesn't restrict.

What's next

Walk through the token set that ships with the binary, or see how an AI agent connects to the on-prem MCP endpoint once it's running.

Explore Tokens Connect your AI agents
Important Information

Design System disclosure

This site provides open-source design tokens, documentation, and self-hostable software published by Woodfine Capital Projects Inc. Information here is for general reference only and does not constitute an offer, warranty, or a guarantee of fitness for any particular purpose. Statements regarding planned, intended, or targeted future features are forward-looking and subject to change without notice; they are not undertaken to be updated except as required by law.