Amundsen on Debian
Niles Partners Inc. · Intelligence & Research
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 9 captures on record
What the publisher says
As described on Microsoft Marketplace.
Niles Partners is launching a product which will configure and publish Amundsen, to a wide variety of statistical (linear and nonlinear modeling, classical statistical tests, time-series analysis, classification, clustering) and graphical techniques which are embedded pre-configured tool with Debian10 and ready-to-launch.
Amundsen is a kind of metadata-driven application, which is the holy grail of future applications. Amundsen is used to enhance the productivity of data analysis, data scientists and engineers during interaction with data. It does that by indexing data resources (tables, dashboards, streams, etc.) and powering a page-rank style search based on usage patterns (e.g. high queried tables show up earlier than less queried tables). This product is named after Norwegian explorer Roald Amundsen, he was the first person to ascertain the South Pole.
Show the rest of the publisher’s description (6 more lines)
It has the inclusion of the three microservices entailing a data ingestion library and a common library.
- amundsenfrontendlibrary: Frontend service, is a Flask application with a React frontend.
- amundsensearchlibrary: Search service, that leverages Elasticsearch for search abilities, is used to power frontend metadata searching.
- amundsenmetadatalibrary: Metadata service, which leverages Neo4j or Apache Atlas as the persistent layer, to offer various metadata.
- amundsendatabuilder: Data ingestion library for developing metadata graph and search index. Users are able to either load the data with a python script with the library or with an Airflow DAG importing the library.
- amundsencommon: Amundsen Common library has the inclusion of common codes among microservices in Amundsen.
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Sources
Publisher resources
1 linkLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.