Run Activepieces on your own offshore server to build and operate visual workflows. You choose the integrations and control the deployment. Size the server for concurrent runs and review the installed edition, licensing and any third-party API charges; self-hosting does not make every workflow cost-free.
What you get
- A visual builder with 200+ integrations, from Slack and GitHub to Stripe and OpenAI
- A piece SDK, so you can write your own integration when none fits
- Triggers on a schedule, a webhook or on demand
- Control of the deployment, while connected services still receive the data your flows send to them
Get it running
Size for your workflows
Choose a supported catalog deployment with the Impreza Agent online. Check the current version requirements and leave capacity for workers, the database and concurrent flows; a fixed memory figure is not a guarantee for every workload.
Install it in one click
Install it from the catalog with a hostname such as flows.example.com. That hostname is what upstream services register their webhook callbacks against, so choose one you will keep.
Save the encryption key before anything else
The install generates an encryption key and a session signing secret. Put the encryption key in your password manager immediately: it is what decrypts every credential the platform stores.
Build your first flow
Connect the services you use, pick a trigger, and test with sample data before pointing it at anything that matters.
That key decrypts the stored credentials for every connected service. Change it or lose it and the existing connections become unreadable, which means reconnecting every integration by hand. It also means a backup is only restorable if you kept the key: back it up separately from the server, and treat it as the most important secret in the deployment.
It holds tokens for every service it touches, so it deserves the same care as a password manager: keep it patched, restrict who can reach the builder, and never paste production credentials into a flow you are only experimenting with.
Activepieces and n8n offer self-hosted workflows. Compare the integrations, edition, licensing and maintenance needs that fit your team instead of choosing only by execution pricing.
Upstream services keep calling the URL they registered. Changing the hostname later breaks those registrations, so decide the domain before you connect integrations.
Operate flows and protect connected credentials
Use app inspection and maintenance to check the supported deployment before an update. Flow schedules and retries belong to Activepieces; an Impreza platform event does not prove that a business workflow finished successfully. Test with non-production connections before enabling a changed flow.
Plan app backups to Impreza S3 alongside a database-consistent recovery procedure. Preserve the encryption key and required configuration securely with the data needed to recover flows and connections. A database copy without the matching key is not enough to recover encrypted credentials.
For migration between compatible servers, review callback URLs and pause triggers as needed so the old and new instances do not execute the same work twice. Validate one test flow before restoring normal traffic.
Start now
Spin up an offshore VPS and install Activepieces from the catalog, or read the documentation.