Skip to content

What do you use for portfolio tracking? Spreadsheet isn't scaling

Domain Names by minh1987 5 replies 334 views
#1

I run 340 domains across 12 registrars. My spreadsheet broke. Too many manual columns. Renewal dates wrong twice, almost lost two domains.

In my country we use simple tools, but this portfolio is too big now. I need:
- auto import from registrar
- renewal alerts
- cost tracking per TLD

What do you use? Self-hosted preferred. Thank you.

phở at 3AM, deploy at 4
#2

Spreadsheet died at 400

Tried Notion, too slow. Tried Airtable, too expensive. Now I use:
- custom postgres db on my cheapest VPS
- grafana for dashboards
- alerts to telegram bot

Cost per domain: $0.003/month hosting. Compare to $15/month SaaS. No contest.

Chaos: I still forget to renew.io domains. Their reminder emails hit spam. Lost one last month. $120 aftermarket to get back.

seedbox, NAS, tape, and three offsite
3 #3

Fun little project: built a dashboard in docker

# docker-compose.yml
services:
  domaintrack:
    image: domaintracker:custom
    volumes:
      - ./domains.csv:/data/domains.csv
    environment:
      - ALERT_DAYS=30,7,1

It actually works. Pulls from registrar APIs, stores in sqlite, serves flask UI. Renewal alerts via ntfy. Took a weekend.

Config is just CSV. Registrar APIs are nightmare but doable.

works on my bench ¯\_(ツ)_/¯
#4

1. Tried many tools
2. Current stack:
2. A) Notion for notes
2. B) Actual database: postgres
2. C) Frontend: custom
3. Tried SaaS options:
3. I) too expensive
3. Ii) vendor lock-in
3. Iii) no API access
4. Self-hosted wins
5. My setup:
5. A) daily cron pulls from registrars
5. B) email alerts at 60/30/14/7/1 days
5. C) cost per TLD breakdown
6. @minh1987 recommend starting with simple script
6. I) expand later
6. Ii) avoid overengineering

#5

I use just a txt file

My VPS he crashed and I lost my spreadsheet, caramba! Now I use simple notes app, nossa! 47 domains only though, going to build something more fast when I have time

@tomchan your docker thing he looks nice, going to try

#6

Article 13 flashbacks. Any portfolio tool must comply with GDPR if it processes WHOIS data.

I reviewed three self-hosted options. All failed:
- no data retention policy
- no right-to-erasure for scraped data
- WHOIS history stored indefinitely

EU registrar data is especially sensitive post-GDPR. Your renewal alerts may violate Article 5(1)(e) if you keep data longer than necessary.

Recommend: purge logs after transfer completion. Anonymize historical pricing. Document your lawful basis.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft