Internal panels and small SaaS
You need a real back office — users, roles, permissions, logs — and you’d rather spend the month on what makes your product different.
The PHP boilerplate · zero dependencies
Login, roles, permissions, security, billing — the boring part of any project, always the same. Now it all comes from one version-controlled codebase that stays up to date, and every new panel starts from there.
We build our own products. Every one of them started the same way: two weeks of authentication, permissions, password resets and a settings page, before writing a single line of the thing we actually wanted to build.
The alternatives always came with something attached: a library, a runtime, a build step, a license. A framework brings an upgrade treadmill that breaks things every twelve months. A SaaS starter kit means renting your own foundation. Few of them survive two years of server updates untouched, and the ones that do tend to be rigid.
So we created PHPFoundry: a PHP admin panel you upload and use. No Composer, no npm, no framework. It runs on the same cheap hosting your clients already have, and it keeps running when the server updates PHP without asking you.
Upload it to a shared hosting account and have it work. That’s the whole specification. No build step, no composer install, no exotic PHP extension. There is a CLI, and it makes updates and maintenance easier — but nothing needs it to get started.
Transactional email is where most starter kits send you back to Composer. Here it works out of the box — plain SMTP, or an API provider such as Resend — and you pick one in the settings screen, not in a config file. Every message is logged, so a password reset that never arrived is something you can look up instead of guess about.
The addon system is not an empty folder with a specification. Two addons come with it and run on the same panel:
Billing — customers, products, plans with their limits, and subscriptions. Directory — listings with custom fields, media, locations, ad slots and a public front end you can theme. Both are working code you can read, copy and bend into whatever your project needs.
Zero dependencies has a side effect we didn’t plan for: an assistant can read the whole thing. There is no framework magic to explain, no dependency injection container to reason about, no generated code. It’s PHP you can point at and change.
That matters more than it used to. Plenty of people building real products today are not full-time developers — they work with an AI and they need a codebase it can actually follow.
You need a real back office — users, roles, permissions, logs — and you’d rather spend the month on what makes your product different.
Every client asks for the same foundation and you rebuild it every time. Start from one codebase, keep what is specific to each client in an addon, and deploy on the hosting they already pay for.
Listings with their own fields, media, locations and ad slots, plus a public front end to theme. That addon is already written — you bring the data.
Features, documentation and pricing are at phpfoundry.com. It’s almost finished and isn’t on sale yet — the waitlist is open.
Go to phpfoundry.com →