GODsend PS4
GOLDHEN PLAYSTATION 4

Your PS4,
on your desktop.

Connect over FTP, see what is installed, stream a package straight into the console's installer, drive it with a virtual DualShock 4, and keep saves and conversions in the same window. Same Rust and Tauri stack as GODsend PSP.

GoldHEN FTP Remote package install Virtual DualShock 4 macOS, Windows, Linux

Download

GoFile is the primary mirror, file.kiwi is the encrypted backup. Links refresh weekly.

BuildGoFilefile.kiwiSize
Fetching the current build...
Installed library grid with icons, versions and package state Virtual DualShock 4 with d-pad, sticks and triggers Console dashboard with FTP, installer and pad status Console list with ports, test and discovery Two pane local and console file manager Homebrew catalog with release assets

Everything in one window

The parts of managing a GoldHEN PS4 that usually need three tools and an FTP client.

Console status

FTP latency and banner, installer and pad reachability, installed title and package counts, all probed from the real ports.

Library

Installed titles from appmeta with icons, ids and versions. Patches and DLC stay out of the grid; packages waiting in /user/pkg have their own tab.

Remote install

GoldHEN takes a URL, so the app serves the PKG over a one-shot HTTP server and lets the console pull it, resume support included. A 40 GB title is never copied twice.

Virtual DualShock 4

Buttons, triggers, both sticks, PS, share, options and touchpad click, in up to four slots, with keyboard mapping.

Payloads

Send a .bin or .elf over the bin loader on 9090 from the Console page or the CLI.

Saves

List save folders, zip them into the download folder, restore them, delete with a confirmation.

Conversions

Unpack a PKG to a folder with PFS decryption, split for FAT32, merge a split set.

Files

Two panes, local and console, with tree upload and download and FAT32 splitting on the way to USB.

A real pad, not a remote screen

Input travels over a WebRTC data channel to the Control4Free payload.

The payload opens port 4264 and refuses any request whose Origin is not its own or null, so the offer exchange runs in Rust while the app's webview owns the peer connection. Input goes out at 60 Hz, which also repairs a release lost in transit.

An MCP server that starts with the app

Let an agent drive the console with the same tools you use.

While GODsend PS4 is open it serves the Model Context Protocol on loopback (default http://127.0.0.1:8744/mcp). Tools cover status, library, install, payloads, files, conversions, saves, search, homebrew and the pad service.

claude mcp add --transport http godsend-ps4 http://127.0.0.1:8744/mcp

There is also a stdio binary for clients that spawn their own server: godsend-ps4-mcp.

Build

cargo test --workspace
npm --prefix app install
npm --prefix app run build
npm --prefix app run tauri build

The CLI: cargo build --release -p godsend-ps4-cli, then godsend-ps4 help.

Requirements

NeedWhy
GoldHEN with FTP on 2121Every file operation.
Remote package installer on 12800Installs. Without it the app uploads to /user/pkg instead.
Control4Free on 4264The virtual controller. Install it from the Homebrew page.
aria2c (optional)16-connection downloads; without it downloads use one connection.
Real-Debrid or TorBox keys (optional)Resolve debrid links. Internet Archive needs neither.
GameSearch backend (optional)Link resolution for the game index. Browsing works against the public site.

Guides

Connect your PS4 Install games and homebrew Use the virtual controller Back up saves Convert and split Troubleshooting