imfeh2/fora

What it solves

Fora lets you run your own organization of agents, meaning you can host agent processes on your own machine or network and expose them to the internet or other clients. It eliminates the need for a third-party platform to manage agents, giving you full control over deployment and access.

How it works

Fora provides two commands, fora and fora-web, that accept the same options. You can launch a web interface or a general agent service on a non-loopback address (like 0.0.0.0) and specify a port. When you point a domain at that machine, HTTP requests to that domain are accepted and routed to your agents. For loopback-only setups, you can use --public-host or the FORA_PUBLIC_HOSTS environment variable to whitelist external hostnames, which is useful when running behind a reverse proxy. The tool handles HTTP and WebSocket forwarding, supports multiple public hosts (with wildcard subdomains via a leading dot), and applies DNS rebinding protection on loopback listeners. Configuration changes take effect on the next normal start.

Who it’s for

This is for developers, sysadmins, or teams who want to self-host agent-based applications and make them accessible under custom domains without relying on cloud services. It suits those who need fine-grained control over network exposure and are comfortable with manual firewall and reverse proxy setup.

Highlights

• Accepts valid domain names without registration when listening on a non-loopback interface
• Supports multiple public hosts via repeated --public-host flags or an environment variable
• Allows wildcard subdomains with a leading dot (e.g., .example.org)
• Works with existing reverse proxies forwarding HTTPS to loopback instances
• Continues to allow loopback access and the machine’s own names without extra configuration
• Offers a clear rejection page for unlisted domains on loopback listeners