PHP → Go binary delivery for real projects
PHP projectas a Go binary.
Upload a PHP project, get compatibility diagnostics, watch live build logs, and download a clean run package: binary, manifest, checksums, and deploy instructions.
✓ Sealed artifact✓ Deploy-ready✓ PHP / Composer / MVC
$ php2go compile --web public/index.php
[10:42:01] Validating project archive...
✓ project analyzed
[10:42:03] Resolving Composer autoload...
✓ dependencies resolved
! 3 compatibility notes VIEW REPORT
◆ app-server 24.8 MB▤ manifest.json 2.1 KB≡ README_RUN.md 4.8 KB# SHA256SUMS 0.6 KB
Problem
The PHP project works.|Shipping it cleanly is the hard part.
A working PHP project often depends on dozens of small details: autoload, extensions, include paths, permissions, env, and web-server settings. Until it is moved, nobody knows where delivery breaks.
Too much gets shipped
Sources, vendor, and configs travel to places that only need a runnable package.
Server must be recreated
Extensions, PHP-FPM, permissions, nginx, systemd, and environment variables are rebuilt by hand for each setup.
No clean output
A client or server gets a project folder and a pile of manual instructions instead of a clean runnable result.
How it works
A clear path from PHP archive|to runnable package.
The whole path is visible: from input archive and diagnostics to a result that can be verified, handed off, and deployed.
ZIP
A normal project ZIP: entrypoint, sources, and dependencies needed for the build.
Analyze
We check structure, autoload, dependencies, and the start file.
Compile
php2go generates Go code, builds the binary, and writes detailed logs.
Seal
The final package is checked so extra working files are not shipped.
Download
Download a package with binary, manifest, SHA256SUMS, and run instructions.
Deploy
Run the result as a backend and use nginx/systemd examples as deployment starters.
Features
Not just compile.|A proper delivery workflow.
The service covers not only compilation, but the boring work around it: diagnostics, history, package validation, and result handoff.
php2go reportClear compatibility signal
Diagnostics show what blocks the build: dynamic code, extensions, vendor packages, include paths, or unsupported functions.
- ✓project analyzed
- ✓dependencies resolved
- ✓binary built
PASS Composer autoload detected
PASS 184 / 186 classes resolved
NOTE src/Legacy/Router.php:81
NOTE ext/imagick not available
INFO php2go deps --missingOutput control
Ship the result,|not the working directory.
The final output is checked as a delivery package: executable, instructions, manifest, checksums, and deploy examples. Extra working files should stay out of the downloadable archive.
- ✓Manifest + checksums
- ✓Deploy files included
- ✓Download validator
- ✓README_RUN + .env
◆app-serverExecutable · 24.8 MB✓
▤manifest.jsonBuild metadata · 2.1 KB✓
▤README_RUN.mdLaunch guide · 4.8 KB✓
▤SHA256SUMSIntegrity · 0.6 KB✓
▰deploy/nginx + systemd✓
▤.env.exampleConfiguration template✓
Use cases
For teams that want to keep PHP|and improve delivery.
The service helps when PHP code already brings value, but deployment, client handoff, or compatibility checks take too much manual time.
Legacy PHP
Get a problem map before rewriting: what already builds and what needs attention.
Agency
Show the client a clear result: what was uploaded, what was built, how to run it, and how to verify it.
SaaS / closed product
Keep versions, logs, and packages recorded so backend delivery is repeatable.
Bitrix / MVC / Composer
Test real MVC/Composer projects with autoload, configs, and dynamic code.
Live build without SSH access
Users see the process.|The system hides the machinery.
The interface shows the useful parts: project, command, status, logs, and final package. Internal routing and operational details stay out of the public side.
● project and limits controlled● build writes live logs● results linked to the job
php2govalidation and queue→build stepanalysis and build→artifact.ziprun package
✓ archive checked, job created ✓ status and logs update in dashboard ✓ package validated and ready to download
Pricing
Start free.|Pay when you need a build.
First, test a real project and the quality of diagnostics. Paid scenarios make sense when builds become part of your workflow.
Free
Freefor trying the service
- ✓1 projects
- ✓ZIP up to 1 MB
- ✓10 MB storage
One Compile
$19one-time payment
- ✓1 successful compile
- ✓1 projects
- ✓ZIP up to 256 MB
- ✓1024 MB storage
Starter
$29per month
- ✓10 projects
- ✓ZIP up to 256 MB
- ✓4096 MB storage
Pro
$49per month
- ✓50 projects
- ✓ZIP up to 512 MB
- ✓20480 MB storage
FAQ
Questions|before the first build
No magic promises: the result depends on code, dependencies, extensions, and dynamic patterns. The point is that logs make the next step visible.
Do I need to rewrite PHP code?+
No. The goal of php2go is to compile existing PHP code. Compatibility depends on extensions, dynamic patterns, vendor packages, and runtime functions.
Can Composer projects be compiled?+
Yes, the service is designed for real PHP projects with dependencies. Complex packages may require compatibility work or diagnostics.
What do I get after a build?+
An archive with the binary, README_RUN.md, manifest.json, SHA256SUMS, .env.example, and nginx/systemd deploy files.
Does it replace PHP-FPM?+
For a successfully compiled web project, the binary can run as a standalone backend behind nginx, without PHP-FPM in production.
Will sources be included in the downloaded archive?+
The production package is meant to ship a runnable result and instructions, not the project working directory. The archive is validated before download.
What is an entrypoint?+
It is the starting PHP file of the project, for example public/index.php. Analysis and web-binary build start from it.
Do I need to upload vendor?+
Usually the project is uploaded with prepared dependencies or a structure the service can understand. Composer classes must be available to the build.
What about PHP extensions?+
Not every extension or non-standard function is supported equally. Build logs point to the exact place where runtime compatibility, project configuration, or code changes are needed.
Does this fully protect the code?+
No honest tool can promise absolute protection. But a checked binary package reduces the chance of accidentally shipping sources, temporary files, or extra working data.
Will it make the project 100x faster?+
No such promise. The goal is to produce a standalone Go binary and a clean delivery package. Performance depends on the code and runtime paths.
What if the build fails?+
Review the job log, report/check/deps output, and the first fatal diagnostic. It usually includes stage, file, line, and the likely direction: project code, dependencies, or compiler limitation.
How do I run the result on a server?+
The artifact includes README_RUN.md, nginx config example, systemd service, and .env.example. Use them as a production deployment base.
Ready for the first build?
Check how ready your PHP is|for binary delivery.
Start with a real project: upload a ZIP, choose the entrypoint, and see what is already build-ready and what needs attention.
✓ ZIP + entrypoint✓ compatibility report✓ ready-to-run artifact
Demo terminal
Try the command before signing up
Open the demo terminal and see the build scenario: command, statuses, sealing, and archive preparation.
$ php2go compile --web public/index.php ✓ project analyzed ✓ dependencies resolved ! 3 compatibility notes → generating Go packages... █