Fearless API Development.

Foreign keys that seed valid IDs out of the box? Sold.

First mock server my designer could run herself.

Wrote an entire demo backend in YAML on the train to a meetup. Zero servers harmed, fully offline.

Custom error bodies per route saved my integration tests. Finally a mock that fails the way prod does.

Replaced a 200-line Express mock with a 12-line akuma.yml. Code review took thirty seconds, and my frontend team finally stopped waiting on me to hand-write fixtures.

The persistence is the part I didn't know I needed. I seed once, refresh the page a hundred times, and the data is still sitting right where I left it. No more re-stubbing on every reload.

We kept a janky json-server fork limping along for every prototype, and someone broke it roughly once a week. Deleted the whole thing. The akuma.yml lives in the repo now, it reviews like real code, it diffs cleanly in pull requests, and nobody on the team fights it anymore.

I've tried Postman mocks, Prism, Mockoon, and a pile of hand-rolled Node servers over the years. Every one needed an OpenAPI spec I didn't have time to write, or fell over the moment I wanted persistence. Akuma is the first where the config is shorter than the thing it replaces, and it still gives me real tables, real IDs, and custom errors. I'm not going back.