Binaries API for ForgeKit
and WAMP Dev Binaries Hub
for Windows
for your entire development workflow.
Built for ForgeKit.
Ready for everyone.
It was created by an enthusiastic ForgeKit user.
and WAMP Dev Binaries Hub
for Windows
for your entire development workflow.
Built for ForgeKit.
Ready for everyone.
It was created by an enthusiastic ForgeKit user.
Apps updated in the last 7 days
ForgeKit Custom Binaries API
First of all!
Download ForgeKit from https://forgekit.tools and then read.
Binary management in ForgeKit
ForgeKit uses a proprietary binary configuration maintained by the developer. Recently, support
for custom binaries has been added via the custom-binaries.json file, which users
can edit to define binaries that are not yet officially approved by ForgeKit but should generally
work correctly through the integrated manager.
Disclaimer
The binaries listed in the custom-binaries.json file are generated dynamically and are not tested for compatibility with ForgeKit, even though they represent updates of binaries that are already officially supported by ForgeKit.
The user acknowledges and accepts that using non‑official binaries may involve risks, including malfunctions, data loss, or damage to the installation.
ForgeKit API - custom-binaries.json
ForgeKit Custom Binaries
This section is for you, the ForgeKit user!
Go to ForgeKit > Manage Binaries > Custom Binaries.
Copy the API URL below by clicking on the clipboard icon, paste it into the external source field (the field under custom-binaries.json), and then select it.
Done! Now you can enjoy the possibility of installing the latest versions of ForgeKit base components: Apache, Nginx, PHP, MariaDB and MySQL (and more coming..).
ForgeKit Experimental Custom Binaries
ForgeKit vs others WAMP Stack for Windows
First of all!
Download ForgeKit from https://forgekit.tools and then read.
What is ForgeKit
ForgeKit is a Windows Local Development Environment (WAMP) designed to simplify PHP stacks management, similar to Laragon, XWAMP and other all‑in‑one tools.
Its key strength is the ability to run multiple web servers with different PHP and database configurations simultaneously, in isolated environments, without changing the system, without complex configuration and without conflicting with existing WAMP setups.
Why ForgeKit is the most advanced and modern WAMP stack for Windows in 2026
ForgeKit is not just another local PHP environment — it is a next-generation AMPP platform designed for developers who need speed, flexibility, and reliability. While traditional WAMP stacks like Laragon, XAMPP, WampServer, AMPPS, and UwAmp rely on single-server setups and manual switching, ForgeKit delivers a modern, isolated, multi-server architecture that transforms the way you work.
Key Advantages Over Other WAMP Stacks
- Run multiple PHP versions simultaneously — no switching, no downtime, no conflicts.
- Multiple web servers at the same time — Apache, Nginx, and more, each with its own configuration.
- Fully isolated environments — ForgeKit never modifies Windows, registry, PATH, or system services.
- Professional binary management — official catalogs, custom catalogs, safe updates, and legacy extension support.
- Zero conflicts with existing AMPP setups — ForgeKit runs cleanly alongside any other stack.
- Fast, frequent updates — continuous improvements, stability fixes, and new features.
- Modern interface and workflow — clean UI, instant logs, smart panels, and optimized database tools.
Built for Real Developers
ForgeKit is ideal for developers working on multiple projects, legacy applications, modern frameworks, or complex PHP stacks. It offers the power of Docker-like isolation without the complexity of containers — making it one of the most efficient and developer-friendly WAMP solutions available today.
Focus on
ForgeKit is the best WAMP stack for Windows because it provides simultaneous multi-PHP, multi-server support, isolated environments, safe binary management, and frequent updates — outperforming Laragon, XAMPP, WampServer, AMPPS, UwAmp, and Devilbox in flexibility, stability, and developer experience.
Comparing ForgeKit With Other WAMP Stacks
Choosing the right local development environment can dramatically impact productivity, stability, and project compatibility.
Traditional WAMP stacks like Laragon, XAMPP, WampServer, AMPPS, and UwAmp were built for single-server workflows and basic PHP hosting.
ForgeKit takes a completely different approach: it introduces a modern, isolated, multi-server architecture designed for real developers working on multiple projects, multiple PHP versions, and complex environments.
ForgeKit make the difference
Before diving into the detailed comparison, it’s important to understand what sets ForgeKit apart.
It is engineered to run multiple PHP versions simultaneously, manage independent web servers, isolate every project, and avoid system conflicts — all while providing a clean, fast, and frequently updated interface.
This makes ForgeKit a next-generation solution that goes far beyond the limitations of traditional WAMP stacks.
Warning: The data provided has been generated using artificial intelligence and may contain inaccuracies. If anyone has any comments or feedback, they can write to me using the email addresses shown at the bottom of the page.
Free & Almost‑Free WAMP Stacks — Comparison Table
Apps updated in the last 7 days
WAMP Binaries Hub
ForgeKit
ForgeKit - v.1.8.1 - Changelog2026-09-07Zoom, a resizable layout, and new privacy controlsNew Features
- Zoom: the app can now be zoomed with Ctrl and +/- (or Ctrl and scroll), with a zoom control in the title bar. Your zoom level is remembered.
- Sites: the sites sidebar can be dragged wider or narrower, and double-clicked to reset.
- Privacy: new privacy section where users can turn off anonymous usage or help us improve ForgeKit
Improved
- PHP: OPCache enabled by default for PHP now. It's free performance.
- phpMyAdmin: fixed "cannot prepare phpMyAdmin: ... Access is denied" on start/open for users whose config directory blocks file replacement (e.g. certain network drive permissions) - now falls back to a direct write if the atomic rename fails.
- Databases: new "Connection info" button next to phpMyAdmin, with copyable Laravel .env and WordPress wp-config.php blocks for that server.
- Agent status: the status dot no longer pulses to save cpu and battery while in background
- Status bar: Improved UI
- Messages: "no code editor selected" and "could not open a terminal" errors now carry an "Open Preferences" button that jumps straight to Preferred Apps.
- Window: the app can now be resized much smaller, both narrower and shorter, and the layout adapts instead of clipping.
- Footer: improved footer UI with new Contact and Support us links.
- Downloads: moved next to the other footer buttons, and stays usable while a modal is open.
- Aura Farming Box: opens in its own window now, so it shows a lot more and doesn't take up space in the main app.
- Preferences: the section list on the left now highlights and jumps to every section correctly on a tall window.
- New Contact and Support us links in the app
- General UI improvements throughout the app.
ForgeKit - v.1.8.0 - Changelog2026-07-25The CompletionistMailpit, Redis, Memcached, and a full sweep of UI improvementsNew Features
- Mail Servers: added support for Mailpit, a local SMTP catcher. Create one or more named inboxes and connect a web server's PHP mail() to any of them with a click. Nothing connects automatically.
- Mail Servers: each inbox shows ready-to-copy SMTP connection info (.env-style, with Laravel and Symfony examples) for apps that configure their own mail client.
- Mail Servers: a web server can be moved between inboxes at any time, and inboxes respect the LAN preference the same way web servers do.
- Cache Servers: new "Redis / Cache Servers" tab. Add, start/stop/restart, and remove Redis and Memcached instances the same way as web servers, databases, and mail servers.
- Cache Servers: each instance shows ready-to-copy connection info (.env-style, with a Laravel example) for both Redis and Memcached.
- Cache Servers: Redis gets its own redis.conf per instance, created once and never overwritten - open and edit it directly from the instance's Config menu (e.g. to turn persistence back on).
- Cache Servers: Redis versions offered are 7.0.15 and 8.8.1 (via redis-windows/redis-windows); Memcached is 1.6.8 (via jefyt/memcached-windows). Installed and managed through the existing Manage Binaries flow.
Improved
- Manage Binaries: fixed the list flickering/jumping while an install or removal is in progress.
- Error messages and toast notifications: text is now selectable, and a copy button was added, so you can grab the full message instead of only what's visible.
- Agent startup: fixed a race where forgekit-agent.exe would show a "port 80/443 already in use" warning for itself on launch.
- Agent widget: "Could not refresh status" and "Agent not running" no longer flash on normal startup or after an update. The widget shows a "Starting" state while the agent comes up instead of reporting an error.
- Agent widget: added a spinner for the "Starting" state. The port-in-use warning also now says when it's just a previous ForgeKit instance still shutting down (auto-resolves) versus another app you need to close yourself.
- Router landing page: added a search box above the site list once you have more than a handful of sites, and the list scrolls on its own instead of growing the whole page.
- Router landing page: added a Mail Servers section listing every Mailpit inbox with an open-inbox link (and a LAN link, when LAN access is on).
- Router: https://127.0.0.1/ no longer fails with a TLS error. The auto-issued localhost certificate now includes IP address SANs, and existing installs fix themselves automatically on next agent start.
- Router landing page: the site list no longer scrolls horizontally on narrow windows. Long folder paths, URLs, and domains wrap instead of overflowing.
- phpMyAdmin: fixed opening phpMyAdmin failing on a fresh install or new machine. First-time startup can take longer than the old 15s allowed (antivirus scanning php.exe for the first time is a common cause), so the timeout was raised and the modal now offers a "Try again" button instead of a dead end.
- PHP: gd is now enabled by default for new sites and for phpMyAdmin's runtime. It's only turned on when the matching DLL is actually present, so it can't break an install that doesn't ship it, and it works correctly on PHP 7.4 and earlier where the extension is named gd2.
- PHP: raised default limits for new sites so heavier scripts (image processing, API calls, larger imports/uploads) don't fail out of the box. memory_limit 128M to 512M, max_execution_time 30s to 300s, and date.timezone now defaults to UTC instead of being unset. Applied to both Apache and nginx sites; nginx sites previously got none of ForgeKit's PHP defaults.
- nginx: added client_max_body_size (50M) and fastcgi_read_timeout/fastcgi_send_timeout (300s) to site configs. nginx's own 1M upload cap and 60s timeout were overriding the more generous php.ini settings above before PHP ever saw the request.
- PHP: new PHP binaries and phpMyAdmin's runtime now get a CA certificate bundle out of the box, fixing "SSL certificate problem: unable to get local issuer certificate" on any outbound HTTPS call from PHP's cURL (Laravel's HTTP client, Guzzle, etc.). PHP's Windows builds don't ship one of their own. The bundle is refreshed automatically every time a new ForgeKit release is built, so it stays current without any runtime network dependency.
- Manage Binaries: opening the modal no longer waits on the custom catalog (a user-supplied JSON file or URL) to load - the official/local binaries list now appears immediately, with the Custom Binaries section loading separately and showing its own spinner. Switching between custom-binaries.json and a catalog URL also only refreshes that section instead of reloading the whole modal.
- fkit CLI: `fkit npm`/`node`/`npx`/`corepack`/`yarn`/`pnpm` now hand child processes a PATH prefixed with the site's own Node folder. Previously, `fkit npm install` itself always worked, but on a machine with no globally installed Node, any lifecycle/postinstall script that shelled out to `node`/`npm` by name could fail to find them (npm's own PATH-prepending safety net is off by default). This is scoped to the one process fkit spawns per invocation and never touches the parent terminal's real PATH.
- Preferred Apps: terminal picker now also detects Windows PowerShell, PowerShell 7, Command Prompt, WezTerm, Alacritty, and ConEmu/Cmder, not just Windows Terminal and Git Bash.
- Preferred Apps: code editor picker now also detects PhpStorm, WebStorm, Zed, GVim, and Neovim Qt. The logs/config editor picker can use any detected code editor too, not just Notepad++/Notepad.
- Preferred Apps: a manually picked .exe is recognized by filename too, so it still gets full support instead of a bare launch.
- Preferred Apps: WezTerm, Alacritty, and ConEmu now open with the user's own configured shell instead of always forcing PowerShell.
- Preferred Apps: fixed Windows PowerShell and Command Prompt opening a window that flashed shut immediately instead of staying open.
- Preferred Apps: fixed WezTerm not getting the site's PHP/Node on PATH at all.
- Preferred Apps: known limitation, not fixed - a shell profile that already defines its own php/node command (Laravel Herd does this) can still override ForgeKit's PATH in WezTerm.
- Preferred Apps: reverted registry/Scoop/Chocolatey/WinGet app detection and Alacritty/ConEmu's auto PHP/Node PATH, added earlier this cycle. Likely why Windows Defender started flagging ForgeKit as a false positive. Detection still works via PATH and each app's install folder.
- Add Instance: when a database, mail server, cache server, or web server has no matching binary installed yet, the modal now tries to send you straight to Manage Binaries instead of showing a form you can't submit. If an install is already running, it shows up inline as "Installing…" and becomes selectable the moment it finishes.
- Add Instance / Edit Label: UI Improvements by replacing the separate Preview/Name/Color fields with one row, an editable color pill for the name plus quick-pick swatches (blue, yellow, green, red, or a custom color).
- Switch PHP Version: a PHP version currently installing now shows up as "Installing…" instead of just not being there, and becomes selectable the moment it finishes.
- Node version dropdown (Add Site / Edit Site): same fix as above - a Node version currently installing shows inline and updates live once it's done.
- Manage Binaries: fixed the Custom Binaries section's loading spinner flickering on and off every second while any install was running anywhere in the app, not just in that section.
- Manage Binaries: title, back, and close buttons now stay pinned in place while the list scrolls instead of scrolling out of view; added a matching footer with the same actions.
- Add Site: typed-in fields (domain, folder, web server, Node version, HTTPS options) now survive a trip to Manage Binaries and back instead of resetting to blank.
- Add Site: auto-selects the web server when there's only one, instead of defaulting to "none" and confusing first-time users.
ForgeKit - v.1.7.1 - Changelog2026-07-21Clearer startup diagnostics and a smoother update experienceNew Features
- Installer: added an option (checked by default, also offered on every update) to install the latest Microsoft Visual C++ Runtime, needed by PHP and some other bundled tools
- Notifications: the message bar now pauses its auto-dismiss timer while your mouse is over it, and restarts the countdown once you move away, so it won't disappear before you've had a chance to read it or copy the message
Improved
- Startup errors: nginx, Apache, PHP, and MySQL/MariaDB now report the real reason when they fail to start (e.g. a missing Visual C++ runtime DLL) instead of a generic "did not come up in time" timeout
- Web servers: reduced the startup wait for nginx, Apache, and PHP from 15s to 10s
- Databases: reduced the startup wait for MySQL/MariaDB from 60s to 15s
- Updates modal: each version in "What's changed" can now show a title, subtitle, small image, and a "Read more" link, in addition to the New Features/Improved categories it already had
Notepad++
Visual Studio Code
VSCodium
Adminer
PHPMyAdmin
Git for Windows
Caddy Server
NGINX
Mailpit
Papercut-SMTP
Apache CouchDB
FirebirdSQL
MariaDB
MongoDB
Memcached
FrankenPHP
Memcached
PIE - PHP Installer for Extensions
Coding Fonts Hub
Only best Coding Fonts
This section is inspired by an old project of mine about Visual Studio Code Themes, and it uses a database I had specifically created to evaluate and suggest individual fonts.
The parameter I used to rate each font was its readability at 9/10px.
Over time —and with presbyopia— I reassessed all the fonts that weren’t readable at 10px but were perfectly readable at 12/14px.
For this reason, I won’t show ratings here, but keep in mind that any of these fonts could be the right one for writing code.
About Font downloads
Unlike the WAMP binaries, the fonts listed here do not have a direct download link; instead, they link directly to the developers’ websites or to a Google Search (indicated by the icon).
At the moment, this approach is necessary due to the wide variety of fonts included, and because it is not possible to find an API for each of them that provides a permanent link to the latest version.
From my own experience — in fact, while writing this text — I discovered that for about 30 fonts (which you won’t find on this list) the original websites no longer exist, even though the fonts are still available elsewhere.
I plan to retrieve updated URLs whenever possible. Through scripting, I aim to switch to direct download links at least for the fonts hosted on GitHub (specifically those with a GitHub versioning API), making the direct link visible right on the download button.
For now, I will simply highlight the fonts I like the most, the ones I have used most often, and those I still use today.
For each font, I have indicated specific properties to highlight their availability: ligatures, italic variant, slashed or dotted zero, bitmap font.
About this Project
Why WAMP Binaries Aggregator exists
I built WAMP Binaries Aggregator to dynamically generatecustom-binaries.json for ForgeKit, relying on official and public APIs whenever possible, or
using a scraper on download directories to read the URLs of individual components of the
development environment. See instructions on ForgeKit Custom Binaries API section.
About downloads and hosted content
This website is not a repository and does not host any files on its servers. It does not act as a mirror, nor does it store local copies of the listed packages.
All downloadable files are retrieved exclusively from the official websites of their respective projects. Download URLs are automatically collected through various public and documented APIs, which provide up-to-date information about available versions and the original links published by the developers.
The only files directly downloadable from this website are the custom-binaries.json libraries for ForgeKit, used to extend or customize it's binary management.
These files are generated dynamically based on data provided by official APIs and do not contain any software packages; they simply describe, in JSON format, the original sources and their available versions.
Our service therefore focuses on aggregating, organizing, and making this information accessible, ensuring that every download always comes from authentic sources, without any modification or redistribution of the content.
Operating notes
To avoid overloading upstream API providers and prevent service degradation, WAMP Binaries
Aggregator regenerates custom-binaries.json only after a minimum time interval has
passed since the previous generation. The API exposed by this site behaves the same way: it
serves the already generated file until the configured regeneration time expires.
The expiration time is not uniform: it is set server to server.
This can cause a slight delay between the moment new binaries are published by the upstream APIs and the moment they become available through WAMP Binaries Aggregator, but it ensures stability and reliability for both this service and the external providers.