Graphora LogoGraphora

Why We Open-Sourced Graphora

• Ezhil Vendhan

Note (February 2026): Graphora is now under the MIT License. You are free to use, modify, and embed Graphora in any project — open or closed-source — without restriction.

TL;DR Graphora’s text-to-graph engine and reference UI are available on GitHub. You can self-host the platform, extend it for your ontology, and use it in any project. Our consulting team partners with enterprises that need domain ontologies, integration help, or managed delivery. Repos: graphora-api · graphora-fe

Why Open Source?

  1. Keep the core transparent – Improvements to the Graphora codebase are visible to everyone, building trust in the platform.
  2. Align with how customers buy – Many teams want to evaluate Graphora on their own infra before engaging us. An open license removes procurement friction.
  3. Match our operating model – Consulting stays focused on outcomes (ontology design, integrations, SLAs) while the base platform remains transparent.
  4. Maximum adoption – MIT lets any team embed Graphora freely, which grows the ecosystem faster.

What’s Included Today

  • Graph ingestion + enrichment pipeline covering document parsing, entity extraction, disambiguation, and Neo4j writes.
  • Domain starter kits (finance, healthcare, public sector, consumer goods) to accelerate ontology design.
  • Deployment scripts for Docker Compose plus IaC examples for AWS/GCP/Azure.
  • Reference frontend (graphora-fe) with dashboards, lineage explorer, and demo scenarios you can extend.

Self-Hosting Checklist

  1. Clone the repo and copy the .env.example.
  2. Point the pipeline at your blob storage / queue / vector store.
  3. Load an ontology starter kit, or plug in your own JSON schema.
  4. Tailor the conflict-resolution hooks for your business rules.
  5. Add SSO/observability using the hooks we expose (we kept them simple on purpose).
  6. Contribute back fixes or extensions via PR — it keeps the ecosystem healthy.

When to Bring Our Consulting Team In

  • You need domain-specific ontologies, lineage, and governance that match compliance requirements.
  • You want Graphora embedded in an existing stack (SAP, ServiceNow, custom portals, mainframe exports, etc.).
  • You’re shipping to regulated environments (HIPAA, GDPR, PDPA) and need design reviews, DLP, or on-prem delivery.
  • You prefer a shared-delivery pod—we co-own roadmaps, SLAs, security, and runbooks.

Licensing & Compliance Notes

  • MIT License covers the Graphora codebase. Your data, ontologies, and downstream apps remain proprietary.
  • You may use, modify, and embed Graphora in commercial and closed-source products without restriction.
  • No CLA required for contributions — just open a PR.

What’s Next

  • Additional starter kits for procurement/tenders and manufacturing process intelligence.
  • Terraform blueprints for AWS PrivateLink + private Neo4j Aura deployments.
  • A hardened Helm chart with opinionated observability (Grafana/Loki) baked in.
  • More learning resources: deployment recipes, architecture walkthroughs, and postmortems from real projects.

If you build something interesting with Graphora—or need a partner to deliver production outcomes—let’s talk. Book a consultation or open an issue if you hit a snag.