Interactive PHP → Go compiler

Turn PHP projects into Go binaries without manual build chaos.

Upload a ZIP, inspect the project in a protected cloud terminal, run allowed php2go commands, and download a compiled binary with logs, manifest, and run instructions.

rocket_launchStart compiling play_circleView demo

Isolated workspaces Whitelisted commands only SaaS limits and billing

C:\php2go-cloud\demo

session=demo · worker=online · runtime=sealed

$ php2go report public/index.php

files=248 classes=91 functions=327 fallbacks=4

$ php2go compile --web --bin app-server public/index.php

stage=Analyze ok · stage=Codegen ok · stage=GoBuild ok

runtime linked · artifact sealed · limits charged

artifact ready: app-server-linux-amd64.zip

Binary + logsGo binary

Admin plansAdmin SaaS

Who it is for

For teams that need to package PHP into a clear deployable artifact.

php2go Cloud covers the path from ZIP archive to binary without local toolchain setup, command chaos, or manual limit accounting.

conversion_path

Legacy PHP

When old PHP code needs to move closer to a Go runtime or be checked for compatibility quickly.

terminal

Agencies and contractors

Upload the client archive, get the analysis log, run the build, and deliver a readable artifact.

deployed_code

DevOps and product teams

One build process, usage limits, job history, and reproducible commands.

What users get

Not just a compiler, but a managed build workflow.

ZIP

Safe upload

ZIP files are checked for dangerous paths, executable extensions, zip bombs, and unwanted files.

CLI

Cloud terminal

Users see allowed commands and can only run php2go scenarios.

BIN

Ready artifact

The output is a binary, build logs, and a clear run path without exposing server internals.

LOG

History and limits

Jobs, payments, invoices, usage, and plans stay visible in the admin area.

Demo terminal

Show value before registration and payment.

The public demo block simulates the real terminal: commands, analysis, worker queue, and a ready artifact. A fully interactive demo mode will be a separate next block.

php2go report public/index.phpphp2go check public/index.phpphp2go deps public/index.phpphp2go compile --web --bin app-server public/index.php

demo terminal

allowed commands loaded · archive=demo.zip

$ php2go check public/index.php

syntax ok · unsupported calls=0 · warnings=2

$ php2go compile --web --bin demo-server public/index.php

queued job #demo-1024 · worker picked

artifact manifest written · sha256 verified

download ready after registration

01Upload

The project ZIP lands in an isolated workspace.

02Analyze

Run report/check/deps before compiling.

03Compile

Commands pass whitelist and usage limits.

04Download

The compiled binary package is delivered as ZIP.

Security

The user does not get shell access. They get a controlled php2go console.

The SaaS must accept user code without allowing arbitrary execution. Commands, archives, logs, and artifacts are constrained separately.

ruleCommand whitelist

Only php2go commands needed for analysis and compilation are allowed.

folder_zipArchive checks

Protection against path traversal, zip bombs, dangerous extensions, and secret files.

receipt_longAction history

Job, payment, invoice, and admin activity history remains in the system.

Pricing

Plans for one-time builds and subscriptions

Sell one-time compilations, subscriptions, or custom plans from the admin panel.

monthly

Free

Free

2 Projects
300 units charged
32 MB ZIP

Choose plan

one_time

One Compile

$19

1 Projects
1000 units charged
256 MB ZIP

Choose plan

monthly

Starter

$29

10 Projects
3000 units charged
256 MB ZIP

Choose plan

monthly

Pro

$49

50 Projects
20000 units charged
512 MB ZIP

Choose plan

FAQ

Common questions before the first build

How should I prepare the ZIP?

Put the project sources into an archive so the entry point, for example public/index.php, is inside the ZIP. Vendor/runtime can be configured separately.

Can users run any command?

No. The terminal accepts only whitelisted php2go commands: report, check, deps, and compile.

What does the client receive after build?

A ZIP with the binary, logs, and run instructions. Runtime internals and server paths are not exposed.

Is it safe to upload third-party PHP code?

Archives are checked before extraction, commands are limited, and the runner has resource limits. Container isolation is recommended for production.

Ready to build the first project?

Upload a ZIP and get a controlled build instead of manual chaos.

Start with a free project or upgrade when you need higher limits.

rocket_launchStart compiling