Getting Started

Introduction

What Crudy is and why it exists.

Crudy is a full-stack framework for building licensed, multi-tenant internal tools. It pairs a typed Fastify backend with a Next.js frontend and a pluggable module system so you can ship CRMs, trackers, dashboards, and back-office apps without rebuilding auth, permissions, and tenancy every time.

What you get out of the box

A Fastify API with JWT authentication and an OAuth2 password grant.
A PostgreSQL data layer with the pgmorbac extension for multi-org role-based access control.
A Next.js (App Router) frontend with pre-built pages for login, settings, organizations, users, and roles.
A CLI to scaffold new apps and new modules.
A license model that gates which modules a deployment can run and enforces per-org record quotas. Licenses are issued by Crudy (pricing).

Who Crudy is for

Crudy is aimed at engineering teams who:

Build internal applications more than once a year and want a shared chassis instead of starting from scratch.
Need real multi-tenancy with org trees, role inheritance, and granular permissions, not flat tenant IDs glued onto SaaS code.
Want the freedom to deploy anywhere Node and PostgreSQL run, with no managed control plane in the loop.

Note

Crudy is opinionated about security defaults and the shape of a module. It is not a low-code builder. You write TypeScript, your modules live in source, and your data model lives in plain SQL migrations.

How the rest of the docs are laid out

Getting Started walks you from install to a running app, then introduces the CLI.
Architecture explains the moving parts: which package owns what, how an app folder is structured, and how modules plug into the framework.
Modules is the reference for building your own backend and frontend modules, declaring quotas, and shipping a complete example.
Deployment covers Docker, environment variables, and how licensing works for the consumer side.

If you are evaluating Crudy, start with Architecture: Overview. If you want to ship something today, go straight to Quickstart.

What you get out of the box

A Fastify API with JWT authentication and an OAuth2 password grant.

A PostgreSQL data layer with the pgmorbac extension for multi-org role-based access control.

A Next.js (App Router) frontend with pre-built pages for login, settings, organizations, users, and roles.

A CLI to scaffold new apps and new modules.

A license model that gates which modules a deployment can run and enforces per-org record quotas. Licenses are issued by Crudy (pricing).

Who Crudy is for

Crudy is aimed at engineering teams who:

Build internal applications more than once a year and want a shared chassis instead of starting from scratch.

Need real multi-tenancy with org trees, role inheritance, and granular permissions, not flat tenant IDs glued onto SaaS code.

Want the freedom to deploy anywhere Node and PostgreSQL run, with no managed control plane in the loop.

Note

How the rest of the docs are laid out

Getting Started walks you from install to a running app, then introduces the CLI.

Architecture explains the moving parts: which package owns what, how an app folder is structured, and how modules plug into the framework.

Modules is the reference for building your own backend and frontend modules, declaring quotas, and shipping a complete example.

Deployment covers Docker, environment variables, and how licensing works for the consumer side.

If you are evaluating Crudy, start with Architecture: Overview. If you want to ship something today, go straight to Quickstart.