Advaneo DataMarketplace vs data.all

Advaneo DataMarketplace catalogs data offers and provides a portal for discovering, licensing, and exchanging data. It stores descriptions rather than providers’ raw data; after a buyer accepts a license and payment is confirmed, the raw data transfers directly from provider to buyer. Discovery includes text search, visual navigation, and machine-learning-based metadata recommendations. Metadata follows a standard based on IDSA standards, and the site says the platform and search support 16 languages. Providers can offer data free or commercially, set license terms and prices, and supply raw data after acceptance and payment. Payments currently support Mastercard and Visa credit cards. An IDS Connector can link file systems, databases, and sensor streams, while authenticated connectors exchange data with one another. Its cloud Workbench provides Jupyter Notebook and lists Python 3, Julia 1.0.1, R, and Ruby 2.5.1 support; common data science libraries are preinstalled and can be extended. The Free plan costs nothing and includes 15 MB of Workbench space and an IDS-Connector trial. Premium is listed at €2,950 a month, with an advanced yearly payment of 25 € monthly. Advaneo was founded in 2002 and is based in Düsseldorf, Germany.

data.all is an open-source platform for managing and discovering data assets in AWS accounts. Its central catalog inventories datasets, tables, folders, and dashboards, with filters for asset type, tags, region, and glossary terms. Datasets can contain structured tables or unstructured folders and use AWS S3, KMS, IAM, and Glue resources. Teams can share datasets between environments by granting selected roles read access through Lake Formation without moving data. The catalog imports tables from Redshift Serverless and provisioned clusters. Analytics options include Athena worksheets, SageMaker Studio access, Jupyter notebooks, and QuickSight dashboards. Administrators manage teams and users across environments. Authentication supports Cognito federation with a corporate identity provider or an external OIDC provider. Deployments may face the internet or remain inside a VPC. AWS setup requires at least two matching-region accounts and administrator credentials.