Logo
NeoArc Studio

How NeoArc Works

Walk a single entity from its definition in the model through to a published diagram, a database schema, a compliance check and an auditor-ready report, all derived from the same source.

One entity, followed all the way through

This page is not a feature tour. It is a worked example. We take a single entity, Customer, give it a single property, emailAddress, and walk what happens to that property as it moves through the model into projections, governance and published output. Then we change it and watch everything downstream react.

If you want the product summary, read NeoArc Studio first. If you want the security and deployment detail, read Security and Deployment. This page sits between them and shows the machine working.

Model
The authoritative definition of your domain. Entities, properties, vendor-neutral types, relationships and shared property sets live here. Nothing is duplicated; everything downstream references this layer.
Projections
Database schemas, API contracts, search indexes and UI views derived from the model through typed transformations. Profiles handle the vendor-specific resolution so the model stays neutral.
Governance
Risks, controls, non-functional requirements and compliance notes attach to architectural nodes as typed edges. Coverage and drift are computed from the graph rather than assembled before an audit.
Publishing
Websites, PDFs, presentations and in-app help are generated from the same model. Every audience gets a view in the format they want, and none of those views can disagree with the others.

Where to go from here

If you want to understand what the product is for, read NeoArc Studio. If you want the deployment and security posture, read Security and Deployment. If you want to see how the governance layer holds up under scrutiny, read Governance and Compliance.