Skip to content

MiniApps Platform: many small apps on one PHP engine

A company rarely needs one big application. It needs a dozen small ones: a booking form, a price calculator, a partner portal, an internal dashboard. MiniApps Platform runs them on a single PHP engine instead of a dozen WordPress installs.

One engine, separate apps

Mini-apps run on Atomic Framework: authentication with Telegram Login, queues, CLI tooling and WebSocket support come from the framework, and the application template gives a new app a working skeleton on day one. Each mini-app keeps its own routes, templates and data.

That split matters during maintenance. An update to the engine reaches every app at once; an app release touches only its own folder. No plugin conflicts between two products that never should have shared a database.

SEO and security per app

Mini-apps are pages too, and each one needs a title, a description, a canonical and the right schema. The SEO module covers metadata, sitemaps and language versions, so an app published next month is indexable on day one.

Security headers ship as configuration, not as an afterthought: HSTS, X-Frame-Options, X-Content-Type-Options, Content-Security-Policy and Referrer-Policy are set per app. A partner portal gets a stricter policy than a public calculator.

Why not one monolith

A monolith starts fast and ends slow. The tenth feature adds a condition to the tenth shared file, and every release risks the whole surface. Separate apps on a shared engine keep the blast radius small.

The cost is discipline: a contract for shared services, a versioning rule for the engine, and a deployment that can ship one app without touching the rest.

Where it fits

Internal tools for a distributed team, customer-facing calculators, partner portals, booking flows, small SaaS products with a narrow feature set. Each is too small for a platform team, and too important to live in a spreadsheet.

Related: business automation for the process side, WordPress development when the app should live in the existing site.