Furge / Isolated runtimes

A trading runtime of your own.

Every Furge user gets a separate server-side environment for execution strategies, bots and custom scripts. Your jobs run in your own daemon, with separate processes, private files and CPU and memory limits. Furge manages the infrastructure.

Open your workspace
Furge workspaceConfigure & monitor
Your isolated runtimeServer-side
Execution
strategies
Custom
scripts
Market-making
bots
Your connected exchange account
One runtime per user. Isolated software environments on shared hardware.
Isolated runtimes

What your runtime gives you.

01

Separate from other users

Your strategies do not run inside another user's daemon. Each account has its own container and runtime state, with boundaries around processes, files and resource usage.

02

Independent of your browser

The daemon is the background service that runs your trading jobs on the server. Once a job starts, closing a tab or disconnecting your laptop does not stop it.

03

Managed, not another server to maintain

Configure jobs in Furge rather than provisioning a VPS, installing dependencies and keeping a laptop awake. Inspect runtime status and logs from the same workspace.

Start trading. Not a server.

Read the documentation
  1. Connect an exchange account and authorize trading access.
  2. Configure an execution strategy or bot, or deploy a custom script.
  3. Monitor jobs, inspect events and stop runs from Furge. The server handles execution between visits.