Anjana Data Governance: Review, Pricing & Features
Everything you need to evaluate Anjana Data for data governance: what it is, my review, pricing, features, integrations and the best alternatives.
By Ari Bajo - data engineer turned writer.
Updated on November 19, 2026
- Product
- Anjana Data
- Category
- Enterprise data governance
- Pricing
- From $37,800/year
- Deployment
- SaaS, self-hosted, hybrid, data residency
- Links
- Website
On this page
What is Anjana Data?
Anjana Data is a Spanish data and AI governance platform that sits on top of existing data platforms. Teams use it to run a governance operating model, a catalog and glossary, and a Marketplace where approved data sharing agreements grant access.
Anjana Data review
Anjana Data is the best data governance tool for Spanish and European enterprises and public bodies that want a governance layer independent of any one platform, with automated access provisioning, AI Act templates, and self-hosted or EU-hosted deployment.
Strengths
- Approved data sharing agreements create grants in Snowflake, Power BI, S3 and cloud IAM, and expiry revokes them.
- Self-hosted, SaaS or hybrid, priced by governed assets with no per-user fees.
- AI Act and ISO 42001 templates, plus RoPA and DPIA asset types.
Caveats
- No built-in AI: no chat, generated descriptions or agents.
- Lineage is documented by hand, not parsed from SQL, dbt or OpenLineage.
- No automated PII scanning, profiling or data quality checks.
Fun facts
Anjana Data was founded in Bilbao in 2019.
Telefónica Tech started reselling Anjana in Spain in April 2025.
Anjana 26.1 (June 2026) added a new Marketplace, an MCP server and a Kubernetes install.
Anjana Data pricing
Anjana prices by governed assets, with no per-user fees. On AWS Marketplace, SaaS starts at $37,800 a year.
Checked November 12, 2026 on the pricing page and AWS Marketplace.
Anjana Data features
Anjana Data appears in my lists of the best data catalog and data stewardship tools. It supports 39 of the 70 tracked data governance features.
Anjana Data data catalog
Plugins extract metadata from Oracle, SQL Server, Snowflake, Unity Catalog, BigQuery, Redshift, Glue, Denodo, Power BI and Tableau.
Compare: data catalog tools
Automated Metadata Harvesting: Tot plugins discover and extract tables, columns, views and reports from Oracle, SQL Server, Snowflake, Databricks Unity Catalog, BigQuery, Redshift, AWS Glue, S3, Denodo, Power BI and Tableau; a user picks which structures to import in an extraction wizard (docs).
Search & Discovery: The Catalog search bar runs across all attributes and relationships, with static, dynamic and quick filters by subtype, status, organizational unit and adherence, plus saved searches (docs).
Custom Fields & Templates: Administrators define metadata attributes (text, select, date, entity reference and more) and assign them to templates per entity subtype, with sections, menus and validations (docs).
Asset Certification: Each asset moves through lifecycle statuses (draft, pending validation, approved, deprecated, expired) set by validation workflows, and the status icon is shown on every asset (docs).
Business Glossary: Business terms, metrics and other glossary entities are owned by data domains, approved through validation workflows and linked to catalog assets through configurable relationships (docs).
Metadata Propagation: HERITABLE attributes pass boolean values between related objects, for example a dataset is flagged as holding personal data when any of its fields is, and a DSA inherits values from the datasets it contains (docs).
AI-Powered Search: Search runs on Solr with attribute weights, stopwords and a synonyms file; there is no built-in natural language search, and plain-English queries only work through an external AI client connected to the MCP server (docs).
Usage & Popularity Statistics: The docs show no per-asset query counts, view counts or popularity ranking in the Catalog (docs).
Anjana Data data lineage
Table-Level Lineage: Datasets are linked as inputs and outputs of processes and process instances, which shows which tables feed which downstream datasets (docs).
Column-Level Lineage: Dataset fields can be related to other fields, metrics and reports, which shows which fields are used to build a report; these links are relationships in the metamodel, not parsed from SQL (docs).
End-to-End Lineage: Relationships chain source datasets through processes and solutions to reports and business terms, so the graph can run from source system to report, though it is built from documented relationships rather than query parsing (docs).
Impact Analysis: Versioning rules and lineage are used to review the impact of a change before it is approved, and deprecating an asset notifies the users who rely on it (docs).
Automated Lineage Extraction: Lineage is drawn from relationships between entities, processes and reports in the metamodel; the plugins discover tables, fields, views and reports, but none parse SQL, query logs or ETL jobs to build lineage (docs).
OpenLineage Support: No OpenLineage integration appears in the plugin catalog or the docs (docs).
Anjana Data data stewardship
A configurable metamodel, domains, roles and BPMN workflows run every create, change, deprecate and access step, with versions and expiry dates on each asset.
Compare: data stewardship tools
Review & Approval Workflows: Validation workflows written in BPMN XML route creation, modification, deprecation, organizational unit changes and access requests to the right approvers, with comments and request reasons (docs).
Governance Campaigns: The Workspace and bulk attribute editing apply changes, assign owners or launch processes on many assets at once, and Excel editing updates a whole subtype in one upload (docs).
Metadata Automation: Workflow listeners fire on governance events, an inventory interceptor transforms attribute values on save, and scheduled batches handle expirations and notifications (docs).
Critical Data Elements: There is no dedicated critical data element register; a team would have to model it as a custom attribute or entity type (docs).
Governance Scorecards: No questionnaire-driven maturity scoring of assets or domains is documented (docs).
Anjana Data data classification
Data Policy: Access to governed data goes through Data Sharing Agreements: a consumer adheres to a DSA, the request is approved by workflow, and role and domain permissions control what each user can see and do (docs).
Native Policy Enforcement: When a DSA is approved, plugins create roles or groups and grant or revoke access in Snowflake, Denodo, Power BI, S3, Azure Storage, Ranger and cloud IAM, then revoke it when the DSA expires (docs).
Sensitive Data Discovery: No automated PII scanning or pattern-based classifier is documented; personal-data flags on dataset fields are filled in manually or imported from source tags (docs).
Data Masking: Plugins only obfuscate columns flagged as personal data in the limited data samples shown in the portal; there is no dynamic or static masking of query results (docs).
Anjana Data data compliance
Audit Trail: The traceability log records who created, modified, approved or requested access to each asset, with workflow comments and a downloadable snapshot of the asset after each action (docs).
Regulatory Framework Mapping: A preconfigured AI management system maps AI systems, risks, controls and evidence to the EU AI Act and ISO 42001 Annex A, and links GDPR processing activities to DPIAs and breaches (website).
ROPA: Records of Processing Activities are a regulatory compliance asset type in the Catalog, linked to DPIAs and data assets (docs).
Compliance Reporting: The website describes governance dashboards and reports through external BI tools and the AI governance setup stores conformity evidence, but no regulator-ready report or evidence pack is documented (website).
Data Activity Monitoring: The audit module can store access events that governed systems push through the API, but Anjana does not collect or analyze source query activity itself (docs).
Data Retention Policies: Assets and DSAs have expiration dates that revoke access, but no rule archives or deletes the underlying data (docs).
Data Subject Rights: No DSAR, deletion or portability request handling is documented (docs).
Anjana Data collaboration
Alert Notifications: The Hermes service sends governance notifications (workflows, expirations, deprecations, adherence failures) to Slack, Microsoft Teams, Google Chat and email (docs).
Ticketing Integrations: The integrations page shows Jira, Confluence and ServiceNow logos, but the docs describe no plugin that creates tickets from governance events (website).
Discussions & Annotations: Comments exist only inside validation workflow steps; there are no threaded discussions on assets (docs).
Anjana Data data marketplace
An approved Data Sharing Agreement creates real grants in Snowflake, Denodo, Power BI, S3, Azure Storage, Ranger and cloud IAM, and revokes them when it expires.
Self-Service Access Requests: Consumers add assets to a cart and request access; the adherence request routes to the DSA owner by workflow and, once approved, a plugin grants access in the source platform (docs).
Data Products: Data Sharing Agreements package datasets, reports, KPIs and quality rules under one owner, with a contract, expiration date and versions, and are published in the Marketplace (docs).
Data Mesh Support: Data domains (organizational units) own their assets and workflows under a centralized, federated or hybrid governance model, and the vendor positions the Marketplace for data mesh setups (docs).
Subscription Management: Users who adhere to a dataset or DSA are tracked as consumers and are notified when it is going to be deprecated or expire (docs).
Anjana Data data quality
Data Contracts: DSA contracts are producer-consumer agreements with license terms, usage, quality and availability conditions; consumers must sign the contract before access is granted (docs).
SQL Table Tests: Quality rules are defined in Anjana but executed by external engines such as the Aqtiva (Omma Data) plugin, which is now deprecated (docs).
Data Health Scores: No composite quality or health score per asset or domain is documented (docs).
Anomaly Detection: No statistical or ML anomaly detection on data values or volumes is documented (docs).
Data Profiling: Plugins return a limited data sample for preview but compute no column statistics such as null rates or distributions (docs).
Anjana Data AI governance
Templates model AI systems, use cases, risk and impact assessments against the EU AI Act and ISO 42001, and link models to their training datasets.
AI Asset Inventory: The metamodel includes AI models and AI systems as entity types with their own templates, owners, required attributes and workflows (docs).
AI Lineage: The AI governance setup links each model to its training, validation and production datasets through relationships shown in the lineage graph (website).
AI Regulatory Compliance: Preloaded vocabularies follow the AI Act Article 6 risk classes, with entity types for risk assessments, impact assessments, GPAI training content summaries and conformity files (website).
AI Model Health Score: No composite trust or readiness score for AI models is documented (website).
AI Agent Access Governance: The MCP server applies the user's own permissions and keeps agent changes in draft, but it serves only metadata and adds no policy check at the point an agent reads data (docs).
Anjana Data workflows
REST / GraphQL API: Public, administrative and configuration REST APIs, documented in Swagger, read and write assets, relationships, workflows, notifications and audit entries (docs).
dbt Integration: There is no dbt plugin in the plugin catalog (docs).
Python SDK: The SDK is a Java 17 / Spring Boot kit for building plugins; there is no pip-installable library (docs).
Webhooks: Outbound webhooks only deliver notifications to Slack, Microsoft Teams and Google Chat; there is no generic webhook to arbitrary endpoints (docs).
Anjana Data data context layer
MCP Server: The MCP server, first released in version 26.1 (June 2026), lets AI clients search assets, read lineage, catalog and enrich metadata, request DSA access and query the audit log with the user's own permissions (docs).
Knowledge Graph: Metadata is modeled as a graph of entities, users and organizational units linked by typed relationships, which the Lineage module explores from any node (docs).
Unstructured Data Catalog: The Databricks plugin harvests Unity Catalog volumes as a separate "unstructured data asset" type (DBK_VOLUME) that can be governed like other assets, but only at volume level; the file plugins handle structured formats (CSV, Excel, Avro, Parquet), and documents, SharePoint and vector indexes are not covered (docs).
Semantic Models: The glossary links business terms to assets, but Anjana does not generate a machine-readable semantic model with join paths (docs).
Verified Queries: There is no built-in assistant; the MCP server exposes search, lineage, cataloging and access-request operations to an external AI client, with no store of approved example queries (docs).
Semantic Layer Interop: The Power BI plugin maps semantic models only to manage access permissions; no plugin reads or writes metric definitions from dbt, Snowflake, Databricks, Cube, LookML or OSI (docs).
Not covered: AI features · Master data management
Anjana Data integrations
Anjana Data connects to Snowflake, Databricks, BigQuery, Redshift, Power BI and Tableau, and to Apache Ranger to push access policies. Anjana Data lists 37 integrations in total.
- Data Warehouse: Amazon Redshift, Databricks SQL, Google BigQuery, IBM DB2, Oracle DB, Snowflake, Teradata
- Databases: MariaDB, Microsoft SQL Server, MySQL, PostgreSQL
- Data Storage: Amazon S3, Azure Blob Storage, Google Cloud Storage
- Query Engine: Hive SQL
- Data Platform: Denodo
- BI: Power BI, Tableau
- Data Governance: AWS Glue Data Catalog
- AI Agents: Claude, Claude Code, Cursor, GitHub Copilot
- Notifications: Google Chat, Microsoft Teams, Slack
- Authentication: AWS Identities, Amazon Cognito, Auth0, Google Workspace, Keycloak, LDAP, Microsoft ADFS, Microsoft Entra, Okta, Ping
- Data Security: Apache Ranger
Anjana Data deployment options
Anjana runs self-hosted on VMs or Kubernetes, as SaaS on AWS, Azure or GCP in EU or US regions, or hybrid.
SaaS Deployment: The SaaS option is fully run by Anjana Data on AWS, Azure or GCP, with tiered capacity packages and a dedicated Customer Success Manager (docs).
Self-Hosted Deployment: The IaaS/PaaS license installs on customer VMs (Ansible) or Kubernetes (Helm) on premises or in the customer's cloud, with an installer for setup and upgrades (docs).
Hybrid Deployment: In SaaS Hybrid mode Anjana hosts the core and the customer runs only a plugins machine next to its data systems (docs).
Data Residency: SaaS runs by default in Frankfurt, Spain, Ireland, N. Virginia or N. California, and other regions are available as a paid add-on (docs).
Anjana Data security
Anjana supports SAML and OIDC SSO, permissions by domain and an audit module, with Spain's ENS certificate. It has no SOC 2 or ISO 27001 of its own.
SSO: Login supports SAML 2.0 and OpenID Connect, with guides for Entra ID, Okta, Auth0, AWS, GCP, Keycloak and LDAP/Active Directory (docs).
RBAC: Roles hold permissions per entity type and action (create, modify, change status, deprecate, change organizational unit) and can be scoped by data domain (docs).
Audit Log: The Audit module logs every user action in the platform, including changes made by AI clients through the MCP, and is restricted to roles with audit permission (docs).
Compliance Certifications: Anjana Data S.L. holds an ENS (Esquema Nacional de Seguridad) medium-level certificate for 2026; for ISO 27001 and SOC 2 its trust center points to AWS, Google and Atlassian, not its own audits (website).
SCIM Provisioning: Users are synced on a schedule by reading directory APIs (Microsoft Graph, Google Directory, Okta, LDAP/AD, Keycloak, AWS), not through a SCIM 2.0 endpoint (docs).
Anjana Data alternatives
The closest Anjana Data alternatives and most popular competitors are DataGalaxy, Collibra, Alation, OvalEdge and OpenMetadata. They share Anjana Data's main use cases and features, from the closest match down. The Anjana Data alternatives page compares their pricing, deployment and features, and says when to choose each one instead.
Choose Anjana for a governance operating model with access provisioning and AI Act templates, especially in Spain. For automated lineage and AI features, consider Collibra or Atlan.
- 1. DataGalaxyAnjana Data vs DataGalaxy
- 2. CollibraAnjana Data vs Collibra
- 3. AlationAnjana Data vs Alation
- 4. OvalEdgeAnjana Data vs OvalEdge
- 5. OpenMetadataAnjana Data vs OpenMetadata
Anjana Data FAQ
Is Anjana Data open source?
No. Anjana Data is proprietary software with no open-source edition.
How much does Anjana Data cost?
Anjana prices by governed assets, with no per-user fees. On AWS Marketplace, SaaS starts at $37,800 a year.
Which data platforms does Anjana Data integrate with?
Anjana Data connects to Snowflake, Databricks, BigQuery, Redshift, Power BI and Tableau, and to Apache Ranger to push access policies.
Can Anjana Data be deployed on-premise?
Yes. Anjana runs self-hosted on VMs or Kubernetes, as SaaS on AWS, Azure or GCP in EU or US regions, or hybrid.
What are the best Anjana Data alternatives and competitors?
The closest alternatives are DataGalaxy, Collibra, Alation, OvalEdge and OpenMetadata. The Anjana Data alternatives page compares their features and pricing and says when to choose each one over Anjana Data.
Browse all 102 tool profiles, grouped by category.
Evaluating data tools in 2026?
I curate the most comprehensive lists of data tools, up-to-date comparison tables, and actionable market guides for data teams. More useful than a Gartner report. More reliable than asking AI. Next up: Data FinOps.