Architecture
How Mock API Studio Works: Cloud Configuration and Local Runtime
Understand the boundary between Mock API Studio's cloud control plane and its local runtime, including synchronization, generated records, SQLite state, and request handling.
Cloud configuration
The dashboard stores account, workspace, project, TypeScript model, endpoint, relationship, and runtime configuration. It is the shared control plane for defining what the mock should expose.
Local execution
The CLI authenticates, downloads an accessible project definition, and starts Express routes plus a SQLite data store on your machine. API requests, generated records, authentication state, and CRUD mutations are handled locally.
Dashboard configuration -> CLI synchronization -> localhost Express API -> local SQLite stateSynchronization boundary
Configuration is synchronized when the CLI starts. Restart the process after dashboard changes. The runtime does not upload generated records or local CRUD state to the cloud.
Security boundary
Keep API tokens private and do not put real production secrets or customer data into mock projects. Local authentication features simulate application flows; they are not a substitute for production security testing.
Related questions
Does the cloud host my generated mock endpoint?
No. The cloud stores project configuration; the CLI serves the generated endpoint and records locally.
Keep exploring
Last updated September 17, 2026. Product behavior described here is verified against the current Mock API Studio runtime.