What it does
NocoDB connects to supported SQL databases and offers grid-style interfaces with API access. Features and connector support depend on the current edition and configuration.
Why it’s interesting
Schema introspection connects developer-owned data with operations-facing interfaces. Permission boundaries matter when exposing existing databases.
Real-world use case
Create an internal project tracker over a dedicated staging database.
What I can learn
- 01
Database metadata to virtual models
Trace how existing database tables and relations become application models without changing the underlying SQL schema.
- 02
Virtualized grid rendering
Study how a grid renders only visible rows and columns so large tables remain responsive during scrolling.
- 03
SQL generation across database dialects
See how UI filters and sorting are translated into SQL for different database engines.
One thing to explore
Models and controllers
Follow the packages/nocodb/src implementation and connect it to the concepts above.
Explore the source (opens in a new tab)10-Minute Challenge
Explore table views
Before you start: Docker and a local database; use disposable records and review access settings before connecting any existing database.
- Read the current edition and license terms.
- Start a local instance following official docs and use disposable data.
- Create a small Projects table and compare its grid and form views.