Pricing

pricing_icon_free_2x pricing_icon_yacht_2x pricing_icon_glossary_ferry_2x pricing_icon_glossary_cruise_liner_2x
features / tier
Free trial
Yacht
Ferry
Cruise Liner
MANTA for all supported scanners
Unlimited instances, revisions, and users
Native visualization (optional)
Limited metadata export from GUI
Available on premise or in the cloud
Conditional data lineage?
Automated POC
Unlimited export/import, including custom data flows, business metadata and additional properties
Service & Repository API?
Third party platform integrations
Customizations available? (paid separately)
Environment size? (number of scripts) 1,0001k 1,0001k 5,0005k 20,00020k
Price(annual in USD) Get free trial free $20,000/year20k $40,000/year40k $90,000/year90k
Extra script package(annual in USD) - 1,000 scripts for $3,000/year1k for 3k 2,000 scripts for $3,000/year2k for 3k 5,000 scripts for $3,000/year5k for 3k

Pricing Calculator

Number of scripts

Glossary

Arrow icon right Arrow icon down

environment size

Here's a little FAQ on "environment size" and how much you are going to pay for MANTA:

  • What is a script? For the purpose of pricing MANTA, scripts are all the unique code elements such as stored procedures, views, functions, ad-hoc statements, and ETL session instances.
  • How does MANTA count scripts? MANTA counts all unique scripts for which metadata is stored in MANTA's repository (it is up to the customer which metadata to keep) and/or scripts analyzed in the last 30 days. Analyzing the same, unchanged script multiple times does not increase the script count.
  • Do I have to analyze my whole BI with MANTA? No, you can analyze only selected parts based on what you need and how much would you like to pay.
  • How can I count all the scripts I want to analyze? Below are descriptions of all the technologies MANTA's scanners recognize and how you can count the scripts:

Teradata – MANTA Flow supports data dictionaries, SQL, BTEQ, stored procedures, macros, TPT, and database query logs.

How to count the number of scripts

Views, macros, stored procedures, and any SQL, BTEQ, or TPT scripts count as scripts. BTEQ and TPT scripts should be counted as the number of BTEQ and TPT files on the filesystem. And use this command to count in-database objects:

Show code

SELECT d.DatabaseName, t.TableKind, count(1)
FROM dbc.TVM as t JOIN dbc.DBase as d on t.DatabaseId = d.DatabaseId
WHERE t.TableKind in ('V','M','P')
GROUP BY d.DatabaseName, t.TableKind
;

Informatica – MANTA Flow supports workflows, mappings, sessions, SQL overrides, repositories, and parameter files.

How to count the number of scripts

PowerCenter session instances count as scripts. Indicative session count from Informatica repository:

Show code

SELECT SUBJECT_AREA, COUNT(1) FROM INFA.REP_SESSION_INSTANCES GROUP BY SUBJECT_AREA;

Oracle – MANTA Flow supports data dictionaries, SQL, PL/SQL, stored procedures, packages, functions, and triggers.

How to count the number of scripts

Procedures, packages, triggers, functions, views, types, and any SQL or PL/SQL scripts count as scripts. And this is the command to count in-database objects:

Show code

select owner, count(1)
from dba_objects
where object_name not like 'SYS_PLSQL_%'
and (
(
object_type in ('PROCEDURE','PACKAGE BODY','TRIGGER','VIEW','FUNCTION','TYPE BODY')
and status = 'VALID'
) or (
object_type = 'MATERIALIZED VIEW'
)
)
group by owner;

Microsoft SQL Server – MANTA Flow supports Microsoft PDW, Azure SQL Database, Azure SQL Data Warehouse, and SSIS tasks. Among those, it supports data dictionaries, SQL, T-SQL, stored procedures, functions, triggers, and packages.

How to count the number of scripts

Procedures, triggers, functions, views, and any SQL or T-SQL scripts count as scripts. This is the command to count global objects (run the query once for each SQL Server instance included):

Show code

select count(1) from sys.server_triggers WHERE type = 'TR'

And this is the command to count database-bound objects (run the query in every database included):

Show code

select
(select count(1) from INFORMATION_SCHEMA.ROUTINES where ROUTINE_TYPE in ('PROCEDURE', 'FUNCTION')) +
(select count(1) from INFORMATION_SCHEMA.VIEWS) +
(select count(1) from sys.triggers WHERE type = 'TR')

In Microsoft SSIS ( SQL Server Integration Services), tasks are counted as scripts. To count the number of tasks, unzip all the project files (if using project deployment), find all the package (*.dtsx) files and count the number of occurrences of "</DTS:Executable>" inside those files, minus one for each package file.
Microsoft SQL Server Analysis Services – MANTA Flow supports tabular models, and multidimensional models.

How to count the number of scripts

In Microsoft SSAS (SQL Server Analysis Services), each dimension in a cube and each table in a tabular model counts as a script. To count the number of dimensions in all cubes, count the number of occurrences of "" tag under the "" tag inside *.xmla or *.bim files for SSAS multidimensional model:

Show code

xmllint –xpath "count(//*[local-name()='Cube']/*[local-name()='Dimensions']/*[local-name()='Dimension'])" outputxml.xmla

To count the number of tables in all tabular models inside *.xmla or *.bim files for SSAS tabular model, you can use this command:

Show code

cat outputjson.xmla | jq "first(..|select(.model?)).model.tables | length"

type outputjson.xmla | jq "first(..|select(.model?)).model.tables | length"

Microsoft SQL Server Reporting Services – MANTA Flow supports tabular models, and multidimensional models.

How to count the number of scripts

In Microsoft SSRS (SQL Server Reporting Services), each report counts as a script. To count the number of reports, you can run this query in your SQL Server database where the SSRS catalog is stored:

Show code

SELECT count(*)

FROM dbo.Catalog catalog

WHERE type = 2;

SAP ASE (Sybase) – MANTA Flow supports data dictionaries, SQL, T-SQL, stored procedures, functions, triggers, and packages. Please note that we do not support SAP IQ yet.

How to count the number of scripts

Procedures, triggers, functions, views, and any SQL or T-SQL scripts count as scripts. This command can be used to count database-bound objects (run the query in every database included):

Show code

select count(1) from sysobjects WHERE type in ('V', 'P', 'TR')

Hive – MANTA Flow supports data dictionaries, and HiveQL.

How to count the number of scripts

Views and any SQL or Hive QL scripts count as scripts. To list views in Hive (2.3.0+):
Show code

SHOW VIEWS [in/from <dbName>]

To count views directly in the underlying metastore database:

Show code

select count(1) from tbls where tbl_type = 'VIRTUAL_VIEW'

IBM Netezza – MANTA Flow supports NZPLSQL scripts, stored procedures and more from IBM Netezza.

How to count the number of scripts

Procedures, views and any SQL or NZPLSQL scripts count as scripts.  This is the command to count in-database objects (run the query in every database included):

Show code

select (
(select count(distinct procedure) from _v_procedure where UPPER(OBJTYPE) = 'PROCEDURE' and BUILTIN = false) +
(select count(1) from _v_view where UPPER(OBJTYPE) in ('VIEW', 'MATERIALIZED VIEW'))
)

IBM DB2 – MANTA Flow supports data dictionaries, scripts, stored procedures, SQL, modules, functions, triggers, and Oracle compatibility mode.

How to count the number of scripts

Procedures, functions (stand-alone as well as module-and type-bound methods), packages, triggers, views, and any SQL or PL/SQL scripts count as scripts. This is the command to count in-database objects:

Show code

values (
(select count(1) from SYSCAT.ROUTINES where ORIGIN <> 'S' and OWNERTYPE <> 'S') +
(select count(1) from SYSCAT.TRIGGERS where OWNERTYPE <> 'S') +
(select count(1) from SYSCAT.TABLES where TYPE IN ('V', 'W') AND OWNERTYPE <> 'S') +
(select count(1) from SYSCAT.MODULES where OWNERTYPE <> 'S' and MODULETYPE = 'P')
)

PostgreSQL, Greenplum and Amazon Redshift – MANTA Flow supports data dictionaries, scripts, views, and functions.

How to count the number of scripts

This command should be used in each database extracted to get the number of scripts:

Show code

SELECT schema_name, count(1) as count FROM (
SELECT n.nspname AS schema_name
FROM pg_namespace n
INNER JOIN pg_class c ON n.oid = c.relnamespace
WHERE c.relkind = 'v'
UNION ALL
SELECT pn.nspname as schema_name
FROM pg_proc pp
LEFT JOIN pg_namespace pn on pn.oid = pp.pronamespace
INNER JOIN pg_language pl ON pp.prolang = pl.oid
WHERE lower(pl.lanname) in ('sql', 'plpgsql')
) dt
GROUP BY schema_name;

Pig Latin – MANTA supports Pig Latin statements, relations, bags, tuples, and fields.

How to count the number of scripts

Each Pig Latin script and macro counts as a script for the pricing purposes.  You can easily count them in your repository root folder.
Talend – MANTA Flow supports projects, jobs and subjobs, connectors, components, expressions, and SQL overrides.

How to count the number of scripts

Each Talend Job counts as a single script. You can easily count the jobs in your repository via Talend Studio for Data Integration or by navigating to the repository root folder via file explorer and counting the number of files with .item extensions located in the process folder and its subfolders.

For example, using Windows Command Line you can count the number of scripts by executing:

Show code

cd <repository_root_folder>
dir /S /B process\*.item | find /C /V ""

Sqoop – MANTA Flow supports Sqoop import, export, and eval jobs.

How to count the number of scripts

Each call for a Sqoop import, export or eval job is counted as a single script. If you manually provide files with Sqoop jobs, count all the calls for these jobs inside those files. (This can easily be done by counting all the non-empty lines.) If you provide a connection to a relational database where Sqoop jobs are stored, you can use this statement to count them:

Show code

SELECT COUNT(DISTINCT job_name) FROM SQOOP_SESSIONS;

Oracle Data Integrator – MANTA Flow support scenarios, projects, packages, and mappings.

How to count the number of scripts

ODI mappings count as scripts. Indicative mapping count from the ODI repository:

Show code

SELECT COUNT(*) from SNP_MAPPING where is_reusable = 'N';

ER/Studio – MANTA Flow supports physical models, logical models, and conceptual models.

How to count the number of scripts

ER/Studio logical and physical models count as scripts. To count the number of logical and physical models in an ER/Studio file, you can use this script:

Show code

#!/bin/bash for i in "$@" do cat "$i" | tr -d '\015' | # Convert CRLF Windows endings to the Unix ones sed -ne '/^Model$/,/^$/p' | # Get the CSV tables with models sed -ne '/^[0-9]/p' | # Get rid of headers, process entries awk -F',' ' BEGIN { count = 0; } { if ($4 == 1 || $4 == 2 || $4 == 5) # ModelType is at fourth position in the CSV, count only those models that we process (types 1,2 and 5) count++ } END { print "Number of Data Models in file \"'"$i"'\" is " count }' – done

Microsoft Excel – MANTA Flow supports XLSX and XLSM workbooks, sheets, defined names, charts, tables, pivot tables, database connections, and queries.

How to count the number of scripts

Excel workbooks, i.e. Excel files count as scripts.
 
Cognos – MANTA Flow supports reports and interactive reports (including queries with SQL), framework manager models, data modules, data sets, uploaded files and database connections.

How to count the number of scripts

Run the following script against your Content Store database to get an approximate number of scripts:

Show code

select count from .cmobjects where classid in (10,234)

SAP PowerDesigner – MANTA Flow supports physical, logical and conceptual models.

How to count the number of scripts

PowerDesigner .cdm, .pdm, and .ldm files count as scripts.

Arrow icon right Arrow icon down

unlimited tier

We call it the Fleet Tier and it has the same features as Cruise Liner but with absolutely no script limit for your company in any specific region or anywhere on the entire planet. Shoot us an email at manta@getmanta.com to get your estimate.

Arrow icon right Arrow icon down

customizations available

We offer MANTA Flow as a stand-alone product, yet in some rare cases it needs a few additional customizations to meet our customers' needs. A typical case is when a customer has a specific single sign-on system and needs to have MANTA Flow included in it.

Arrow icon right Arrow icon down

certifications

We work with huge companies all around the world and we know what the compliance needs are. That's why MANTA complies with ISO 9001 and ISO 27001.

 

We are also very well aware that clear policies are key to successful cooperation. Here's our Quality Policy and here's our Information Security Policy.

 

Arrow icon right Arrow icon down

automated proof-of-concept

A PoC (Proof of Concept, also known as a pilot in some cases) is a standard process intended to show potential MANTA customers that our solution works in their environments. To give you some insight into the process itself, we've prepared this summary for you: https://getmanta.com/poc.

Arrow icon right Arrow icon down

conditional data lineage

Conditional data lineage is usually found in huge data warehouses that use very general physical models including several big tables like PARTY, BALANCE, ORDER, and others. These tables contain data obtained from various source systems, and there are a lot of data marts and reports built on top of them. These tables make things difficult during impact analyses because data lineage from almost every report goes through them to all sources making the results worthless.

Read more about it in an article dedicated to so-called predicates.

Arrow icon right Arrow icon down

service & repository API

MANTA offers two types of API.

With Service API, our partners can now connect MANTA to their own solutions and push custom code through Manta to extract data lineage online in real-time.

The repository API gives you access to the metadata and lineage stored in the MANTA repository and allows you to connect MANTA to any custom tool or app so it can work with the extracted data lineage.

Learn more about our APIs in this article.

Arrow icon right Arrow icon down

Third-party platform integrations

MANTA is also used as an integration for third-party data governance platforms. This allows our customers to enjoy the benefits of MANTA in the environment they are already familiar with:

We cherish your privacy.

And we need to tell you that this site uses cookies. Learn more in our Privacy Policy.