QuillstackOne way to build an API, in the language you work in

The same rules, the same shape, the same discipline — written for each language rather than ported between them. PHP is here today. Python is being built to the same standard.

Build in PHP

Python

Browse the packages

GitHub

APIs, and nothing else

No templates, no view layer, no asset pipeline, no front-end integration. Everything here is for answering requests with data. A framework that does everything has to compromise somewhere, and this one would rather not do the everything.

The same rules in every language

What a package looks like — its README, its badges, its manifest, how it is released — is one file of rules, and seven of its nine sections are marked as belonging to no language in particular. A checker reads that file, so a rule cannot mean one thing in PHP and another in Python.

Nothing you did not ask for

Thirty-six packages, each usable on its own and none of them requiring the rest. Take the router without the ORM, or the HTTP client without any of it. In PHP the only third-party code in the whole stack is the PSR interfaces themselves.

Impossible rather than discouraged

The ORM batches relations by result set, so an N+1 query is not a mistake to avoid but a thing that cannot be written. A field reaches the wire because somebody said it may. A route says it needs authentication and one middleware enforces it.