Binaries and Runtimes

ForgeKit runs real Windows binaries — no containers, no virtualization.

A binary is a versioned runtime that ForgeKit can install, detect, and reuse.

Examples

  • PHP 8.3.x
  • Apache 2.4.x
  • Nginx
  • MySQL / MariaDB

All binaries can be installed, removed, or managed via:

Manage Binaries

Why ForgeKit uses “Binaries”

Most local dev tools blur versions together.

ForgeKit keeps them explicit.

That means:

  • Multiple PHP versions can run side-by-side
  • Each instance chooses its own runtime
  • Upgrading one project won’t break another

How binaries are used

Binaries are idle by default.

They only run when used by an instance:

  • A Web Instance uses a web server + PHP binary
  • A Database Instance uses a database binary

Where binaries live

All binaries are stored inside:

/bin

Each binary lives in its own folder.

⚠️ Important: One binary per folder

ForgeKit assumes:

One binary = one folder

Example:

/bin/apache-2.4.66
/bin/apache-2.4.67
/bin/php-8.3.7

Do NOT:

  • Put multiple versions inside the same folder
  • Change the internal structure of a binary folder after it’s been registered

This can cause:

  • Duplicate IDs
  • Config conflicts
  • Instances using the wrong binary

Adding your own binaries

You are not limited to ForgeKit’s built-in downloads.

You can add your own binaries manually.

Steps:

  1. Download your runtime (e.g. Apache, PHP)
  2. Extract it into the /bin folder
  3. Ensure it has a clear, unique folder name
  4. Open ForgeKit and click Reload Binaries

ForgeKit will attempt to detect and register it automatically. You should be able to see it in the Binary managemen window

Notes

  • Folder name is used to generate the binary ID
  • If two folders resolve to the same ID, conflicts may occur
  • Keeping clean and consistent folder naming helps avoid issues

Continue to → Instances