Launching today
Nodl
Stop explaining your system , Show it.
7 followers
Stop explaining your system , Show it.
7 followers
IT documentation is walls of text describing systems nobody can picture. Nodl turns your whole IT landscape into a living map: every system, the integrations and databases they share, and the changes that shaped them. Click anything to see everything connected to it, or just ask Canvas AI and it takes you straight to the answer. AI builds your first map from a CSV or Jira export, and a "nodl" label in Jira sends finished work to the canvas. Nothing lands without your review.
Hi Product Hunt!
Every system I've worked on had its documentation die the same way. Confluence pages, spreadsheets, diagrams. All snapshots, accurate the day they were made, drifting ever since, because updating them was a separate chore nobody had time for. Nodl is my answer, if the map is the place where work actually lands, it can't rot. The screenshots are Nodl documenting itself, apart from the last one, which is the live demo.
A few things I decided early and won't change: Nodl is not a Jira replacement, Jira tracks work and Nodl models the system that work lands in. Nothing touches your canvas without your review, not from AI import, not from Jira. Pricing is flat per organisation, no per user fees ever, because charging per person for documentation punishes exactly the sharing you want. And no tracking: no cookies, no analytics scripts.
For launch: the first 2 organisations to go Pro become founding customers, 12 months free with code Founding-Member.
Live demo at getnodl.app, no signup needed. One thing I'd love to hear: does the map match how you actually think about your systems?
honestly this looks pretty slick, the Jira to canvas sync is exactly the kind of thing my team would actually use. one thing i'd love though is some kind of change history diff view, like being able to see how a system and its connections looked last week versus now so you can spot when something got accidentally reconfigured.
Thanks Hüseyin!!
Glad the Jira sync landed, and to be clear about how it works; it's an inbox, not a live mirror. You tag items in Jira with a nodl label, they get pulled in, and nothing touches the canvas without a human reviewing it first. Jira is input, the canvas is the source of truth.
The history view you describe is already designed and near the top of the roadmap. A time machine mode where you drag a slider through time and watch the system build itself, nodes and connections appearing as they were added. Your releases show up as markers on the timeline. "How did this look last week versus now" is exactly the question it should answer. No promised date, but it's coming.
If your team gives it a try I'd genuinely like to hear how the Jira flow holds up on real data.
Being able to ask Canvas AI questions is great, but it would be even more useful if you could pin those answers as sticky notes right on the map itself. That way, recurring questions like "which services touch our payments database" could stay visible to the whole team instead of getting lost in chat history.
@selma1777037
Thanks Selma,
Good idea. Honest answer, AI answers are text today. They do not live on the map yet.
But the part about keeping recurring questions visible to the team already exists. That is what lenses are for. You tag the nodes and changes that answer a question, give the lens a name and a color, and anyone on the team can switch it on. The map dims to just that answer. "Everything touching payments" works well as a lens.
Having the AI paint its answer directly on the canvas is on our list. Sticky notes as a format I had not considered. Noted.
Finally something that makes our messy Confluence docs make sense. Dropped in a Jira export and the map actually showed connections our team never bothered to write down, which was kind of wild to see.
@hilalj1hg Thanks hilal. That moment is exactly what Nodl is built for. The connections everyone knows about but nobody wrote down are the ones that hurt later. Curious which one surprised you most.
Love the "nodl" label trick from Jira, that part feels really smart. One thing I'd love though is some kind of diff view so I can actually see what changed between two versions of the map when something breaks or a new system comes in. Right now I imagine I'd have to mentally compare snapshots which sounds painful for a large landscape.