5 1 Reviews 1 Saved
Introduction: MORI is a genealogy platform designed to foster family connection through collaborative family tree creation and exploration. It features real-time multiplayer collaboration, version history, and an AI-enhanced media gallery to modernize the genealogy experience. Users can work simultaneously with relatives, share trees, and leverage AI tools for photo enhancement and audio transcription.

MORI Product Information

What is MORI?

MORI is a genealogy software designed to bring families closer together by enabling collaborative family tree creation and exploration. It offers features like multiplayer collaboration, version history, and an AI-enhanced media gallery to modernize the genealogy experience. MORI allows users to work simultaneously with family members, share their tree easily, and utilize AI tools for picture enhancement and audio transcription.

How to use MORI?

Start by importing your existing GEDCOM file or creating a new family tree. Add individuals, events, and sources. Share your tree with family members via email to collaborate in real-time. Use AI features to enhance historical photos and transcribe audio files. Explore your tree using the built-in search and navigation tools.

MORI's Core Features

  • Multiplayer collaboration
  • Version history
  • AI-enhanced media gallery
  • Advanced search capabilities
  • Flexible tagging
  • Automatic event timelines
  • Robust source citations
  • GEDCOM Import

MORI Use Cases

#1 Collaboratively build and explore a family tree with relatives.
#2 Enhance and preserve historical family photos using AI.
#3 Transcribe audio recordings to preserve family stories.
#4 Easily share your family history with friends and family.

FAQ from MORI

What makes MORI unique? +

MORI enables collaborative genealogy, allowing you and your family to work together on the same tree. Multiple users can explore and expand the tree simultaneously, facilitating new discoveries and engaging younger generations.

Can I import my existing trees? +

Yes. You can export your existing trees as a GEDCOM file from your current provider and import that file into MORI. The system will then automatically reconstruct your tree.

How does the collaborative interface work? +

MORI provides a streamlined family tree builder for adding individuals, events, and sources. You can share your tree with others by entering their email addresses. Once they join, you can see their cursor movements on the canvas in real-time.

Who owns all of the data I submit? +

You retain full ownership of your data. MORI is designed to assist your genealogical research, and the information you store remains yours.

Do I need to always work with others, or can I still work solo? +

While MORI is optimized for collaboration, it functions perfectly for solo users. You can utilize all features, including AI tools, tagging, and search, independently.

How much does MORI cost? +

MORI is currently free during its beta phase. We aim to build a sustainable service and are considering future options such as paid subscriptions for advanced AI features or DNA testing integrations.

MORI Pricing

Free

$0

Free plan available.

Related Model Comparison Pages

Use these comparison pages to understand the trade-offs between the models most relevant to MORI.

Compare Gemini 1.0 Pro Deprecated and Gemini 2.0 Flash across pricing, context window, capabilities, benchmarks, and API access to choose the better fit for long-context workloads versus long-context workloads.

Compare Gemini 1.0 Pro Deprecated and Gemini 2.5 Flash across pricing, context window, capabilities, benchmarks, and API access to choose the better fit for long-context workloads versus long-context workloads.

Compare Gemini 2.0 Flash Lite and Gemini 2.0 Flash across pricing, context window, capabilities, benchmarks, and API access to choose the better fit for long-context workloads versus long-context workloads.

Compare Gemini 2.5 Flash and Gemini 2.0 Flash across pricing, context window, capabilities, benchmarks, and API access to choose the better fit for long-context workloads versus long-context workloads.