A familiar scene: an engineer waits for data access approval that should take seconds. Instead, it drags on for hours. The analysis sits idle, infrastructure feels locked, and everyone blames “process.” That friction is exactly what Clutch and Domino Data Lab can eliminate when they run in sync.
Clutch, an open-source internal developer platform from Lyft, gives teams self-service access to their own infrastructure. Domino Data Lab powers reproducible data science across secure environments. Alone, they each solve painful workflow problems. Together, they transform controlled chaos—permissions, environments, and versioned experiments—into a predictable pipeline.
Clutch provides automated workflows for operations like creating databases or renewing certificates with RBAC baked in. Domino centralizes data experiments and models, ensuring compliance and lineage. Wire them together correctly and the handoff between infrastructure and data teams stops being bureaucratic. It becomes policy-driven automation.
To integrate, treat Clutch as the trusted gatekeeper for infrastructure actions and Domino as the compute layer that runs authorized workloads. Identity flows through OIDC or SAML—Okta or Azure AD work fine—so that every request carries the same verified identity across both. When an engineer launches a new Domino workspace, Clutch checks RBAC rules and spins up the right resources without manual approval. Logs stay unified, policies stay auditable, and nobody needs to guess who owns a dataset.
When setting this up, align roles between Clutch’s workflows and Domino’s project-level access control. Map service accounts to data projects using least-privilege principles. Rotate credentials automatically with AWS Secrets Manager or Vault rather than hardcoding anything. It keeps both platform states consistent without exposing tokens.