Figranium vs
Automa

Figranium and Automa both make browser automation visual, but they put the workflow in different places.

Figranium runs saved browser tasks on your own instance and exposes them through an API or scheduler. Automa is a browser extension where you connect blocks into workflows that run in the browser environment.

Compare how each tool is built and run, and see which approach suits your browser tasks and integrations.

Explore Figranium
Automa logo

Figranium and Automa:
what's the difference?

See how Figranium helps you build, run, and reuse browser automation.

OverviewFigraniumAutoma
What it does

Build browser workflows visually, then run them through an API or on a schedule.

Automa is a browser extension for automating browser tasks with a visual workflow builder.

Building

Stack browser actions in a visual task editor.

Connect blocks in a visual extension workflow.

Running

Run on a self-hosted instance, via API or schedule.

Run workflows from the browser extension, including on a schedule.

Best fit

Browser tasks invoked by applications and automation platforms.

Automating work directly in a browser extension.

About the tools

About Figranium

Figranium is an open-source, self-hosted browser automation platform. Build browser actions in a visual block editor, then run saved tasks through the REST API or on a schedule. It also supports runtime variables, proxy configuration, and integrations with automation tools and AI clients.

Explore Figranium docs ↗

About Automa

Automa is a browser extension that connects blocks into workflows for tasks such as filling forms, scraping data, and taking screenshots. It also supports scheduled workflows and a workflow marketplace.

Explore Automa docs ↗

Your browser automation, on your infrastructure.

Figranium is open source and self-hosted. Install it on a machine or server you control: the browser, workflow execution, and saved data run on that instance. Trigger tasks through its API or scheduler without moving the runtime to a managed platform.

You choose and pay for the infrastructure, and you are responsible for setup, updates, security, and maintenance. Data can still leave your instance when you configure external services or visit websites; optional anonymous telemetry can be disabled.

Explore deployment options ↗

Why choose Figranium?

Figranium brings browser workflows into your application stack. Build a task visually, run it on your own instance, and trigger it from an API or schedule—ideal when browser automation needs to be part of a larger service.

Explore Figranium docs

Start with a template.

Explore pre-built Figranium workflows for tasks like data extraction, monitoring, and enrichment. Use a template as a starting point, then adapt the browser steps to your needs.

Explore templates

Frequently asked questions

Can I run a task without keeping my browser extension open?

Figranium runs tasks on your self-hosted instance and can trigger them by API or schedule. Automa runs as a browser extension, so its execution depends on its browser environment.

Can I import an Automa workflow into Figranium?

There is no direct import described here. Recreate the steps in Figranium's editor and test them against the target site.

Can another application trigger my workflow?

Figranium exposes saved tasks through its REST API, so an application can invoke a task and pass runtime variables.

Turn browser tasks into workflows.

Build visually. Run on your terms.

Get started