Welcome to Farkitect

Sometimes diagrams just aren’t enough. Farkitect lets you build structured, visual models backed by real data — define the types of things you care about, how they connect, and what properties they carry. Pick a modelling framework you like, extend it, or start from scratch.

Business analysis, enterprise archtiecture, industry-specific issues, software design, data models, organisational mapping, or something entirely your own — Farkitect works for any domain where you need to think clearly about the things in a system and how they relate to each other. It’s wild, it’s crazy, it’s kinda nerdy. Welcome to Farkitecture.

Why “Farkitect”?

You know that moment when you’re staring at a modeling tool and it won’t let you do the thing you obviously need to do? When the boxes are wrong, the arrows don’t mean what you want them to mean, and the metamodel is locked down tighter than a submarine? That moment when you mutter something under your breath that starts with “far…” and ends with a word your mother wouldn’t approve of?

Yeah. We’ve been there too. So we built the tool we wished existed — one where you define the rules, not the vendor — and gave it a name that captures exactly how we felt about every tool that came before it. Farkitect: modeling for people who’ve had enough.

What Makes Farkitect Different

Most modeling tools lock you into a fixed set of shapes and connectors. Farkitect takes a different approach: you define the modeling language itself.

• Use standard metamodels — ArchiMate 3.2, UML, C4, Logical Data Modeling, Business Model Canvas, and others are available out of the box via the Farketplace
• Create your own metamodels — define the element types, relationship types, properties, and constraints that match your domain
• Combine languages freely — a single project can use types from multiple metamodels
• Everything is structured — models aren’t just pictures, they’re structured data you can query, filter, catalog, and export

This is powered by a standard called the Meta Object Facility (MOF), which organizes everything into layers. You don’t need to understand MOF to use Farkitect, but if you’re curious, the explanation pages go into detail.

What You Can Do

With Farkitect, you can:

• Draw diagrams with notation-aware shapes, colors, and icons that come from your metamodel
• Build catalogs — tabular views of your model elements with sortable, filterable columns driven by metamodel properties
• Define properties on your element types (dates, numbers, enumerations, text) and fill them in across your model
• Enforce constraints — metamodels can restrict which relationship types are valid between which element types
• Collaborate — invite team members to your organisation and work together on projects with role-based access
• Import and export — share models as portable .farki files, or export to XMI and Eclipse EMF formats
• Work with AI — the human-readable .farki format means large language models can read, generate, and update your models

The Farquind Yachts Case Study

Throughout this documentation, you’ll encounter Farquind Yachts — a fictional yacht manufacturer that we use as a running example. Farquind is a vertically integrated startup building affordable sailing yachts in Hatteras, North Carolina. The company has a rich cast of characters, a complete organizational structure, and a suite of custom-built software systems.

We use Farquind Yachts because realistic examples make better documentation. When a tutorial says “create an Application element called FQ Vessels,” you’ll know that FQ Vessels is Farquind’s fleet telemetry platform — not just an arbitrary name. The Farketplace starter assets are also built around Farquind, so the same company, people, and systems appear everywhere.

You can read the full case study in Farquind Yachts — The Case Study.

How the Documentation is Organized

This documentation follows the Diataxis framework, which means content is organized by what you need rather than where features live:

Tutorials

Step-by-step lessons that build your skills. Start here if you’re new. Each tutorial takes you through a series of steps and produces a visible result — you learn by doing.

How-to Guides

Focused directions for accomplishing specific tasks. Come here when you know what you want to do and need to know how. Each guide has a clear goal and gets straight to the point.

Explanation

Background reading that deepens your understanding. Come here when you want to know why things work the way they do, or when you want context for the concepts you’re using.

Reference

Technical specifications you consult while working. Keyboard shortcuts, file format details, metamodel specifications, and the glossary.

Next Steps

If you’re new to Farkitect, start here:

1. Quick Start — Open the app, take a first look around, and create your first project (5 minutes)
2. Your First Diagram — Build a real diagram using a built-in metamodel (15 minutes)
3. Farquind Yachts — Read the case study to understand the examples you’ll encounter throughout the tutorials