network
.yaml
Conference networking reimagined as a searchable cluster. Attendees scan a QR code, deploy their config.yaml, and instantly discover connections based on shared values — editor, OS, language, school, region.
01 — Product surfaces
Four views. One cluster.
Conference networking is awkward because the useful context is hidden. network.yaml makes it visible immediately.
your network
A D3 force-directed graph centered on the current attendee. Every connected node shares at least one profile value. Stronger connections mean more shared values.
search the cluster
Full-text search across all attendee attributes — name, role, company, editor, OS, language, school, region. Every result is powered live by Elasticsearch.
QR check-in
Organizers create an event and get a unique QR code. Attendees scan, fill out their config, and are instantly indexed and visible to everyone else at the event.
config.yaml card
Every attendee profile is rendered as a YAML config card. Viewing someone else's profile shows shared values highlighted inline and a compatibility verdict.
02 — Network graph
Your connections,
force-directed.
D3's force simulation positions everyone based on shared profile values. The centre node is you. Thicker, brighter edges mean more values in common.
hover nodes to see shared values
03 — Architecture
One repo. Two Vercel services.
Frontend and backend live in the same repository, both deployed via Vercel Services. vercel.json routes /backend/* to FastAPI and everything else to React.
Browser
React · Vite · D3 · Three.js
Vercel React
frontend/ → mounted at /
Vercel FastAPI
backend/ → mounted at /backend
Elastic Cloud
Elasticsearch · profiles, events, search
04 — Elasticsearch
Elastic is the core,
not a bolt-on.
The app was designed around Elasticsearch from the start. Every attendee interaction — signup, search, match — goes through the cluster.
Storage
Attendee profiles, events, and check-in records stored as Elasticsearch documents
Search
Full-text profile search across all attendee attributes in real time
Matching
Related attendees derived from indexed profile value overlaps
Health
Cluster health checks expose whether Elastic is configured and reachable
05 — Team
$ git merge Merge_Conflicts
Three engineers. One hackathon. Everyone built everything.
HackerRivals Winner · Vancouver Cloud Summit 2026
Merge_Conflicts
3 engineers · 1 hackathon · 1st place
06 — Core flow
Scan. Deploy. Connect.
Organiser creates event
Generates a /checkin/{event_id} QR code
Attendee scans QR
New users complete config.yaml signup
Profile indexed
Stored as Elasticsearch document
Network appears
Force-directed graph of shared connections
Built in a hackathon. Deployed to a real event.
network.yaml was built for and used at the actual Vancouver Cloud Summit 2026. Real attendees, real connections.
View on GitHub