FAQ
General
What is Mockomat?
Mockomat is a domain modeling and API simulation platform. You define your data model visually, map it to realistic data sources, and get a live GraphQL API instantly — without writing backend code. When your model is ready, you can export a production-ready NestJS backend that you fully own.
Who is Mockomat for?
Mockomat is designed for:
- Frontend developers who need a realistic backend to develop against before the real API is ready.
- Full-stack engineers who want to prototype domain models and validate API behavior quickly.
- Agencies building client projects that need fast mock APIs for demos and development.
- Architects who want to validate domain structure and API contracts before committing to implementation.
- Educators teaching API design, GraphQL, or domain-driven development.
- Teams that need a shared, realistic mock API for parallel frontend and backend development.
Is Mockomat only a mock server?
No. Runtime simulation is one outcome, but the core value is domain-level control from model to implementation handoff. Mockomat gives you a structured path from domain modeling → API definition → runtime validation → code generation. The mock API is a means to validate your architecture, not just serve fake data.
Does Mockomat replace AI tooling?
No. AI accelerates code generation; Mockomat keeps structure and intent explicit as systems evolve. They complement each other: use AI to generate code quickly, use Mockomat to ensure the underlying domain model and API contracts remain consistent, reviewable, and traceable.
How does Mockomat compare to tools like Postman or Stoplight?
Postman and Stoplight are excellent for API testing and documentation. Mockomat operates at a different level:
- Postman focuses on testing existing APIs. Mockomat creates the API from a domain model.
- Stoplight focuses on API design and documentation. Mockomat adds runtime simulation and code generation.
- Mockomat covers the full pipeline: model → simulate → validate → generate backend. It is not a testing tool — it is a modeling and generation platform.
Getting Started
Can I start without creating an account?
Yes. Guest mode (Quick tier) lets you start immediately without registration. You get one temporary project with a public GraphQL endpoint. Your work is tied to your browser session — create an account when you want to save it.
What is the difference between Quick and Free?
| Quick | Free | |
|---|---|---|
| Registration | None required | Account required |
| Projects | 1 temporary | Up to 5 persistent |
| Persistence | Session only (lost on tab close) | Saved across sessions |
| API requests | Rate-limited per IP | 1,000 per day |
| Endpoints | Public | Public |
Quick is for instant exploration. Free is for ongoing work.
How long does it take to set up a working mock API?
About 15 minutes for a basic model with a few entities and relations. See the Getting Started guide for a step-by-step walkthrough.
Data and Mapping
What data sources does Mockomat use?
Mockomat supports three mapping types for generating field values:
- OFF_FIELD — maps to real-world dataset fields (e.g., Open Food Facts) for realistic, diverse data.
- FAKE — uses Faker to generate synthetic data: names, emails, addresses, dates, prices, and more.
- CONST — returns a fixed value for every record (e.g., a default status like
"active").
Enterprise customers can also upload custom proprietary datasets.
Is the data realistic?
Yes. OFF_FIELD mappings use real product data from open-licensed datasets, and Faker generates realistic synthetic data that follows real-world patterns (proper name formats, valid email structures, realistic price ranges). The data is not random garbage — it is designed to feel authentic.
What about data privacy?
Mockomat stores project metadata (model definitions, mappings, configuration) but does not handle real production data. Mock APIs serve synthetic or dataset-backed data, never real customer information. This makes Mockomat inherently safe for development environments and eliminates PII concerns.
Can I import an existing schema?
OpenAPI import is supported as an input source for the export (code generation) feature. Additional import formats (JSON Schema, code-first import) are planned for future releases.
Technical
What tech stack does Mockomat use?
- Backend: NestJS, Apollo GraphQL (code-first), MongoDB, MariaDB, Redis
- Frontend: Angular 21, NgRx, Apollo Angular, Angular Material
- Code Generation: Python with Jinja2 templates
- Infrastructure: Docker, deployable to AWS, GCP, or any Node.js hosting environment
What does the generated backend include?
The export feature generates a complete NestJS project with:
- Domain modules (one per entity) with controllers/resolvers, services, entities, and DTOs
- Database configuration (TypeORM for SQL or Mongoose for MongoDB)
- Optional JWT authentication scaffolding
- Input validation with class-validator decorators
- A README with setup instructions
See the Export documentation for full details.
Is the generated backend production-ready?
The generated code compiles, runs, and serves the API you designed. It is a high-quality starting point — not a finished product. You will need to add custom business logic, integrate external services, configure production infrastructure, and write tests. Think of it as eliminating the scaffolding phase so your team can focus on business value from day one.
Can I use the generated code commercially?
Yes. Generated code is 100% owned by you with no license restrictions. You can modify, deploy, redistribute, and commercialize it without attribution or fees.
Can I deploy to AWS, GCP, Azure, or on-premise?
Yes. The generated backend is a standard NestJS application that runs anywhere Node.js runs. No Mockomat-specific runtime or SDK is required.
Do I need NestJS knowledge to use Mockomat?
Not to model, simulate, or export. NestJS knowledge is needed to extend the generated backend with custom business logic. The generated code follows NestJS conventions, so any NestJS developer can pick it up immediately.
What GraphQL operations are supported?
Each entity generates:
- List query — paginated collection with optional filter and sort
- Detail query — single item by ID
Mutations (create, update, delete) are part of the generated backend code, not the mock runtime.
Plans and Pricing
How does pricing work?
Mockomat offers a generous free tier and scales with your needs:
- Quick (free) — no login, 1 temporary project
- Free (free) — account required, 5 projects, 1,000 req/day
- Business ($19/month) — private endpoints, API keys, 50k req/month
- Business Pro ($49/month) — teams, analytics, 250k req/month
- Enterprise (custom) — unlimited, custom datasets, SLAs
See the Account and Plans page for full details.
Can I collaborate with my team?
- Free: No collaboration features — projects are personal.
- Business: Role-based access for sharing projects with controlled permissions.
- Business Pro: Multi-user teams with concurrent session management.
- Enterprise: Full team management with admin roles, configurable session limits, and audit capabilities.
What happens if I exceed my request limit?
The API returns HTTP 429 (Too Many Requests) with a Retry-After header. Free tier limits reset daily at midnight UTC. Paid tier limits reset on your billing date. You can purchase additional request capacity as an add-on.
Blueprints
What is a blueprint?
A blueprint is a pre-built Mockomat project template covering a common domain pattern (e.g., E-Commerce, CRM, Blog). You clone a blueprint into your workspace and customize it with your own names, attributes, and relations. It saves you from building common structures from scratch.
Can I create my own blueprints?
Community blueprint publishing is a planned feature. Currently, all blueprints are curated by the Mockomat team. In the future, registered users will be able to submit their own projects as community blueprints.
Troubleshooting
For a comprehensive diagnostic guide covering empty responses, null fields, relation issues, sort/filter problems, authentication errors, and more, see the dedicated Troubleshooting reference.
Quick Checks
- Empty data? Verify data import is complete and all attributes have mappings. See Troubleshooting → Empty Responses.
- Relations return empty arrays? Check relation direction and target entity. See Troubleshooting → Empty Relations.
- Sorting or filtering has no effect? Ensure the field is marked as
sortableorfilterable. See Troubleshooting → Sort and Filter Issues.
Why are some screenshots marked as missing?
Documentation is built with screenshot IDs and placeholders first. This keeps content production moving while final captures are prepared. Missing screenshots will be replaced with actual captures as they become available.
Future Features
Will there be a CLI tool?
A CLI tool is planned that will support login, code generation, local preview, and CI/CD integration from the command line.
Will there be additional export targets?
NestJS is the primary export target. Additional targets (Laravel, Prisma, TYPO3) are planned for future releases based on demand.
Will there be real-time collaboration?
Real-time collaborative editing (multiple users editing the same model simultaneously) is on the roadmap for enterprise plans.
FAQ page visual placeholder.