FlowForge

What does FlowForge do?

FlowForge describes itself as "Open-source workflow automation and AI voice agents that run on PHP shared hosting." A visual canvas lets a user connect trigger steps (webhooks, schedules, timers) to action steps across 1,690 apps and 8,700 actions. An AI builder reads a plain-language description and proposes a workflow. The step-by-step debugger shows the data at each step and the run history is kept in MySQL.

The second half of the product is AI voice agents. The README says the agents can answer phones, book appointments and read from the same data sources as the workflow canvas. They are built from the same UI as a workflow, so a reader who builds a phone agent uses the same connectors. Permissions are per-team and the system is multi-user.

Key facts

• Licence: AGPL-3.0.
• Backend: PHP 8.2 or later, Laravel 12.
• Database: MySQL 5.7 or later.
• Frontend: React 18, with React Flow for the visual canvas and Tailwind CSS.
• Hosting: PHP shared hosting (Hostinger, cPanel, DirectAdmin) or a VPS. No SSH, Composer or Node.js is required on the server.
• Scheduling: one cron job executes all workflows.
• Connectors: 1,690 apps, with 8,700 actions.
• AI builder: writes a workflow from a plain-language description, with any supported model.
• AI voice agents: answer phones and book appointments.
• Debugger: step-by-step, with run history in MySQL.
• Team support: multi-user with permissions.
• Version: 1.8.1 at the time it was read.

What does it replace, and where does it fall short?

FlowForge replaces Zapier and Make for teams that want self-hosted workflow automation on PHP hosting they already pay for, with voice agents and an AI builder in the box.

Where it falls short: AGPL-3.0 is a strong copyleft licence. A hosted fork that charges end users for FlowForge-as-a-service has to publish its source under AGPL, which rules out a closed-source commercial fork. The connector list is the maintainer's at 1,690 apps and 8,700 actions; the README does not list each one, and there is no independent registry to check it. The AI voice agents need a phone-provider account separately (the README does not bundle Twilio or a similar service), and the AI builder calls a model the user configures.

How does FlowForge run?

Upload the release zip to a PHP 8.2+ host, point the web root at public/, create a MySQL database and run the installer, which writes a cron entry that drives every workflow. The README states that no SSH, Composer or Node.js is required on the server; the frontend is pre-built.

Open the admin UI in a browser and sign in. Drag a trigger onto the canvas, pick a connector and an action, run the step-by-step debugger, and save. The AI builder is a separate panel: describe a workflow in plain language and FlowForge proposes a canvas layout. Voice agents are built from the same canvas and connected to a phone provider through a connector.

Who is FlowForge for?

A small or mid-sized team that already pays for PHP shared hosting (Hostinger, cPanel, DirectAdmin) and wants to replace a Zapier or Make subscription without moving to a Node or Docker host. A reader who wants a Node-based stack or a Docker install is better served by n8n or Activepieces. A reader who needs air-gapped automation should look at Huginn or Windmill.

What limits does the README state?

• PHP 8.2 or later is required; older PHP is not supported.
• MySQL 5.7 or later for the database.
• AGPL-3.0 copyleft applies to any hosted fork.
• One cron job drives all workflows; the host has to allow cron.
• Voice agent features require a separate phone-provider account through a connector.
• The AI builder calls a model the user configures; no model is bundled.

Questions people ask

Is FlowForge open source?

Yes. The repository is under GNU Affero General Public License v3.0 (AGPL-3.0), an OSI-approved licence. AGPL is a strong copyleft licence: a fork that is distributed to users, or offered as a hosted service, has to publish its source under the same licence. The README itself says the project welcomes pull requests.

Does FlowForge work offline?

The platform itself runs on the user's own PHP host and does not call a central FlowForge server. Connectors call the third-party services they are built for, so a workflow that triggers Slack or Stripe sends data to those providers. The AI builder calls an LLM provider the user configures. A fully offline run is possible only if every connector in the workflow talks to on-premise services.

Can FlowForge be used commercially?

Yes for commercial internal use. A company can install FlowForge on its own PHP host without a fee, and the AGPL-3.0 grant covers that. Commercial hosting (selling FlowForge-as-a-service to third parties) is allowed, but the host has to publish its source under the AGPL to the users it serves. A commercial fork that wants to stay closed source has to negotiate a separate licence with the maintainers.

How does FlowForge compare with Zapier and Make?

Zapier and Make are hosted products with monthly subscriptions and billed per task or per operation. FlowForge is self-hosted on PHP hosting, billed per host, and it adds voice agents and an AI builder in the same UI. The trade is: Zapier's and Make's hosted uptime and large connector market against FlowForge's one-price self-host, voice agents and AGPL openness. The open-source alternatives to Zapier and Make pages set FlowForge beside n8n, Huginn, Activepieces and Windmill.

Does FlowForge really run on shared hosting?

Yes, that is the project's central claim. The README says no SSH, Composer or Node.js is needed on the server and that one cron job drives every workflow. A cPanel, DirectAdmin or Hostinger plan with PHP 8.2 and MySQL is enough. A heavy workload still benefits from a VPS, because shared hosting quotas on CPU and memory can throttle long runs.

Sources

• FlowForge README and LICENSE: github.com/DeveloperSarim/FlowForge, read 2026-11-09.