fackapi.studio
How to startInteractive FlowFeaturesStorage & Pricing
WorkspaceLet's Contribute

Design the mock APIon a canvas.Serve it from yourown machine.

Build and test independently of a backend that is not ready.

Open the canvas
View the source

Self-hostedOne SQLite fileMIT licensed

How to start

From zero to a live endpoint in four steps.

Fack API's runs on your own machine. Bring it up, name a project, map a few fields to Faker providers, then call the route over HTTP. No database server to run, no API keys to configure.

  1. 01

    Run it locally

    Two ways to bring it up. Docker Compose builds the image and starts the stack; from source runs the app in dev mode. Both end with the server listening on port 3000.

    Choose how to run Fack API
    Docker Engine with Compose v2
    $docker compose up -d
    http://localhost:3000·the dashboard opens here
  2. 02

    Name a project

    A project owns its endpoints, and its slug is the first segment of every mock URL it serves. Endpoints carry a base path; routes hang off them.

    http://localhost:3000GET
    project
    acme-store
    endpoint
    User Service · /v1
    route
    GET /users
    served at/acme-store/v1/users
  3. 03

    Attach a schema

    Pick a provider for each field on the canvas. The result is stored as standard JSON Schema with an x-faker extension, so the contract stays portable to any tool.

    response schemaJSON Schema
    {  "type": "object",  "properties": {    "id":    { "type": "string", "x-faker": "string.uuid" },    "name":  { "type": "string", "x-faker": "person.fullName" },    "email": { "type": "string", "x-faker": "internet.email" }  }}
  4. 04

    Call the route

    The route answers as soon as you save it. Point your app at the URL, or check it from the terminal — the payload is generated per request, not stored.

    terminal200 OK
    $curl http://localhost:3000/acme-store/v1/users
    {  "data": {    "id": "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d",    "name": "Jordan Peterson",    "email": "jordan.peterson@example.org"  },  "meta": {    "statusCode": 200,    "success": true,    "latency": 4,    "method": "GET",    "path": "/v1/users"  }}

The full walkthrough is in the docs.

Every dialog, step by step, plus chaos rules, scenarios, and the TypeScript export.

Read the walkthrough

Nothing leaves your machineLocal SQLite storage · MIT licensed

faker.js
N
Next.js
SQLite
TypeScript
drizzle.orm
React Flow
Zustand
OpenAPI 3.0
faker.js
N
Next.js
SQLite
TypeScript
drizzle.orm
React Flow
Zustand
OpenAPI 3.0
faker.js
N
Next.js
SQLite
TypeScript
drizzle.orm
React Flow
Zustand
OpenAPI 3.0

Everything You Need for Modern Mock APIs & Schema Architecture

Built from the ground up to empower developers, QA engineers, and frontend teams with visual, type-safe API simulation tools.

Flow Canvas

Visual Flow Canvas

Construct API schema nodes, define route parameters, and draw relation edges using a responsive React Flow interactive canvas.

Explore Feature: Visual Flow Canvas
Faker.js

20+ Faker.js Generators

Synthesize realistic users, transactions, UUIDs, dates, and addresses automatically powered by @faker-js/faker.

Explore Feature: 20+ Faker.js Generators
Chaos Engine

Chaos & Latency Injector

Simulate real-world network edge cases: status code errors (404, 500), response delays (100ms - 5000ms), and custom HTTP headers.

Explore Feature: Chaos & Latency Injector
Local First

Client-Side SQLite Engine

100% offline & private. All schema definitions, route configs, and execution logs remain strictly within local SQLite storage.

Explore Feature: Client-Side SQLite Engine
DTO & OpenAPI

1-Click DTO Export

Instantly generate TypeScript interfaces, Drizzle ORM schemas, or OpenAPI 3.0 spec files ready to paste into your codebase.

Explore Feature: 1-Click DTO Export
Zero Latency

Zero-Latency Mocks

Lightning-fast mock response generation with built-in memory caching and dynamic route path pattern matching.

Explore Feature: Zero-Latency Mocks

100% Free & Open Source.
Zero Vendor Lock-in.

Run Fack API on your own machine or infrastructure and store mock routes in your own database. You retain 100% ownership of your mock schema data.

Local-First Self-Hosted

100% Private

Store route schemas and mock definitions in a local SQLite database on your own machine. Runs fully offline with no third-party dependencies.

$0/ Free & Open Source
  • SQLite persistence on your own machine
  • Instant local auto-save & workspace sync
  • Portable single-file OpenAPI & JSON schema export
  • No paywalls, no usage limits, no vendor lock-in
Launch Local Workspace

Self-Hosted & Docker

Self-Hosted

Deploy Fack API on your own infrastructure with Docker, Vercel, or local Node.js. Run mock endpoints in your internal networks.

MIT License
  • Multi-endpoint simulated HTTP routes & latency delays
  • Complete offline control with custom Faker.js seeds
  • Docker container & docker-compose ready to run
  • 100% Free for commercial & open-source projects
View on GitHub

Unlock what's hidden

Get updates on mock schema templates, Faker.js generators, and new releases. Stay updated with modern API design patterns and developer tooling.

Platform

  • Visual Flow Canvas
  • Faker.js Engine
  • DTO & Schema Export
  • Chaos Injector
  • Storage & Privacy
  • Workspace

Ecosystem

  • GitHub Repository
  • Release Notes
  • Author GitHub
  • MIT License

©2026 Fack API Studio. All Rights Reserved. Crafted by Karelaking.

Dashboard•GitHub•License
Interactive Dashboard Preview

Create Mock Endpoints in Seconds.
Deploy Without Writing a Server.

Experience how easy it is to create mock routes in the Fack API dashboard. Configure methods, assign Faker.js generators, inject simulated chaos, and see instant live outputs below.

Dashboard: Endpoint Builder
Step 1: Configure
1. Select Method & Route PathHTTP Route
2. Assign Faker.js Schema GeneratorsClick to Toggle
Launch Dashboard to Create Yours
GEThttps://fackapi.studio/api/v1/users
200 OK • 24ms
{
  "page": 1,
  "limit": 10,
  "total": 150,
  "data": [
    {
      "id": "usr_99a8b1",
      "name": "Alexander Vance",
      "email": "alex.vance@fackapi.dev",
      "role": "Principal Systems Architect",
      "status": "active"
    }
  ]
}
Instant Dynamic SynthesisReady for curl & frontend fetch
Step 3: Ready to use