- Catch issues proactively before they affect consumers
- Maintain reliable and compliant data across your ecosystem
- Establish clear ownership and accountability
- Help everyone discover and understand the data they use
Elementary’s Core Principles
- Code as the source of truth - Elementary keeps your code as the system of record. Any change made in the app opens a pull request in your repository, fitting naturally into your CI/CD process and keeping engineers in control. You can work from code, from the UI, or through MCP and everything stays aligned.
- Scaling reliability with AI - Elementary uses AI to help you scale your reliability practices. Ella, our network of AI agents, assists with test creation, metadata enrichment, troubleshooting, and optimization so teams can stay proactive and focus on higher-value work.
- Enabling all users - Elementary is built for the entire organization. Business users get a clear catalog, ownership information, health scores, and AI assistance so everyone can find, understand, and trust the data without depending on engineering.
Technical Setup
Here’s a link to a checkbox version of this guide that you can download and use to track your progress: Download as markdown.
Setup and integrations
- Create Elementary cloud account (quick-start guide)
- Install Elementary dbt package
Collect dbt artifacts and enable Elementary’s built-in tests (anomaly detection, schema change detection). If you already have the package deployed in the relevant environment you want to monitor, make sure it’s up to date to the latest version, and upgrade it if not. - Connect your data warehouse
Elementary reads metadata (dbt artifacts, information schema, query history) to power test results, run history, automated freshness/volume monitors, and column-level lineage. - Invite team members
- Code repository connection (optional)
Allow users and AI agents to open PRs and manage changes through your CI/CD process. - Integrate with your BI tool (optional)
Enable column-level lineage and full context for BI assets, including the health of upstream sources and models. - Connect to your external Catalog (Optional)
Present Elementary data health context in another catalog, we support Atlan. - Non-dbt tables (optional)
Elementary has a Python SDK for python-based transformations. If you need Elementary to monitor non-dbt tables, reach out to the Elementary team with a list of relevant schemas / datasets / databases. This is a beta feature, the team will guide you through the next steps.
Alerts & Incidents
- Connect messaging app (Slack / MS Teams)
Receive alerts where your team already works. - Connect incident management tool (optional)
We support Opsgenie and PagerDuty. - Connect ticketing system (optional)
We support Jira, ServiceNow and Linear.
AI Agents
- Sign AI features consent form
Elementary AI uses only metadata, not raw or personal data. LLMs run via Amazon Bedrock with no data sharing to third parties. Learn more here. - Elementary to open AI Features
Advanced Setup
- Schedule Elementary syncs with your data warehouse.
- Contact the Elementary team to enable Okta SSO, AWS PrivateLink, or Microsoft Entra ID.
- Configuring Elementary for Development and Production
- Manage multiple environments
Use multiple dbt projects and targets (dev, staging, prod) through the multi-env feature.
If you wish to monitor multiple environments in a single environment view (including unified lineage), reach out to the Elementary team. - Collect job information from orchestrator
Elementary can collect metadata about your jobs from the orchestrator you are using, and enrich the Elementary UI with this information.
Security and permissions
- Configure roles and permissions in Elementary (optional).
- Add SSO authentication with Okta or Azure AD (optional).
- Connect using AWS private link (optional)
- Export user activity logs (optional).

