Application developers often want a consistent way to read and update database records without implementing every data-access operation themselves. Prisma 1 supplied a standalone GraphQL data-layer server and generated clients for that purpose. This historical chart deployed that server, which is deprecated. Modern Prisma ORM works through a different application integration, so adopting it means changing the application boundary and database access code rather than replacing the old server image while expecting the same API.
Current guidance
The archived stable/prisma chart identifies application version 1.29.1. Prisma 1’s upstream explicitly records its September 2022 deprecation; that is the scope of this retirement notice. Current Prisma tooling should not be confused with the old standalone GraphQL data-layer server, even though both share the Prisma name.
For an existing application, map the Prisma 1 service boundary before choosing a replacement: generated clients, GraphQL queries, authentication, subscriptions, data modeling and migration behavior may all depend on it. Moving to an ORM embedded in the application changes where database connections and authorization are implemented. Preserving the same database does not preserve the API contract.
Create a database backup and representative query/mutation tests, then migrate the application integration in a separate environment. Compare relations, identifiers, pagination, transactions and error handling, and plan how schema ownership changes. Avoid running two migration engines against the same production schema. Keep the old endpoint isolated during transition; neither the deprecated chart nor a newer image tag provides a supported automatic conversion.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Original publication: 2018-10-07T08:46:16+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.
Prisma is a performant open-source GraphQL ORM-like layer doing the heavy lifting in your GraphQL server.
Prisma is a data layer for modern applications. It replaces traditional ORMs and data access layers with a universal database abstraction used via the Prisma client. Prisma is used to build GraphQL servers, REST APIs & more.
- Prisma client for various languages such as JavaScript, TypeScript, Flow and Go.
- Supports multiple databases such as MySQL, PostgreSQL, MongoDB (see all supported databases).
- Type-safe database access including filters, aggregations, pagination and transactions.
- Realtime event systems for your database to get notified about database events.
- Declarative data modeling & migrations (optional) with simple SDL syntax.
The post Prisma appeared first on kubedex.com.
Sources & further reading
Spotted something that needs another look?
Help improve this page →