Activepieces hosting

Open automation with hundreds of integrations — and no execution quota.

AutomationMIT (community edition)from $5.99/mo
In short

Activepieces hosting at AIHostBox means a dedicated, single-tenant Activepieces instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and keep it patched. Plans start at $5.99 per month and the admin account, the data and any API keys are yours.

280+ piecesAI stepsBranches & loopsCustom piecesVersioned flows

Activepieces is a workflow builder in the shape most people expect: triggers, steps, branches and a large library of pieces for the SaaS tools you already use, plus AI steps that call whichever model you configure. Flows are versioned, and you can write a custom piece in TypeScript when the library runs out.

The reason to self-host it is arithmetic. Hosted automation is priced per task or per execution, so a busy flow gets expensive precisely when it is working. Here you pay for the instance: two hundred runs a month and two hundred thousand cost the same.

Activepieces hosting plans

StarterPersonal use & small teams
2 GB RAM · 1 vCPU · NVMe
$5.99/mo
Order
PlusBusy workflows & communities
4 GB RAM · 2 vCPU · NVMe
$9.99/mo
Order
ProHeavy pipelines & many users
8 GB RAM · 3 vCPU · NVMe
$16.99/mo
Order

Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.

How we run Activepieces

The official Activepieces compose layout: an app container and a separate worker container from the same image, Postgres (pgvector image) for flows and run history, and Redis for the job queue.

What we configure for you

  • AP_ENCRYPTION_KEY and AP_JWT_SECRET generated per instance
  • AP_FRONTEND_URL set to your HTTPS domain for webhooks and OAuth redirects
  • AP_DB_TYPE=POSTGRES with AP_POSTGRES_* credentials and AP_REDIS_* for the queue
  • AP_EXECUTION_MODE chosen so code steps run sandboxed
  • AP_SMTP_* settings for invitations and alerts
  • AP_TELEMETRY_ENABLED=false unless you want to share usage data

Which plan fits

Starter (2 GB) runs the four containers for personal automations and a handful of scheduled flows. Plus (4 GB) suits a team with frequent webhook traffic, and Pro (8 GB) is for heavy polling, large file steps or many flows firing at once.

The honest limits

SSO, projects, custom roles and audit logs are enterprise-licensed and not included. AI steps call whatever model you configure, so tokens are billed by that provider unless you point them at a model you host.

What people run Activepieces for

Lead routing

Form to CRM to notification, with an AI step for classification.

Document processing

Watch a folder, extract fields, file the result.

Internal alerting

Turn noisy webhooks into the two messages that matter.

Licence and version policy

ItemPosition
Upstream licenceMIT (community edition)
Sold as managed hostingYes
TenancySingle tenant — one customer per instance
PatchingCritical advisories within 24 hours, high severity within 72

Our full position on licences, including the applications we decline to sell, is on the licensing page.

Reading on Activepieces

Works well with Activepieces

More Automation we host

Questions

Activepieces hosting: your questions

Is there a run limit?
No. The only limits are the CPU and memory of your plan, which is the honest constraint rather than a billing one.
Can it call my own model?
Yes — point the AI steps at an Ollama or LiteLLM plan and the automation runs on a model you host.
What is missing from the community edition?
The MIT community edition has unlimited flows, runs and users. Projects, SSO, custom roles, audit logs and Git Sync sit in a separately licensed enterprise directory that needs an Activepieces subscription for production use. We host the community edition only.
Where are my flows and connection secrets stored?
In Postgres, alongside run history. Connection credentials are encrypted with AP_ENCRYPTION_KEY. The database is in the nightly backup, and we keep the key with it; a database restored without the matching key would leave every connection needing to be re-authorised.
Why do webhooks and OAuth connections need the right URL?
Activepieces builds webhook addresses and OAuth redirect URLs from AP_FRONTEND_URL. We set it to your instance’s HTTPS address from the start, so a Google or Slack connection authorises cleanly and webhook URLs you paste into other services stay valid.
How long can a single flow run?
By default a flow run stops after 600 seconds (AP_FLOW_TIMEOUT_SECONDS) and a synchronous webhook waits 30 seconds for a response (AP_WEBHOOK_TIMEOUT_SECONDS). We can raise both for long document jobs, within what your plan’s memory and CPU can sustain.

Run Activepieces without running a server

A dedicated Activepieces instance, deployed and maintained by us. Month to month, cancel whenever.