Launching today
Nexus
One visual graph for all your projects
39 followers
One visual graph for all your projects
39 followers
Nexus maps your software projects and every service they depend on in one visual graph. Click any node to open its dashboard. No account needed, your data stays in your browser. Free for up to 3 projects.
Free Options
Launch Team / Built With
CloudflareDeploy serverless functions globally in seconds
Promoted
Hey Product Hunt, I'm Florian, the maker of Nexus 👋
I run several side projects and kept losing track of which database, deployment and domain belonged to which one. Every project comes with a constellation of services: hosting, a database, a registrar, payments, analytics, social accounts. Nexus puts all of it on one visual graph. Click any node and the dashboard opens in a new tab.
It is deliberately a map, not another dashboard to maintain. There are no API integrations, so adding a service takes five seconds and never breaks.
What's in it today:
Graph and grid views that stay in sync (grid adds link health checks and screenshots)
Press N, paste a URL, done. Drag nodes, collapse projects, filter by tag, search, undo and redo
Local-first: no account, no tracking cookies, your data stays in your browser. JSON export and import, optional cloud sync
Free for up to 3 projects. Pro is €5/mo, or €29 once for lifetime
I'd love to hear two things: how many projects and services are you juggling right now? and what would you want to see on your map next?
I'll be here all day answering every comment. Thanks for taking a look! 🙏
Quick question for anyone juggling a few projects: where do you keep track of which dashboard, database and domain belongs to which one today? Bookmarks, Notion, or just memory? Curious what you’d want on your map first.
I'm juggling about eight side projects right now, and the part that always breaks for me is exactly this — coming back to one after a few weeks and having to re-derive which database, deploy and domain belong to it. A map instead of another dashboard to maintain is the right call, and local-first with JSON export makes me comfortable putting that inventory in it. What I'd want on the map next is domain and cert expiry dates, so a lapse is the thing I notice before it breaks something.
@jcbuilds Thanks for such a thoughtful comment! Eight side projects is exactly the situation I built Nexus for, and "coming back after a few weeks and re-deriving everything" was my own pain too.
Expiry dates are a great idea, and I’d start simple: a date you enter yourself for any service (domain, cert, hosting plan), with a visible warning on the node when it’s getting close. That keeps Nexus local-first and API-free, so it never breaks. Would a manual date be enough for you, or would you really want it checked automatically?