ARCXA - MID

 

ARCXA and the design system. Let me build a polished developer-focused landing page that frames the three value props around the NNX/triple-store architecture. 

mid - ARCXA's NNX architecture to each of your three audiences:

For migrators (consultants/SIs), the pitch is MAAP: Migration as a Product. Instead of delivering a one-time migration, they deliver a compounding governance asset. ARCXA makes the Day 2 audit deliverable nearly automatic, which is both a risk reducer and an upsell — recurring catalog maintenance powered by the same triple store.

Every Migration engagement has governance baked in as a product — not a post-project cleanup sprint. ARCXA turns compliance artifacts into a deliverable, not an afterthought. This is Migration as a Product.

1. MAAP: Migration as a Product — recurring governance revenue, not one-time project
2. Reduce Day 2 audit rework by eliminating manual lineage documentation
3. Dark data detection before scope lock — protect your fixed-bid margin
4. Client-facing lineage explorer — differentiated delivery artifact
5. Knowledge graph persists post-project — upsell ongoing maintenance

For integrators, NNX is a composable middleware layer. Position it as a lineage sidecar that works alongside whatever orchestration they already use — Airflow, dbt, Fivetran. The open exchange format means they're not locked into a vendor graph, and they can sell clients on owning their own migration intelligence.

ARCXA acts as a composable middleware layer that sits alongside your client's existing stack. The NNX exchange format means mapping intelligence flows across vendor boundaries. You own the graph — and so does your client.

ARCXA For Developers: the triple-store angle is the unlock. Every migration event becomes a queryable graph node — subject (source schema), predicate (relationship/transform type), object (target schema). This means lineage isn't a report you write afterward — it's a queryable artifact your pipeline produces automatically. Lead with the REST/SPARQL API and the "knowledge compounds" angle: the more migrations ARCXA processes, the smarter your next one starts.

ARCXA

Architecture Value Props By Role GitHub ↗

Neural Network Exchange · Triple-Store Architecture

Migration
intelligence
that compounds.

// Schema mapping, lineage, and transformation traceability.
Every data move becomes a queryable graph triple.
Every project makes your next one smarter.

View on GitHub Architecture ↓

30%

// avg dark data found pre-migration

Day 1

// searchable + compliant on arrival

NNX

// triple-store exchange format

∞

// intelligence compounds per project

NNX Architecture

The Neural Network Exchange
triple-store model.

Every migration event — schema move, field transformation, lineage hop — is captured as a Subject → Predicate → Object triple. The result is a living, queryable knowledge graph that survives the migration and compounds across every future project.

Subject

Source Entity

Table, field, schema, or data asset in the legacy system.

schema:orders_legacy
field:customer_id
type:varchar(36)

Predicate

arcxa:maps_to

arcxa:transforms_via

arcxa:lineage_of

arcxa:deprecated_by

Object

Target Entity

Table, field, schema, or data asset in the destination system.

snowflake:ORDERS
field:CUSTOMER_UUID
type:varchar(36)

arcxa_query.sparql — find all lineage from a source table

# ARCXA NNX Triple Store · SPARQL endpoint

PREFIX arcxa: <https://schema.arcxa.io/v1/>
PREFIX schema: <https://migrations.arcxa.io/entities/>

SELECT ?source ?predicate ?target ?transform ?version WHERE {
  ?source    arcxa:maps_to     ?target     ;
             arcxa:version     "v2.1"      ;
             arcxa:project     "snowflake-lift-q1-2025" .
  OPTIONAL { ?source arcxa:transforms_via ?transform }
  FILTER (?source = schema:orders_legacy)
}
ORDER BY ?version

# → returns every downstream dependency that has ever touched orders_legacy
# → computable across ALL past projects — intelligence compounds automatically

Three Value Propositions

Why teams attach ARCXA
to every migration.

Whether you're an integrator selling platform migrations, a developer building pipelines, or a data engineer managing governance — ARCXA resolves three distinct failure modes.

01 // MAAP · Migration as a Product

Governance
Insurance

Most migrations fail not because the data didn't move — but because the company lost track of what moved. ARCXA records every schema move as an auditable triple. Your Day 2 audit isn't a panic sprint — it's a query.

→ audit-ready on day one

02 // ROI Multiplier

Protect Your
Platform Spend

You're investing $500k in Snowflake. A 10% ARCXA attach ensures that investment is searchable and lineage-tracked on arrival — not six months from now after a painful data catalog project.

→ catalog-at-no-extra-sprint

03 // Storage Saver

Don't Pay to
Migrate Dark Data

ARCXA crawls your legacy tiers before migration begins. The NNX graph reveals which assets have zero downstream references. On average, 30% of data is redundant — cut before it hits cloud billing.

→ avg 30% storage saved

By Role

Your pitch, by audience.

ARCXA speaks differently to developers, system integrators, and migration consultants. Select your audience below.

The proposition

Plug ARCXA into your migration pipeline and every schema transformation is stored as a graph triple. Query lineage via SPARQL or the REST API. No hand-rolled mapping spreadsheets. Your next migration inherits the intelligence from this one — automatically.

The pitch

• Drop-in lineage layer for Airflow, dbt, Fivetran, or custom ETL pipelines
• SPARQL + REST API — query what moved, what transformed, what was deprecated
• Open NNX exchange format — vendor-portable, schema-typed graph
• Crawl legacy tiers before migration — prune redundant assets from billing scope
• Every project adds to the graph — intelligence compounds, never resets

The proposition

ARCXA is a composable middleware layer that sits alongside your client's existing stack. The NNX exchange format means mapping intelligence flows across vendor boundaries. You own the graph — and so does your client.

The pitch

• Attach at 10% of migration project cost — instant governance upsell
• Supports Snowflake, Databricks, Redshift, BigQuery, Oracle and more
• Sidecar architecture — no rip-and-replace, works with existing tooling
• Deliver audit-ready lineage artifacts at project close automatically
• Recurring value: ongoing catalog maintenance powered by the NNX graph

The proposition

Sell every migration engagement with governance baked in as a product — not a post-project cleanup sprint. ARCXA turns compliance artifacts into a deliverable, not an afterthought. This is Migration as a Product.

The pitch

• MAAP: Migration as a Product — recurring governance revenue, not one-time project
• Reduce Day 2 audit rework by eliminating manual lineage documentation
• Dark data detection before scope lock — protect your fixed-bid margin
• Client-facing lineage explorer — differentiated delivery artifact
• Knowledge graph persists post-project — upsell ongoing maintenance

// Works alongside

Snowflake

Databricks

dbt

Apache Airflow

Fivetran

Apache Kafka

Redshift

BigQuery

Oracle

SQL Server

PostgreSQL

Collibra

Alation

OpenLineage

Apache Atlas

// Open Source

Start mapping
on GitHub.

ARCXA is open source. Explore the NNX schema, contribute to the triple-store engine, or build your own lineage explorer on top of the graph API.

github.com/equitusai/arcxa ↗

// Equitus AI

Built by
Equitus AI.

ARCXA is the mapping intelligence layer inside the Equitus AI platform. Enterprise migrations, compliance, and data lineage — compounding across every engagement.

Explore Equitus AI ↗

ARCXA  ·  github.com/equitusai/arcxa  ·  MIT License

GitHub Equitus AI Issues

The interactive widget above lets you toggle between all three perspectives, shows the NNX triple-store structure visually, and links directly to the GitHub repo. The three value prop cards are clickable and routed to ask-Claude follow-ups if you want to explore any angle deeper.