Stop rebuilding the same platform.

PHP shared hosting and Node VPS from one codebase. React Builder, Platform SDK, Access, ZIP modules, and multi-site MCP — already wired. CMS is one surface. The platform is the product. Clone Core for the host (~15 modules). The 15 first-party domain packages live in a separate repo: github.com/iia3uk/Jasefly-Modules.

Open GitHub · Download install

I was tired of assembling the same stack.

Every new PHP product starts the same way. Pick a backend framework. Then an admin. Then a builder. Then ACL. Then updates. Then a package lifecycle. Then docs. Then AI glue. Weeks disappear into infrastructure — before the product exists. Jasefly exists because that platform was built once. Now the work is the product.

Why Jasefly?

A modern platform that stays honest about hosting: PHP on ordinary shared servers, Node when you want a VPS runtime — same contracts, same Builder, same MCP agent. Prebuilt React assets. ZIP updates. Quarantine for broken modules. A real Platform SDK. Multi-site MCP for controlled AI ops across several installs — not shell root.

Philosophy

Frameworks usually give you a backend. Jasefly gives you a platform — with two production runtimes. Admin, public site, builder, access, packages, updates, and AI tooling share one product surface. One Cursor agent can operate several hosts via MCP. This site is not a brochure. Where a surface exists, open it.

How is it different?

Different problem. Different shape of product.

Laravel / Symfony

Excellent backend frameworks

You assemble the product platform yourself

Admin, SPA, packages, deploy, ACL are your glue

You start from application code

Jasefly

A ready product platform

PHP + React + Builder already wired

Platform SDK, ZIP Runtime, Access, Modules, MCP

You extend a running system

WordPress optimizes for content. Jasefly optimizes for product architecture.

WordPress

Content-first

Plugins

Themes

Website management

Jasefly

Platform-first

SDK

Modules

Framework

Product architecture

Designed for

Where the platform fits without stretching the model.

Probably not for you if…

you only need a blog you only need WordPress themes you only want a bare API backend you do not need a platform That honesty saves everyone time.

Built in production

Two real hosts. No invented client logos. Open them — do not study a mockup.

Open a production site

Official product site or portfolio install — both run on Jasefly.

Open iia3uk.ru →

What you get as a developer

Open a live surface — not a slide.

Where to go next

Short public guides. Deep docs also live in the repo under docs/.

Independent by design.

Jasefly is built by one developer. No corporation behind it. No venture round. No marketing department. Decisions come from real production work — that is why the shape differs from popular PHP frameworks.

Open source

This project grows in public. Every feature starts as production code. Every release is visible. Every architectural decision is documented.

Open GitHub · Download install

Блог