Ory in the inMusic Cloud
summary
inMusic runs a homogeneous API layer over a heterogeneous backend using protobufs as the single source of truth and auto-generates REST and GraphQL gateways, docs and clients; the fleet includes 55 services deployed on AWS ECS from a mono-repo CI/CD. Authentication uses Hydra + Oathkeeper + Keto, with device login implemented as device authorization via RFC 8628, JWT introspection at the edge, Terraform-managed OAuth clients, and a sidecar plan to push scope checks closer to each service.
AI-written summary · about
chapters (8)
- 0:00Introduction and company overview
- 4:12What is the inMusic Cloud
- 6:41Technical architecture of the Cloud
- 11:59Using Hydra for user management
- 15:54Device authentication and side quests
- 18:08Oathkeeper for API authentication
- 22:24Keto for user groups and permissions
- 24:30Q&A and closing remarks
related talks
18mOry Cloud Identity for App Developers, Amorevino Firebase Example
23mBuilding a Google-like IAM system from scratch through Ory products
15mKeynote: Future Directions for the New ID Stack
22mCustomizing Ory Keto with global-scale data sharing requirements
47mAuthentication and Authorization in the World of Media and Identity Providers
25mAnaconda Unified authentication with Ory 
21mZero: Bootstrapping SaaS applications featuring Ory Kratos and Oathkeeper
23mRe-Engineering: Ory Kratos and Ory Keto in production