pype — starter app

A lightweight, pipeline-first PHP framework. Every route is its own pipeline: a request goes in one end, passes through the stages you list, and comes out as data — JSON by default, or HTML through a view.

Request ─▶ [global stages] ─▶ route ─▶ [group + route stages] ─▶ Response ─▶ Outlet ─▶ output

Quick start

composer create-project pype/pype my-app
cd my-app
php bin/pype serve        # http://localhost:8000

create-project copies this app, installs pype/framework into vendor/, creates .env with a fresh APP_KEY, runs the migrations, and then asks two questions:

• Templates: plain PHP (no package), Latte, Blade (BladeOne), or both. Mix them freely later: the file extension picks the engine.
• Faker: for fake data in factories and seeders (the built-in Fake works without it).

Change your mind any time with php bin/pype install. In CI or scripts, answer with flags: php bin/pype install --template=latte --faker (or --no-interaction for neither).

php bin/pype routes            # every route and its stages
php bin/pype make:stage Name   # app/Stages/Name.php
php bin/pype make:migration create_posts_table
php bin/pype migrate
composer test

The guide

Everything pype offers, with examples (routes, stages, validation, auth and JWT, mail, cache, queue, schedule, database, factories and seeders, testing, production...) is in the framework's guide: vendor/pype/framework/docs/GUIDE.md in your app, or on GitHub.

Working with an AI assistant? AGENTS.md holds the rules for building on pype (the shape of a feature, what not to do, the built-ins); CLAUDE.md imports it for Claude Code, and other agents read AGENTS.md directly.

Layout

app/          your code: Stages (every step of a route), Views (page outlets), Outlets (JSON outlets), Data, Mail, Providers
bootstrap/    builds the Application
config/       plain PHP arrays (app, auth, database, session)
database/     migrations/*.php and the SQLite file
public/       web root (index.php, css/)
resources/    views/
routes/       web.php (pages, sessions) and api.php (JSON under /api, tokens); every file loads,
              so feature folders work too: routes/quotes/web.php, routes/quotes/api.php
tests/        PHPUnit feature tests (Pype\Testing\TestClient, in-memory SQLite)
bin/pype      CLI
vendor/       pype/framework lives here