FuseCP is a complete, open-source control panel for Cloud Computing Companies and IT Providers. It lets you provision and manage a full suite of hosted services across your infrastructure from a single web-based administration portal.

FuseCP is the successor to SolidCP. It is free, open source, and actively developed.

Website & downloads: www.fusecp.com

FuseCP uses a multi-tenant model, meaning one installation can serve multiple resellers and their end customers, each with their own isolated service quotas and hosting plans.

Download the latest release installer from www.fusecp.com or the Releases page.

The installer sets up three components on your Windows Server:

All three can run on the same machine for small deployments, or be split across servers for larger environments.

• Operating system: Windows Server 2016 / 2019 / 2022 / 2025
• Database: SQL Server (Express or full), MySQL, MariaDB
• .NET: .NET Framework 4.8 (current release) — .NET 10 support in progress

After installation, open the FuseCP Portal URL in a browser. Log in with the administrator account created during setup.

From the portal you can:

1. Add servers — register your managed hosts under Server → Servers
2. Create hosting plans — define resource quotas under System → Hosting Plans
3. Add resellers and customers — provision accounts under Account Management
4. Provision services — assign web, mail, database, and other services to customer packages

Full administration documentation is available at www.fusecp.com.

FuseCP is a direct successor to SolidCP and maintains database and configuration compatibility. The upgrade path is covered in the installation documentation on www.fusecp.com.

• Website: www.fusecp.com
• Issues: GitHub Issues
• Security vulnerabilities: see SECURITY.md for responsible disclosure

If you want to build FuseCP from source, contribute code, or understand the internal architecture, see:

FuseCP is released under the GNU General Public License v3. See LICENSE for details.

• Code of Conduct
• Security Policy
• Contributing Guide

FuseCP is organized into three primary layers:

Source code is under FuseCP/Sources/. Build and deployment scripts are under FuseCP/ and tools/.

First-time full setup (elevated PowerShell):

powershell -File FuseCP/Tools/bootstrap-test-environment.ps1 `
  -Install -RunAllProfiles -InstallSqlExpress -InstallIIS -InstallWsl -InstallWixToolset

Check prerequisites only:

pwsh -File FuseCP/Tools/check-test-environment.ps1 -Profile Unit

git clone https://github.com/FuseCP/FuseCP.git
git submodule update --init --recursive

pwsh -File FuseCP/Tools/Start-Of-Day.ps1

# Full orchestrated build
FuseCP/build-debug.bat

# Or via the scripted validation entrypoint (recommended for CI-like local checks)
pwsh -File FuseCP/Tools/run-local-validation.ps1

pwsh -File FuseCP/Tools/run-local-validation.ps1 -ChangedOnly -SkipIfNoChanges -DisableNuGetAudit

FuseCP/deploy-debug.bat

Run the VS Code task Done for today or:

pwsh -File FuseCP/Tools/Done-For-Today.ps1

FuseCP/                         Build, deploy, and tooling scripts
  Sources/                      All C# / VB source code
    FuseCP.WebPortal/           Portal ASP.NET project
      App_Themes/Default/Styles/  LESS + compiled CSS theme files
    FuseCP.EnterpriseServer/    Business logic layer
    FuseCP.EnterpriseServer.Data/  EF database layer (Entities, Migrations, Config)
    FuseCP.Server/              Server agent project
  Database/                     SQL install and update scripts
  Tools/                        PowerShell dev and CI tooling scripts
  Bin/                          Shared compiled output
FuseCP.Installer/               Legacy MSI installer (.vdproj)
FuseCP.WebSite/                 Standalone website package
Languages/                      Localization resource files
tools/                          Third-party build tools (WiX, 7-Zip, etc.)
artifacts/                      Local build and session artifacts (gitignored)

All portal styling is authored in LESS source files — never edit main.css directly.

Recompile after editing any .less file:

cd FuseCP/Sources/FuseCP.WebPortal/App_Themes/Default/Styles
npm run build:css

Commit both the .less source and the recompiled main.css together.

FuseCP uses EF Core 8 on .NET 10 and EF 6 on .NET Framework, with a single shared DbContext in FuseCP.EnterpriseServer.Data.

1. Edit Entity class(es) in FuseCP/Sources/FuseCP.EnterpriseServer.Data/Entities/.

2. Update Fluent API configuration in Configuration/ for cross-DB type mapping if needed.

3. Create a migration:

   cd FuseCP/Sources/FuseCP.EnterpriseServer.Data
   MigrationAdd.bat

4. Review the generated files under Migrations/.

5. Also update FuseCP/Database/update_db.sql to keep the legacy SQL path in sync.

When code includes new entities/tables (for example IpSecurityPolicies), update your local DB before running the portal/server.

1. Open PowerShell in repository root.
2. Change directory to the EF data project.
3. Run dotnet ef database update with the provider/connection you use locally.

Your local database name and credentials are in FuseCP/Sources/FuseCP.WebPortal/Web.config under the <connectionStrings> section:

<add name="EnterpriseServer"
     connectionString="DbType=SqlServer;Server=(local);Database=YOUR_DB;uid=YOUR_USER;pwd=YOUR_PASSWORD;TrustServerCertificate=true"
     providerName="System.Data.EntityClient" />

Use those values (database name, uid, pwd) in the commands below.

Set-Location "FuseCP/Sources/FuseCP.EnterpriseServer.Data"
dotnet ef database update --framework net10.0 --context SqlServerDbContext -- "DbType=SqlServer;Server=(local);Initial Catalog=YOUR_DB;Integrated Security=True;TrustServerCertificate=true"

Set-Location "FuseCP/Sources/FuseCP.EnterpriseServer.Data"
dotnet ef database update --framework net10.0 --context SqlServerDbContext -- "DbType=SqlServer;Server=(local);Initial Catalog=YOUR_DB;Uid=YOUR_USER;Pwd=YOUR_PASSWORD;TrustServerCertificate=true"

Replace YOUR_DB, YOUR_USER, and YOUR_PASSWORD with the values from your Web.config.

Set-Location "FuseCP/Sources/FuseCP.EnterpriseServer.Data"
dotnet ef migrations list --framework net10.0 --context SqlServerDbContext -- "DbType=SqlServer;Server=(local);Initial Catalog=YOUR_DB;Integrated Security=True;TrustServerCertificate=true"

If update fails with a login error, switch authentication mode (Integrated Security vs SQL login) and retry with credentials that can modify schema in the target database.

For scaffolding from an existing database or porting raw SQL changes, see the full guide in FuseCP/Sources/FuseCP.EnterpriseServer.Data/README.md.

Never edit EF model snapshot (.cs) files by hand — always let dotnet ef maintain them.

# Broadest (full build, all scopes)
pwsh -File FuseCP/Tools/run-local-validation.ps1

# Changed files only
pwsh -File FuseCP/Tools/run-local-validation.ps1 -ChangedOnly -SkipIfNoChanges

# Scoped (Portal, Enterprise, or Server)
pwsh -File FuseCP/Tools/run-local-validation.ps1 -Scope Portal

# After initial restore (skip restore for speed)
pwsh -File FuseCP/Tools/run-local-validation.ps1 -Scope Enterprise -NoRestore

# Machine-readable output for PR tooling
pwsh -File FuseCP/Tools/run-local-validation.ps1 -ChangedOnly -JsonOutputPath artifacts/validation/summary.json

In scoped mode, Portal already builds FuseCP.WebPortalAndEnterpriseServer.sln; selecting both Portal and Enterprise does not run a redundant extra build.