Skip to main content
Best for personal projects on one machine. It runs on an embedded database, so it cannot scale, cannot move to Enterprise, and moving off it means starting over.Unless you’re happy with that, use Self hosting instead.

​
Install

Run this anywhere:
Or hand it to your AI assistant:

Install Activepieces with an AI assistant

Open in Cursor
Requirements
Everything runs in one container with the database embedded, so there is no PostgreSQL or Redis to set up. Your data lives in ~/.activepieces on your machine.

​
Open Activepieces

Go to http://localhost:8080, or http://<your-server-ip>:<your-port> if you installed on a remote server or changed the port. The first account you create becomes the administrator. There is no default username or password.

​
Make webhooks reachable (optional)

Skip this if your machine already has a public URL. Webhooks and app triggers need an address that third parties can reach. On a personal machine, expose it with a tunnel such as ngrok:
Then set AP_FRONTEND_URL to the ngrok URL and run the container again.
Copying the public URL from ngrok
ngrok is fine for testing but not suitable for production. In production, point AP_FRONTEND_URL at your real domain.

​
Upgrade

Back up first, since the container is replaced:
Then pull the new image and start a fresh container with the same command you used to install:
Your data survives because it lives in ~/.activepieces, not in the container.

​
Uninstall

Remove the container and keep your data:
Delete your data too:

​
Good to know

This setup cannot be upgraded to Enterprise. Enterprise does not support the embedded database, so moving to it means starting over. If that is a possibility, start with Self hosting.
It runs on PGLite (embedded PostgreSQL) and an in-memory queue, which supports a single instance on a single machine. For production or multi-instance setups, use Self hosting with PostgreSQL and Redis.