Wenodify
The product brand and public site (wenodify.peacae.com). Part of the Peacae.com family from Wekify LLC.
About Wenodify
A studio for maps and family trees — built for relationships, not documents.
Wenodify Studio runs in your browser with two canvases: Idea Map for structured content and Family Tree for genealogy. Add nodes, connect branches, fill in labels and notes, then export JSON or SQL when you are ready.
Part of the Peacae.com family of products from Wekify LLC.
How to read the name
Brand · verb · tool
Wenodify is the brand · nodify is the act · Studio is where you work.
nodify
To nodify is to work on the canvas — add nodes, branch, relate, label, note, and lay out a map or tree.
Wenodify Studio
The in-browser workspace where you nodify: Idea Map, Family Tree, export, and local-first editing.
Where it came from
We needed a place to think before the database.
Wenodify is part of the Peacae.com family of products from Wekify LLC. Wekify's work includes language preservation — holding cultural and linguistic knowledge in forms people can learn from and return to. We kept authoring rich, branching content inside the same platforms meant to preserve and deliver it. Those surfaces became crowded: mapping, editing, storing, and running experiences all fought for the same UI.
Wenodify started as a deliberate split. A dedicated studio for relationships and structure. Export as the handoff. Platforms that stay specialized for preservation and delivery. We are not competing with whiteboard or genealogy apps — we are building the toolchain we will use ourselves.
We from Wekify, nodify from nodes. The brand is Wenodify; the verb is nodify — add nodes, branch, relate, and shape a map or tree on the canvas. Wenodify Studio is the tool; nodify is what you do in it.
How it fits together
What Studio does
Map, edit, and export — all in the browser. No account required; your work stays local until you choose to download it.
Map on the canvas
Start with a root node. Add children, partners, and branches — Idea Map for structured content, Family Tree for genealogy.
Edit and organize
Labels and notes on every node. Collapse branches, search the map, auto-layout, undo — stay in flow while the structure grows.
Export your work
Download JSON to keep editing later, or SQL with an export profile. Import a file back anytime to pick up where you left off.
Idea Map · six graph types
Same tree. Different meaning at export.
Idea Map covers six graph types on one canvas — pick the shape that matches how your content will be delivered downstream.
Ideas
Concept maps and outlines. Label = topic; body = notes.
Conversation
Scripted dialog and guided scenes. Label = spoken line; body = delivery notes.
Chatbot
Interactive bots with reply options. Label = prompt or option; body = bot response.
Quiz
Branching assessments. Label = question; body = choices and feedback.
Steps
Procedures and lesson paths. Sibling order matters.
Explorer
Browse-by-topic trees. Label = entry; body = summary or reference.
Family Tree · eight tree types
One relationship canvas. Eight ways to start.
Family Tree uses the same partner-and-child layout for genealogy, language families, clan lineage, noun classes, etymology, dialect maps, org charts, and knowledge domains. Pick a template when you start — exports include treeType so loaders know how to read your labels. Read the tree types guide →
Family Genealogy
Household genealogy — the default template for people, partners, and generations.
Language Family Tree
Linguistic descent — how a proto-language splits into branches and regional forms.
Clan & Lineage Tree
Clan structure and living descent from a shared ancestor.
Noun Class Tree
Grammatical noun-class systems — classes, subclasses, and exemplar vocabulary.
Word Etymology Tree
Lexical history — how a root form develops across time and usage.
Dialect Map
Regional variation — how a standard or parent lect splits into dialect geography.
Org Chart
Organizational hierarchy — teams, departments, and roles reporting lines.
Knowledge Domain Tree
Taxonomic knowledge maps — subjects broken into topics and subtopics.
Product principles
Built for the canvas
Every control should help you map, edit, or export — not compete with the work.
Momentum first
Creation should feel immediate. The tool should never become the work.
Clarity over clutter
Controls stay close enough to help and quiet enough to let the canvas lead.
See it in motion