Elementl
Elementl, Inc. is the company behind Dagster, rebranded as Dagster Labs in August 2023. Founded in 2018 by Nick Schrock (creator of GraphQL) and led by CEO Pete Hunt, the San Francisco company builds Dagster, an open-source, Apache-2.0 licensed, cloud-native data orchestration platform, and Dagster+, its managed cloud offering. Dagster's defining innovation is the Software-Defined Asset model, which treats data tables, ML models, and datasets as first-class, versioned objects with built-in lineage, data quality checks, and observability rather than as ordered task lists. The platform exposes a GraphQL API and a REST API for reporting external asset materializations, checks, and observations, plus Python and CLI clients. The company has raised roughly $48.8M, including a $33M Series B (2023) led by Georgian with participation from Sequoia, Index Ventures, Amplify, 8VC, Human Capital, Hanover, and Slow. The Dagster product API surface is catalogued separately in the api-evangelist/dagster profile.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Elementl the way a machine reads it — 3 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Elementl scores 31.2/100 (thin), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Elementl
Each block below is one kind of artifact we hold for Elementl. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Elementl — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/elementl · machine-readable index on apis.io