NeoArc vs GitBook

Developer documentation and architecture documentation serve different audiences and need different capabilities. GitBook is a polished documentation platform built for developer guides and public-facing docs with strong AI search. NeoArc Studio takes a model-first approach where a central data model drives data views and API schemas, with the Intent Graph (33 node types, 19 edge types) automatically tracking every relationship. This comparison helps you decide when each tool is the right choice.

Feature Comparison

Detailed comparison of documentation capabilities:

Git Integration Comparison

Key Differences

Model-First Architecture

NeoArc is built around a model-first approach. You define a central data model, and that model drives data views and API schemas. Changes to the model propagate automatically. When you rename a field, impact analysis identifies every affected artefact and creates migration cards on the integrated task board (with both Kanban and Gantt views). GitBook treats each page as an independent document with no structural relationships between them.

Intent Graph as Foundation

The Intent Graph (33 node types, 19 edge types) is the foundation of NeoArc. It automatically builds a semantic graph connecting all your architecture artefacts - pages, diagrams, schemas, API endpoints, data models, and more. This is not manual linking. When you reference a diagram in a page, connect a schema field to a data view column, or embed an API endpoint, NeoArc tracks these relationships automatically. The Architecture Explorer lets you browse connections and understand impact before making changes. GitBook has no equivalent traceability.

Six API Types

NeoArc includes dedicated editors for six API types. REST APIs support OpenAPI with endpoint definitions, parameters, request bodies, and responses. GraphQL support includes operations, custom scalars, directives, and interfaces. gRPC covers Protocol Buffer service definitions. AsyncAPI supports 18 messaging protocols including Kafka, AMQP, MQTT, and WebSocket. Webhooks support 7 verification methods with delivery and retry configuration. MCP server documentation covers tool definitions and resource schemas. GitBook displays API documentation but lacks built-in editing tools for any of these.

Scroll-Driven Presentations

NeoArc transforms diagrams into scroll-driven presentations with visibility controls, viewport transitions, and configurable animations. Present directly from the viewer or export for meetings. GitBook has no presentation capabilities.

Visualisation and Publishing

NeoArc includes 6 D3-powered visualisation blocks for data-driven graphics within pages. Professional PDF publishing supports cover pages, controlled typography, password protection, and page numbering. 16 governance reports can be exported to PDF. GitBook focuses on web-based documentation and does not offer these capabilities.

Graph Diagrams

The platform includes force-directed graph diagrams in three modes: mindmap for brainstorming, conceptual for domain modelling, and graph-db for Neo4j-style schemas with node properties and cardinality constraints. Export to 24 schema formats including 12 SQL DDL dialects, GraphQL SDL, TypeScript, Prisma, and more. Import from 15 formats including SQL DDL, draw.io, GraphML, PlantUML, and Mermaid ERD. GitBook requires third-party embeds for diagrams.

When to Choose

Documentation Type Comparison

Complementary Use

Some teams use both tools: