🗄️
Staff only.
Internal tool hosting
Nobody outside the company will ever see it. Everybody inside depends on it.
Built with
Built by
Features
Benefits
Solutions
The application only a company's own staff uses: an admin panel, an intranet, a stock or logistics tool. PHP holds an enormous share of these, because they were written quickly by whoever was available, and PHP was what was available.
Low traffic, high consequence
20 concurrent users at peak, nothing on weekends. By every metric a hosting dashboard reports, the application looks idle. When it stops, invoices aren't raised and shipments aren't booked, and the manual fallback was forgotten years ago.
Load-based reasoning gives the wrong answer here. The PHP component and the database run through the working day whether or not anyone logs in, and that, plus backups, is the bill. A framework version or three behind is fine; an end-of-life PHP runtime is not.
Access control is the application's job
There's no VPN and no private networking here, and that's worth saying plainly: an internal tool is reachable over the public internet like anything else. The platform offers two coarse gates — the password protection setting puts HTTP basic auth in front of the whole environment, and .htaccess rules can pin access to known office IPs.
An IP gate breaks the moment staff work from home or from a phone in a warehouse aisle, and basic auth is one shared credential. The boundary that survives reality lives in the code: sessions that expire, roles checked on every action, a second factor for accounts that can move money.
Trust
An honest account.
