Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

76 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Fracture

Release Stars Issues License

English | فارسی

Fracture is a Windows desktop control panel designed for easy management of sing-box profiles, local proxy runtime, and Cloudflare listener settings.

It brings the full workflow into one app, with profile import, runtime control, diagnostics, and local configuration stored safely on your machine.

Screenshots

Home Profiles

Settings Logs


What Fracture Does

  • Import proxy profiles from subscription links, URI strings, or text files
  • Organize profiles with rename, reorder, export, delete, and active-profile selection
  • Run ping and speed tests before connecting to verify performance
  • Edit Cloudflare listener JSON directly inside the UI
  • Control local runtime status, proxy ports, routing mode, LAN sharing, and startup behavior
  • Monitor live status, logs, egress information, and traffic counters in real time

Supported Profile Types

Fracture supports the profile formats used by its parser and runtime pipeline, including:

  • vless://
  • vmess://
  • trojan://
  • ss://
  • socks://
  • http://
  • hysteria2://
  • tuic://
  • wireguard://
  • naive+https://
  • naive+quic://
  • anytls://

Quick Start

  1. Open Fracture.
  2. Import or paste your profiles.
  3. Optionally run ping or speed tests.
  4. Select an active profile.
  5. Start the runtime from the Dashboard.

Project Structure

  • apps/desktop — Tauri + React desktop application
  • apps/backend — FastAPI service for profile storage, runtime control, and realtime updates
  • sing-box/ — bundled sing-box runtime assets and helper files
  • configs/ — generated runtime folders and log output
  • data/ — local settings, profile storage, and Cloudflare listener state

Local Data

Fracture stores runtime state and configuration locally in files such as:

  • data/profiles.json
  • data/cloudflare-config.json
  • data/app-settings.json
  • configs/

These files remain on the local machine and are not shared by default.

Development

Run the backend and desktop app together during development:

npm run run

Build a packaged release for distribution:

npm run build:release

Prepare the next GitHub release from the latest v* tag:

npm run release:prepare

That command:

  • infers the next semantic version from commits since the latest version tag
  • updates the app version across the tracked manifest/config files
  • creates .github/releases/<version>.md as the curated release notes file
  • creates .release-tmp/release-notes-input-<version>.md with a hardcoded AI prompt, commit history, and full diff context

After you paste the final release notes into the generated .github/releases/<version>.md, finalize and publish:

npm run release:finalize

That command creates the release commit, tags v<version>, pushes the branch and tag, and lets the GitHub release workflow publish the release assets.

Support And References

Donation Wallets to Support the Developer:

  • TON: UQATECPeh89wITfWeFkUuO0o30Gup5QhmDlx9KWYNz54VCjN
  • USDT TRC20: TF24QUZmpznKqrnjN6GhawW45Nx1DBALtR
  • TRX TRC20: TF24QUZmpznKqrnjN6GhawW45Nx1DBALtR
  • SOL Solana: 5dGZcqQGECrczAtqfhrMn4A8VHLKR3qNx5Jaq8vAamyr

Acknowledgements

Fracture builds on ideas and open-source work from the community.

License

This project is licensed under the terms of the LICENSE file.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages