ARCXA.ai

EDB/EQUITUS

Arcxa (Equitus.ai) with EDB (EnterpriseDB) allows organizations to create a high-performance, open-source-based ecosystem that handles both the legacy demands of Oracle and the modern requirements of cloud platforms like Snowflake.

By combining Arcxa's semantic "understanding" engine with EDB’s expertise in PostgreSQL (the world's most popular open-source database), you can transform a risky migration into a structured, automated, and secure Migration as a Product (MaaP).

How Arcxa & EDB Partner to "Power" Equitus Solutions

The partnership focuses on three primary pillars of data power:

1. The Oracle-to-PostgreSQL "Bridge"

The Problem: Many Oracle users want to leave high-cost licenses but find the PL/SQL logic too complex to move manually.
The Solution: EDB provides the most compatible PostgreSQL engine for Oracle users. Arcxa then uses its Triple Store (KGNN) to ingest Oracle metadata and semantically map it to EDB. This automation identifies which parts of the Oracle code can be directly migrated and which need "ETL Assist" augmentation.

2. Triple Store Intelligence on EDB

Semantic Layer: Instead of a simple table-to-table copy, Arcxa can use EDB PostgreSQL as a highly efficient storage layer for its derived ontologies.
KGNN Structure: Arcxa organizes data into a Subject >>> Predicate >>> Object format. By running this on EDB, you gain a "Digital Twin" of your data landscape that is open-source, vendor-neutral, and ready for advanced AI/RAG (Retrieval-Augmented Generation).

3. Zero-Trust Governance for Snowflake

Proven Lineage: For users moving data into Snowflake, the combination ensures that every record has a verifiable "birth certificate."
Security: Arcxa generates the governance, lineage, and provenance logs. EDB acts as the secure, on-premise or private-cloud anchor that holds this metadata, providing a Zero-Trust path before the data ever touches the public cloud.

Comparison: Manual Migration vs. Arcxa + EDB Power

Strategic Benefit for Enterprise Users

Oracle Users: Use EDB and Arcxa to break free from vendor lock-in by converting proprietary logic into open-source semantic facts.
Snowflake Users: Control the "cost of the unknown" by using Arcxa to profile and clean data on EDB before it gets ingested into the cloud, where storage and compute costs are higher.
Developers: Access the tool via Docker and GitHub for a version-controlled, "Migration as a Product" workflow that integrates directly into modern CI/CD pipelines.

proof-of-concept (PoC) between EDB and Arcxa, you will be operating within the Equitus.ai ecosystem. Because Arcxa is an "open-core" tool designed for enterprise security, its public availability is often distributed via specific container registries or requested through their developer portal.

1. Finding the GitHub Repository

The core Arcxa engine is maintained by Equitus.ai. While some components of their Knowledge Graph and migration logic are open-source, the primary repository for the enterprise-grade "Migration as a Product" (MaaP) tool is:

Organization: github.com/equitus-ai (Check for the arcxa or migration-assist repositories).
Documentation: If the repository is currently set to private for a specific release, the Equitus Developer Portal provides the invitation links for PoC participants.

2. Docker Images for PoC

Arcxa is built to be cloud-agnostic and runs in Docker to ensure that "Zero-Trust" lineage is maintained across environments. For an EDB (PostgreSQL) to Snowflake PoC, you typically pull two images:

Arcxa Engine: docker pull equitus/arcxa-engine:latest
EDB Connectivity Layer: docker pull equitus/adapter-edb-postgres:latest (Note: Always verify the latest tag on Docker Hub or the Equitus private registry provided during your onboarding).

3. Setting Up the Proof-of-Concept (Step-by-Step)

To integrate EDB and Arcxa, follow this architectural flow:

Step A: Provision the EDB Source Run your EDB Postgres instance. Arcxa will treat this as the "Subject" of its Triple Store mapping.

docker run --name edb-source -e POSTGRES_PASSWORD=password -d edb/edb-postgres:latest

Step B: Deploy Arcxa for "Semantic Understanding" Point Arcxa at the EDB instance. Instead of just moving data, Arcxa will scan the EDB catalog to derive the Ontology (the relationships between your tables).

Configure the arcxa.yaml file with your EDB credentials.

Launch the Arcxa container:

Bash

docker run --network=host -v $(pwd)/config:/app/config equitus/arcxa-engine

Step C: Generate the "ETL Assist" Arcxa will generate a "Migration Product." This is a set of automated scripts and manual "augmentation" prompts that:

Map EDB types to Snowflake types.
Identify complex PL/SQL logic that needs human review.
Produce the Lineage & Provenance logs required for Zero-Trust governance.

4. Why this PoC is valuable for Oracle/Snowflake users:

Risk Control: By using Arcxa to "understand" your EDB/Oracle data before it hits Snowflake, you avoid the cost of importing "junk" or "dark" data.
Automation: It automates 80% of the DDL and DML conversion, leaving only the complex 20% for your engineers (the "Augmentation" phase).
Governance: You get a full audit trail (Provenance) of how data moved from EDB to the cloud, satisfying security requirements.