“OzzyRM replaced our scattered schema notes. The ERD alone saved onboarding time for every new hire.”
Maya Chen
Staff Engineer
Interactive schema documentation for your ORMs and raw SQL. One package, zero CSS setup. Mount it in any React-based app and ship schema docs your team will actually use.
Documentation generated from your prisma schema. Scroll to explore models and enums, or use the sidebar to jump to a section.
Application user with auth credentials and profile data.
| Field | Type | Attributes | Default |
|---|---|---|---|
id | String | PKrequired | cuid() |
email | String | uniquerequired | - |
role | Role | required | USER |
posts | Post | list | - |
Blog post authored by a user, with optional comments.
| Field | Type | Attributes | Default |
|---|---|---|---|
id | String | PKrequired | cuid() |
title | String | required | - |
author | User | - | - |
comments | Comment | list | - |
Comment left on a post by a user.
| Field | Type | Attributes | Default |
|---|---|---|---|
id | String | PKrequired | cuid() |
body | String | required | - |
post | Post | - | - |
author | User | - | - |
Marks a field as unique across all records in the table.
Text values such as names, emails, or identifiers stored as text.
Primary key. Uniquely identifies each row in the model.
Field must always have a value; maps to NOT NULL in SQL.
Works with
I built OzzyRM to make schema docs easier while I develop. One place to explore models, relations, and types without leaving the app, so shipping database work feels clearer from day one.

Rizain
OzzyRM Developer
Reviews
“OzzyRM replaced our scattered schema notes. The ERD alone saved onboarding time for every new hire.”
Maya Chen
Staff Engineer
“We mount it next to our React app and the whole team finally looks at the same model docs.”
Jordan Lee
Full-stack Developer
“Prisma plus SQL in one place felt impossible before. Unified schemas are the feature we needed.”
Aisha Rahman
Backend Lead
“Search and glossary make the docs usable day one. No more asking what every attribute badge means.”
Noah Park
Product Engineer
“OzzyRM replaced our scattered schema notes. The ERD alone saved onboarding time for every new hire.”
Maya Chen
Staff Engineer
“We mount it next to our React app and the whole team finally looks at the same model docs.”
Jordan Lee
Full-stack Developer
“Prisma plus SQL in one place felt impossible before. Unified schemas are the feature we needed.”
Aisha Rahman
Backend Lead
“Search and glossary make the docs usable day one. No more asking what every attribute badge means.”
Noah Park
Product Engineer
“Zero CSS setup was the closer. Install, point at the config, ship schema docs in an afternoon.”
Elena Vos
Platform Engineer
“The interactive ERD is what I show stakeholders. Models and relations finally look intentional.”
Sam Ortiz
Tech Lead
“Onboarding juniors used to take a week of schema walkthroughs. Now they explore OzzyRM themselves.”
Priya Nair
Engineering Manager
“Clean, fast, and actually pleasant to open. Schema docs finally feel like product, not homework.”
Chris Boone
Software Engineer
“Zero CSS setup was the closer. Install, point at the config, ship schema docs in an afternoon.”
Elena Vos
Platform Engineer
“The interactive ERD is what I show stakeholders. Models and relations finally look intentional.”
Sam Ortiz
Tech Lead
“Onboarding juniors used to take a week of schema walkthroughs. Now they explore OzzyRM themselves.”
Priya Nair
Engineering Manager
“Clean, fast, and actually pleasant to open. Schema docs finally feel like product, not homework.”
Chris Boone
Software Engineer
Features
OzzyRM ships a complete schema documentation experience. Mount it in your app with zero CSS setup.
01 / 05
Every schema overview includes an interactive entity-relationship diagram. Models, fields, and relations laid out automatically. Click any node to jump to its detail page.
Documentation generated from your prisma schema. Scroll to explore models and enums, or use the sidebar to jump to a section.
02 / 05
Fields table with types, attributes, defaults, and relation links. Indexes, referenced-by lists, and source attribution when schemas are unified across ORMs.
Application user with auth credentials and profile data.
| Field | Type | Attributes | Default |
|---|---|---|---|
id | String | PKrequired | cuid() |
email | String | uniquerequired | - |
role | Role | required | USER |
posts | Post | list | - |
Blog post authored by a user, with optional comments.
| Field | Type | Attributes | Default |
|---|---|---|---|
id | String | PKrequired | cuid() |
title | String | required | - |
author | User | - | - |
comments | Comment | list | - |
Comment left on a post by a user.
| Field | Type | Attributes | Default |
|---|---|---|---|
id | String | PKrequired | cuid() |
body | String | required | - |
post | Post | - | - |
author | User | - | - |
03 / 05
Search models, enums, and glossary entries from the sidebar. Debounced input with keyboard navigation. Find any field or type without scrolling.
Marks a field as unique across all records in the table.
Text values such as names, emails, or identifiers stored as text.
Primary key. Uniquely identifies each row in the model.
Field must always have a value; maps to NOT NULL in SQL.
04 / 05
Every enum gets its own section with values, database names, and descriptions. Navigate from field type badges or the sidebar.
User permission level across the application.
| Name | DB Name |
|---|---|
| USER | user |
| ADMIN | admin |
| MODERATOR | moderator |
Publication state for a post.
| Name | DB Name |
|---|---|
| DRAFT | draft |
| PUBLISHED | published |
| ARCHIVED | archived |
05 / 05
Merge Prisma, Drizzle, and SQL sources into one graph. Define scenarios to highlight use-case slices with filtered ERD paths.
Documentation generated from a merged graph across multiple sources. Scroll to explore models and enums, or use the sidebar to jump to a section.
FAQ
Short answers about adapters, setup, unified sources, and what ships in the docs UI.
Prisma, Drizzle, and raw SQL are supported now. More adapters are on the roadmap, including TypeORM, Sequelize, Eloquent, and others.
No. Install the package, point it at your schema, and mount the React docs UI in your app. OzzyRM ships with its own styles so you do not maintain a parallel docs stack.
Yes. The docs UI is React-based. Use OzzyRMDocs, OzzyRMDocsFromConfig on an RSC host, or the framework-agnostic mount() helper on a DOM node. Catalog loading and the CLI work in Node or Bun regardless of your frontend framework. Next.js is one option, not a requirement.
A unified schema merges multiple sources into one documented graph. Each model and enum keeps a from: badge so you can see which Prisma, Drizzle, or SQL source it came from.
Scenarios slice the full graph into a use-case path, such as an auth flow. The sidebar lists them separately from the unified overview, with a filtered ERD for that path.
Yes. Sidebar search finds models, enums, and glossary terms. Type and attribute badges open the matching glossary documentation pages on this website. There is no in-app glossary sheet.
Yes for schema documentation. You get ERDs, model tables, enums, search, and unified sources in one package. Start from the installation guide and ship docs your team will actually open.
Install OzzyRM, point it at your schema, and mount the UI. No CSS setup. No separate docs site to maintain.
Share feedback
Ideas, reviews, or contribution notes help shape what ships next.