Blueprint · PHP Container Worker

PHP Container Worker Starter (work-php-minimal)

Minimal PHP worker that responds with 'hello from php worker' on every invoke. Bring PHP workloads, agency client backends, and commerce integrations onto the Software Lifecycle Cloud with declarative infrastructure in stack.json.

Container Workers NoSQL Tables Object Buckets

Talk to us Read Technical Documentation → Software Lifecycle Cloud →

One-Command CLI Initialization

CLI Command work-php-minimal

kernstack add worker --name php-app --blueprint work-php-minimal

Modern lifecycle cloud ergonomics for PHP teams and agencies

Across Europe, thousands of digital agencies and mid-market companies run critical commerce, portal, and ERP glue in PHP. Historically, modernizing those systems meant either managing raw Linux VPS fleets or rewriting everything in Node.js.

The work-php-minimal blueprint brings PHP into the same stack.json lifecycle as Go, Python, and Node.js — complete with preview environments, AI search, and agent collaboration.

Managed PHP worker runtime with zero server patching or PHP-FPM tuning
Access KERNSTACK Tables, Buckets, Search, and Workflows via the PHP SDK
Combine PHP workers with Go functions and Python AI workers in one stack

Gradual modernization without a rewrite

Keep proven PHP business logic running in a worker while adding vector search, image moderation, or human-approval workflows alongside it in stack.json.

PHP workers for teams that are not rewriting

work-php-minimal lets an agency or a commerce team keep PHP for the request path they already know. Composer dependencies install at build. The worker still uses the project tables and buckets, so a Go function and a PHP worker can read the same invoice row without a sync job between two vendors.

Studios use this blueprint when a client hands over an existing PHP module. The module moves behind a gateway route, gains a plan diff, and stops needing its own VPS. Human approval workflows stay available for the steps the client still wants to sign.

Starter Code — work-php-minimal php

<?php

require_once __DIR__ . '/kernstack_sdk/autoload.php';

use Kernstack\Workers\WorkerInvokeResponse;
use function Kernstack\Workers\run;

run(function ($req) {
    return new WorkerInvokeResponse([
        'body' => 'hello from php worker',
        'statusCode' => 200,
        'headers' => ['Content-Type' => 'text/plain'],
    ]);
});

stack.json — work-php-minimal plan · deploy

{
  "stack": { "target": "commerce.prod" },
  "gateway": {
    "routes": [
      {
        "name": "web-php",
        "type": "http",
        "target": { "kind": "worker", "name": "php-app" }
      }
    ]
  },
  "resources": {
    "workers": [
      { "name": "php-app", "runtime": "php" }
    ],
    "tables": [
      { "name": "orders", "key_name": "id", "key_type": "string" }
    ]
  }
}

FAQ

Frequently asked questions

Why does KERNSTACK support PHP alongside Go, Node.js, and Python?

European product teams and agencies frequently maintain PHP codebases or commerce connectors. Supporting PHP natively lets them adopt the Software Lifecycle Cloud without forced rewrites.

Can a PHP worker share Tables and Buckets with Python or Go services?

Yes. All runtimes in a project share the same declared Tables, Buckets, Search indexes, and Workflows.

How do I deploy changes to a PHP worker?

Run kernstack plan to inspect the diff and kernstack deploy to build and roll out the updated worker.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →