Your schema. Every layer connected.Less code in between.
Keep your Prisma schema, client and migrations. Aventara turns your models and configuration into contracts, a typed HTTP API and a frontend client.
model User { id String @id @default(cuid()) email String @unique name String?}const users = await avClient.User.find.many({ select: ["id", "name"], limit: 3,});{ id: string; name: string | null }[]The selected fields shape your result. Your Prisma schema stays the source.
Stop describing the same data. Again.
Your database schema already describes your data. Aventara carries that shape through the API and into your frontend, so you can spend your time on what your application actually does.
One model. A deliberate API.
Compile your Prisma schema and configuration into contracts that describe resources, fields and operations. Choose what your API exposes.
Explore the guideA different view for every layer.
Hide sensitive fields, make them write-only, or turn off frontend operations while server code keeps full access.
Explore the guideTypes that follow your query.
Select the fields you need. Your generated client knows the result shape, with no runtime dependency on Aventara packages.
Explore the guideYour business logic belongs here.
Add guards, pipes and hooks through pipelines. Compose transactions with typed references between steps.
Explore the guideEvery layer, connected.
Your schema and configuration become a contract. NestJS or Next.js serves it. Your frontend gets a typed client generated from the deployed contract.
Your next API starts with a schema.
Create a project, connect your models, and build the parts that make your application yours.
Build with FrameworkDo I keep my Prisma client and migrations?
Yes. Your application owns its Prisma client, schema and migrations. Aventara extends your ORM and runs operations through the adapter.
Which hosts can serve the API?
NestJS 12 on Express or Fastify, or a Next.js App Router app on the supported Node runtime. The docs cover both hosts.
Do I need Access?
Access is optional. The framework works on its own; Access adds schema-typed authorization when your application needs it.
Is the API stable?
The framework is a release candidate. Breaking changes are still possible before a stable release. Pin versions and follow the upgrade guide.