E-commerce
10 tablesCustomers, products, categories, orders, payments and reviews — the classic online store schema.
Database templates
Starting a new project? Open a template in the editor in one click, delete what you don't need, rename the rest — a proven skeleton beats a blank canvas. Every template is a real, normalized schema with keys and relationships already wired.
Treat them as starting points, not gospel. Each one encodes decisions that are common but not universal: how prices are stored, how membership roles are modeled, where a join table carries extra columns. They are the patterns most projects in that domain end up needing — the part that usually takes the first evening of a new codebase. If you want to read the full SQL before opening anything, every template also has a detail page with the schema, the diagram and a table-by-table breakdown.
SaaS
8 tablesUsers, workspaces, projects, tasks and billing — the backbone of a subscription SaaS.
Blog
6 tablesUsers, posts, categories, comments and tags — a content platform schema with many-to-many tagging.
CRM
7 tablesCompanies, contacts, deals and activities — how a sales pipeline is modeled.
School
7 tablesStudents, teachers, courses, classes, enrollments and attendance — a school in seven tables.
Booking
8 tablesHotels, room types, rooms, guests, bookings and payments — a booking engine schema.
Inventory
6 tablesWarehouses, suppliers, products, stock levels and purchase orders — tracking goods end to end.
Project management
9 tablesOrganizations, projects, members, tasks, labels and sprints — a team tool schema.
Social
9 tablesUsers, posts, comments, likes, follows and private messages — the social graph schema.
Restaurant
8 tablesRestaurants, menu items, customers, orders and reservations — from menu to kitchen ticket.
General
7 tablesAuthors, books, members, loans and fines — catalog and circulation for a lending library.
General
9 tablesDepartments, doctors, patients, appointments, prescriptions, admissions and invoices.
General
8 tablesBranches, customers, accounts, holders, transactions, cards and transfers — a retail bank core.
General
8 tablesMembers, plans, subscriptions, trainers, classes, sessions, bookings and check-ins.
General
9 tablesRestaurants, menus, customers, addresses, couriers, orders and deliveries — from basket to doorstep.
General
7 tablesDepartments, employees, job titles, payroll runs, payslips, leave and attendance.
How to use one
Pick the template closest to your domain and click Open in ERDGenerator. It loads into the visual editor as an ordinary project — nothing is locked. Move tables around until the layout reads well, delete the tables you don't need, add columns, and draw new relationships with the right cardinality. When the shape is right, export: runnable SQL for your dialect (PostgreSQL, MySQL, SQLite or SQL Server), a PNG or SVG for documentation, or a read-only share link to get feedback from a teammate or client before you write any migration.
Adapting a template to your domain
The value of a template is in its structure, not its names. A few edits cover most cases. Rename tables and columns to your vocabulary — customers becomes members, orders becomes bookings — and keep the relationships intact. Add join tables where your domain has many-to-many links the template does not model. Snapshot values that change over time: if the e-commerce template stores a price on the product, copy it onto the order line when you need historical invoices to survive later price changes. Adjust column types and lengths to your actual constraints rather than keeping the defaults. Delete anything that exists in the template only for completeness — an unused table is worse than a missing one, because the next reader assumes it matters.