THE ORISITE PLATFORM

From PHP source to an application you can operate.

A cloud hosting platform with its own panel, application runtimes, release history, and domain operations.

Your application is the starting point

Orisite is designed for PHP applications across frameworks. Choose a runtime that matches the application, build a versioned release, and manage its lifecycle without exposing server credentials to customers.

  1. LAYER 01

    Your workspace

    People, projects, and environments define ownership. A customer can work with application settings without receiving platform administrator access.

  2. LAYER 02

    The control plane

    Release requests, policy checks, domain intent, and audit records belong here. A request records what should happen; it is not proof that a node has performed it.

  3. LAYER 03

    The runtime node

    The execution boundary applies resource policy and reports what is running. Production activation requires a configured node and verified observations.

Bring the PHP application you already have

Compatibility starts with the application: its supported PHP version, extensions, document root, routing rules, background processes, and writable paths. Laravel and Symfony commonly serve a public directory; a WordPress installation has a different file and upload layout. Custom PHP is evaluated using the same requirements.

FrankenPHP is the preferred engine, while NGINX with PHP-FPM and Apache cover other runtime requirements. Worker mode is optional and needs an application lifecycle that safely resets request state. A conventional PHP application should not be described as worker-compatible without testing it.

Keep code releases separate from changing data

An immutable release contains application files and build output. Uploads, database contents, and other persistent state must survive replacement of that release. Declare the writable mounts and connection references before deploying.

A rollback can select an earlier application artifact. It cannot undo a destructive schema migration or recover deleted uploads. Plan backups, restoration, and database compatibility independently.

Shared infrastructure with application-level boundaries

The hosting model shares node capacity while assigning each application explicit CPU, memory, process, and storage policies. Customers use the Orisite panel; platform operations own the container runtime, node credentials, and infrastructure maintenance.

Serverless describes the intended deployment experience: customers focus on applications rather than administering servers. Automatic scaling, scale-to-zero, regional coverage, and production availability are not implied by that description and have not been published as service commitments.

Runtime compatibility
EngineApplication fitWhat to verifyAvailability
FrankenPHPPHP applications; worker mode when the application supports itValidate application lifecycle and long-lived worker behaviourPlanned
NGINX + PHP-FPMFastCGI PHP applications and static sitesConfigure document root, routing rules, and PHP-FPM limitsPlanned
ApachePHP or static applications with Apache-specific requirementsValidate modules, rewrite rules, and .htaccess behaviourPlanned
YOUR APPLICATION. YOUR WORKFLOW.

Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.