Self-hosted Activepieces and custom pieces
MicroFlow, our workflow platform, is built on Activepieces. If you want your own instance, or steps that connect it to in-house systems, this page covers what to plan.
Reviewed by: Rahul Jaiswar, founder
What Activepieces is
Activepieces is an open-source workflow automation platform with a visual builder, triggers and ready-made steps called pieces. It runs as a hosted service or on your own servers with Docker.
How we use it
MicroFlow is built on open-source Activepieces (MicroFlow). It has a visual flow builder, an AI copilot that builds and fixes flow steps (it can use Ollama Cloud models, Ollama), and support for multiple AI model providers. It also has browser automation through a Chrome extension and tables that log runs.
What a custom piece involves
A piece is a TypeScript package that defines triggers, actions and how it signs in to the outside system. Once built and loaded into your instance, it appears in the visual builder beside the ready-made pieces, so your team uses it without touching code. The work is mostly in the other system’s API: its sign-in method, its limits and the shape of the data it returns.
When it fits
- Flows touch customer or employee records that should stay on your servers.
- Per-task pricing on a hosted tool is climbing with volume.
- A system you run in-house has no ready-made connector, and a custom piece would add one.
When it doesn’t
- Only a few simple flows are planned; setup effort may outweigh the gain.
- The process is long, stateful and core to your product; that belongs in code (platform or custom code).
- Nobody will hold the server. We can host and run the instance in an account you own, with cover set in the scope of work (what running a self-hosted system involves).
Decide before installing
- Which version will we run, and how are upgrades tested?
- Which features are in the open-source edition, and which need a paid licence?
- How are custom pieces built, versioned and deployed?
- How long is run history kept?
Watch for
- Upgrades include database migrations. A new version can fail on an existing database, so pin the version and test each upgrade on a copy first.
- Source edits aren’t live until rebuilt. Outside dev mode, pieces run from built output, so edits to source go live only after a rebuild.
Related tools and pages
Considering your own workflow platform?
List the tools you use now and roughly how many flows run each day.