Runs Independent From Your System

Overview

ForgeKit is designed to run completely independently from your system.

Everything lives inside a single folder, fully isolated from your machine. Your existing setup remains untouched. Nothing breaks, nothing gets overwritten, and nothing is modified globally.

Safe alongside your existing setup

ForgeKit can run side-by-side with tools like:

  • XAMPP
  • WAMP
  • Laragon
  • Custom local environments

There is no interference between ForgeKit and your current setup. You can keep everything you already use and try ForgeKit without risk.

Port usage

ForgeKit uses standard web ports to behave like a real server environment. The ForgeKit router listens on port 80 (HTTP)

Because of this:

  • Only one application can use port 80 at a time

If another tool (like XAMPP or WAMP) is running on port 80, Apache or Nginx or whatever is listening to port 80 must be stopped.

Running alongside other tools

ForgeKit can coexist with other environments, but not share the same ports simultaneously.

You can:

Stop XAMPP/WAMP Apache server → run ForgeKit

Stop ForgeKit → run your other tool

This ensures each environment runs cleanly without conflicts.

No system changes

ForgeKit does not modify your system:

  • No registry edits
  • No global PATH changes
  • No system-wide installs
  • No hidden background configuration

Everything ForgeKit uses is scoped to its own directory.

Fully self-contained

All ForgeKit components are stored within its installation folder:

  • /bin → installed runtimes (PHP, Apache/Nginx, MySQL/MariaDB)
  • /agent → golang agent .exes
  • /cli → golang cli tool
  • /certs → ssl certificates that ForgeKit auto generates
  • /instances → running servers and their configs
  • /sites → your project mappings
  • ForgeKit.yaml → configuration
  • ForgeKit.exe → application

Because of this:

  • You always know where everything is
  • Nothing is scattered across your system
  • Cleanup is simple and predictable

Easy to remove

Removing ForgeKit is straightforward:

  1. Stop any running instances
  2. Delete the ForgeKit folder

That's it. No leftover files, no cleanup scripts, no system impact.

Why this matters

Traditional local development tools often:

  • Modify system settings
  • Share global resources (like PHP versions)
  • Leave behind files after uninstall
  • Interfere with other environments

ForgeKit avoids all of this by design.

Summary

ForgeKit is built to be:

  • Safe to try
  • Easy to understand
  • Simple to remove

It runs independently, respects your system, and gives you full control.