🛡️ StackCrest

Turn your tech stack into a heraldic crest.

Enter the technologies you build with and StackCrest forges a distinctive coat‑of‑arms — a real SVG shield with charges, a name band and a motto scroll — served from a stable URL. Drop one line of markdown in your GitHub README or portfolio. Same stack always makes the same crest. Free, no sign‑up, no trackers.

Pure SVG · deterministic · renders inline on GitHub. Source.

Forge your crest

Embed it

Paste it in your README. The crest links back to StackCrest, so anyone who sees it can forge their own.
Live preview — byte‑identical to the embedded image.

How it works

  1. Type your stack above. The crest updates live in the preview.
  2. Copy the one‑line markdown snippet.
  3. Paste it into your GitHub README, profile, or portfolio — it renders as an image.

Deterministic

The same stack always forges the same crest — field colour, division, and the charge for each technology are derived from a hash of the stack. No randomness, no surprises.

Just a URL

/crest.svg?stack=… returns a real image/svg+xml. There's no server state and no datastore — it's computed from the query string, so it caches well and renders anywhere an image does.

No trackers

No analytics, no cookies, no sign‑up, no fingerprinting. The image request carries only the params you put in the URL.

Safe by construction

Text is escaped, the tech list is capped, and unknown technologies still get a charge (by hash) — nothing breaks, nothing is uploaded.

Why this exists (honestly)

README decoration is a crowded space — github-readme-stats has 70k+ stars and skill-icons is everywhere. StackCrest doesn't pretend to replace them.

The bet is narrower: a distinctive crest artifact — a heraldic shield, not another row of logos — that other developers notice and want their own version of. The embed is the whole point: a crest in your README is an ad for the next person's crest. That's the only growth mechanism here, and whether it actually spreads is exactly what this small experiment is testing. No overclaiming.

FAQ

Is my stack uploaded anywhere? No. The crest is computed from the URL you build; there's no account and no logging of your inputs beyond ordinary web‑server request handling.

Will the same stack always look the same? Yes — it's deterministic. Reordering the list can change the layout, but the same list in the same order is always identical.

My technology isn't “known” — does it still work? Yes. Every token maps to a heraldic charge by hash, so anything you type gets a consistent emblem.

Can I use it off GitHub? Anywhere an image URL works — portfolio sites, blogs, Notion, GitLab, your CV as an SVG.