Xtrable
Most architecture work is not greenfield. It is making sense of systems that already exist. NeoArc meets you there: point it at the artefacts you already have and it builds a model you can explore, govern and project forward.
Seven formats, one path
NeoArc reads the definitions your systems are already written in, and maps each into the same clean model:
- OpenAPI and Swagger, validated against specs as large as the full Stripe API.
- SQL table definitions from a database dump.
- Prisma schemas.
- DBML from dbdiagram.io.
- JSON Schema bundles.
- GraphQL schema definitions.
- Protobuf message definitions.
Whatever the source, the result is the same: entities, properties, keys and relationships you can reason about, not a wall of raw text.
From an existing service to a model in minutes
Bring in a third-party API or an internal database and within minutes you have a navigable model: search it, walk its relationships, see what is orphaned or inconsistent, and start projecting it onto the stores and contracts you need. The months usually spent reconstructing a system's shape by hand collapse into an import.
Re-import without losing your work
Sources change. When you re-import, NeoArc does not throw your model away and start over. It matches the new definition to what you already have, keeps the identity of every entity and field so your lineage survives, and shows you a clear preview of what was added, changed, renamed or retired before you accept it. A field dropped from the source is deprecated, not silently deleted, so nothing downstream breaks by surprise.
Honest about the edges
Anything that does not map cleanly is reported as a clear diagnostic rather than hidden. You always know exactly what came across and what needs a second look.