Blueprints
Blueprints are ready-made Mockomat projects for common domains. Instead of building every table, attribute and relation from scratch, you clone a blueprint into your workspace and adapt it to your needs.
What a Blueprint Provides
A blueprint is a complete Mockomat project:
- Coherent tables — a set of domain tables that belong together (e.g.,
Product,Category,Reviewfor an online shop). - Relations — the relations between those tables, with direction and cardinality.
- Attributes — meaningful attributes with types and flags.
- Data mappings — the tables are bound to tables of Mockomat's data pool, so their attributes read columns of imported data (Data Source mappings).
- Operations — when you clone a blueprint, Mockomat creates the default list and detail operations for every table.
Blueprint gallery with the available domains.
Available Blueprints
| Blueprint | Tables | Typical use case |
|---|---|---|
| Users & Profiles | Organization, Team, TeamMember, User, Profile, Address, Session, Notification, ActivityLog, Preference | Accounts, teams, sessions and notifications |
| E-Commerce | Category, Product, Customer, Order, OrderItem, Review | Online shops, carts and order dashboards |
| Cars & Vehicles | Manufacturer, Vehicle, Dealer, Listing, TestDrive | Vehicle marketplaces and dealer tools |
| Real Estate | Agency, Agent, Neighborhood, Property, Viewing | Property portals and viewing schedules |
| Furniture & Home | Category, Designer, Product, Room, RoomItem, Review | Furniture catalogs and room planners |
| Food & Restaurants | Category, Product, Supplier, Location, StockItem, StockMovement | Food products, stock per location and suppliers |
Blueprints are created and maintained by the Mockomat team.
Blueprint cards with table count and description.
How to Use a Blueprint Effectively
1. Browse and Select
Open Blueprints in the app. Each blueprint card shows its domain, a short description and how many tables, attributes and relations it contains. Pick the blueprint closest to your target domain — it does not need to be a perfect match.
2. Clone into Your Workspace
Clone the blueprint to create a new project from it. The original blueprint is not modified.
What gets cloned:
- All tables and their attributes
- All relations
- All data mappings
Mockomat then creates the default operations for every table. A clone counts toward your plan's project limit; a guest replaces their one session project with the clone. Cloning into a workspace needs the Editor role or higher there.
3. Rename with Your Business Language
Replace the blueprint's generic names with your team's terminology. If the blueprint uses Product but your domain calls it Listing or Item, rename it now.
4. Review Attributes Table by Table
- Are all attributes relevant to your domain?
- Do you need attributes the blueprint does not include?
- Are the types correct?
- Are the attributes your consumers search in marked Searchable?
Remove attributes you do not need and add the ones that are missing. A new attribute stays empty until you bind it to a column of the imported data.
5. Validate Through Preview
Run a preview query to confirm the model still works:
- Do the attributes you need return values?
- Do relations resolve as expected?
- Does the response shape match your frontend's expectations?
Blueprint clone flow into the active workspace.
Customization Strategy
Do not rewrite everything at once. Keep the blueprint skeleton and evolve it in focused passes.
Pass 1: Naming and Core Attributes
- Rename tables to match your business language
- Rename key attributes (identifiers, display names)
- Add the few attributes the blueprint is missing
- Remove attributes that are clearly irrelevant
Pass 2: Relation Cleanup
- Verify the cardinality for your domain (1:1, 1:n, m:n)
- Adjust direction where the blueprint's ownership model does not match yours
- Add or remove relations
Run the preview after this pass to confirm nested queries still resolve.
Pass 3: API Exposure Alignment
In API Design:
- Rename operations to match your API conventions
- Add the parameters your consumers filter by
- Adjust default page sizes and sort orders
Pass 4: Runtime Validation
- Run queries against every table
- Test operation parameters, sorting and pagination
- Verify relations (one level deep)
Blueprint customization in model and API views.
Reusing Your Own Projects
To reuse your own structure, use Fork a project: it copies a project you can open into a workspace you choose, the same way a blueprint is cloned. Use it to keep a reference project with your team's conventions.