Understand Your Schema Like Never Before

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.

localhost:3000/docs#overview

Schema

Documentation generated from your prisma schema. Scroll to explore models and enums, or use the sidebar to jump to a section.

Entity relationship
localhost:3000/docs#model

User

table: users

Application user with auth credentials and profile data.

6 fieldsreferenced by 2
FieldTypeAttributesDefault
id
String
PKrequired
cuid()
email
String
uniquerequired
-
role
Role
required
USER
posts
Post
list
-

Post

table: posts

Blog post authored by a user, with optional comments.

5 fieldsreferenced by 1
FieldTypeAttributesDefault
id
String
PKrequired
cuid()
title
String
required
-
author
User
-
-
comments
Comment
list
-

Comment

table: comments

Comment left on a post by a user.

4 fields
FieldTypeAttributesDefault
id
String
PKrequired
cuid()
body
String
required
-
post
Post
-
-
author
User
-
-
localhost:3000/docs#docs
unique
  • @uniqueattribute

    Marks a field as unique across all records in the table.

  • Stringtype

    Text values such as names, emails, or identifiers stored as text.

  • PKattribute

    Primary key. Uniquely identifies each row in the model.

  • requiredattribute

    Field must always have a value; maps to NOT NULL in SQL.

↑↓NavigateOpenescClose

Works with

Any Preferences You Already Use

Supported

PrismaDrizzleSQL

Future support

Coming Soon

TypeORM
Sequelize
Eloquent
Doctrine
SQLAlchemy
Hibernate
GORM

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

Rizain

OzzyRM Developer

Reviews

What builders are saying

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

Everything inside the docs UI

OzzyRM ships a complete schema documentation experience. Mount it in your app with zero CSS setup.

01 / 05

Auto-generated ERD

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.

localhost:3000/docs#overview

Schema

Documentation generated from your prisma schema. Scroll to explore models and enums, or use the sidebar to jump to a section.

Entity relationship

02 / 05

Model & field documentation

Fields table with types, attributes, defaults, and relation links. Indexes, referenced-by lists, and source attribution when schemas are unified across ORMs.

localhost:3000/docs#user

User

table: users

Application user with auth credentials and profile data.

6 fieldsreferenced by 2
FieldTypeAttributesDefault
id
String
PKrequired
cuid()
email
String
uniquerequired
-
role
Role
required
USER
posts
Post
list
-

Post

table: posts

Blog post authored by a user, with optional comments.

5 fieldsreferenced by 1
FieldTypeAttributesDefault
id
String
PKrequired
cuid()
title
String
required
-
author
User
-
-
comments
Comment
list
-

Comment

table: comments

Comment left on a post by a user.

4 fields
FieldTypeAttributesDefault
id
String
PKrequired
cuid()
body
String
required
-
post
Post
-
-
author
User
-
-

03 / 05

Instant search

Search models, enums, and glossary entries from the sidebar. Debounced input with keyboard navigation. Find any field or type without scrolling.

localhost:3000/docs#search
unique
  • @uniqueattribute

    Marks a field as unique across all records in the table.

  • Stringtype

    Text values such as names, emails, or identifiers stored as text.

  • PKattribute

    Primary key. Uniquely identifies each row in the model.

  • requiredattribute

    Field must always have a value; maps to NOT NULL in SQL.

↑↓NavigateOpenescClose

04 / 05

Enum reference

Every enum gets its own section with values, database names, and descriptions. Navigate from field type badges or the sidebar.

localhost:3000/docs#role

Role

3 values

User permission level across the application.

NameDB Name
USERuser
ADMINadmin
MODERATORmoderator

Status

db: post_status3 values

Publication state for a post.

NameDB Name
DRAFTdraft
PUBLISHEDpublished
ARCHIVEDarchived

05 / 05

Unified schemas & scenarios

Merge Prisma, Drizzle, and SQL sources into one graph. Define scenarios to highlight use-case slices with filtered ERD paths.

localhost:3000/docs#overview
unified0.3.23 models1 enums

Unified schema

Documentation generated from a merged graph across multiple sources. Scroll to explore models and enums, or use the sidebar to jump to a section.

from: app-prismafrom: billing-drizzlefrom: legacy-sql
Entity relationship

FAQ

Common questions

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.

Ship Schema 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.