Skip to main content
Figranium uses environment variables to configure key aspects of the server and automation environment. These variables are defined in src/server/constants.js.

Core Variables

Ports, sessions, IP restrictions, and proxy trust settings.

Execution

Concurrency limits and task queue behavior.

Rate Limiting

Login and data request rate limits.

VNC / Headful

noVNC port for headful browser debugging.

Feature Flags

Session cookie security and other toggles.

Browser Engine

CloakBrowser stealth engine configuration.

CAPTCHA Solving

Remote provider, local model, and Apple companionRemote endpoint and local model solver settings.

PostgreSQL

Postgres connection and SSL options.

Core Variables

Execution

When set, Figranium queues incoming execution requests that exceed the limit and processes them in order as slots free up. Leave unset (or set to 0) for unlimited concurrency. This is the default and matches the behavior of earlier versions. This is useful when running on resource-constrained hosts or when you want to prevent a burst of scheduled tasks from overwhelming the browser pool.

Rate Limiting

VNC / Headful Debugging

Feature Flags

Browser Engine

See Stealth & Anti-Detection for when to switch engines and what the CloakBrowser stack changes.

CAPTCHA Solving

See CAPTCHA Solving for the full feature reference, including the task-level auto-solve toggle and troubleshooting.

Database (PostgreSQL)

For production deployments, Neon is the recommended backend database provider due to its serverless autoscaling and zero-maintenance PostgreSQL infrastructure. See PostgreSQL Support for full details.

Example .env File

Notes

  • Allow Private Networks: By default, ALLOW_PRIVATE_NETWORKS is false, meaning Figranium blocks requests to private and internal network addresses. If you need to scrape services on your local network (e.g., during development), set this to true.
  • Session Secret: If SESSION_SECRET is not provided, Figranium will generate a random one on startup (or read from data/session_secret.txt if available). However, for consistent sessions across restarts, set a static secret.
  • Allowed IPs: If you expose Figranium to the internet, always restrict access using ALLOWED_IPS or authentication.