Source Control Native

NeoArc Studio takes a different approach. Everything you create is a text-based JSON file stored in your Git repository. Your diagrams, design documents, API specifications, schemas, and decision records sit alongside your code in the same folder structure you already use.

Why This Matters

File Formats

All NeoArc content uses human-readable JSON files with clear extensions:

No Vendor Lock-in

CI/CD Integration

Because your documentation is just files in Git, you can integrate it into your existing CI/CD pipelines:

Works with Your Existing Infrastructure

NeoArc Studio works with any Git provider: GitHub, GitLab, Azure DevOps, Bitbucket, or self-hosted Git servers. Your documentation benefits from whatever security, access controls, and compliance features you already have in place for your code repositories.

The Documentation Workflow That Actually Works

Baseline-Driven API Comparison

Baselines do more than track general drift. When you compare against a baseline, the system classifies every API contract change as breaking, additive, deprecation, or cosmetic across all six API types (REST, GraphQL, gRPC, AsyncAPI, Webhooks, MCP). The drift dashboard shows API contract drift alongside architectural drift, and the system recommends version bumps based on change severity.