I’ve been using various contact managers but they all feel like sales tools, so I built Nametag to track the people I actually care about - friends, family, colleagues. It maps relationships, tracks birthdays, and visualizes your network as an interactive graph.
Self-hosting highlights:
- Docker Compose setup - PostgreSQL, Redis, Next.js app. One command to start
- No email service needed - Accounts auto-verify, works completely offline
- Unlimited contacts - No artificial limits (hosted version caps free tier at 50)
- Complete data ownership - Your relationship data stays on your infrastructure
- Optional email - Can configure Resend if you want birthday/reminder emails
- No phone-home - Runs entirely on your network if you want
- AGPL-3.0 licensed - Full source access
Features:
- Track people with flexible attributes (name, birthday, contact info, notes)
- Map relationships between people (family, friends, colleagues, custom types)
- Interactive D3.js network graph visualization
- Custom groups for organizing contacts
- Birthday reminders (if you configure email)
- Dark mode, i18n (English and Spanish for now, but more are coming)
- Mobile-responsive
Tech stack:
- Next.js 16 (TypeScript)
- PostgreSQL + Prisma ORM
- Redis for rate limiting
- D3.js for graph visualization
- Tailwind CSS
Quick start:
git clone https://github.com/mattogodoy/nametag
cd nametag
# Edit .env with your secrets
docker-compose up -d
Database migrations run automatically on first start.
Access at localhost:3000.
There’s also a hosted version at https://nametag.one/ if you don’t want to self-host (helps fund development).
GitHub: https://github.com/mattogodoy/nametag
Happy to answer questions about the setup, architecture, or deployment!
Would you mind taking a look at this issue? https://github.com/mattogodoy/nametag/issues/15 I’m planning the implementation for CalDAV/CardDAV and have a few high level questions I’d like your opinion on. Thanks!
Sorry for the late reply. My wife has been keeping me busy with shit I don’t want to do. Looking at the conversation on github, I saw the first suggestion being the inclusion of pimsync into the docker compose file. I’m no developer, but it stands to reason that the same challenges remain if doing this because at the end of the day, pimsync is just a parser to sync with file systems, and for it to work with carddav the other party would still need to support carddav, right? So that idea is dead in the water. I am going to reply now to your 4 questions in the github. My handle is ‘mofongox’.