You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no default account. Open http://:8080/login and click Create account: the first sign-up becomes the administrator and closes sign-up, further users are invited from the settings. Anyone who reaches the port can claim it until then, so create the account right after the install.
Webhook triggers and OAuth2 connection redirects are built from BYTECHEF_PUBLIC_URL in /opt/bytechef_data/.env, which points at the container IP. Change it when the IP changes or ByteChef sits behind a reverse proxy or domain, then run systemctl restart bytechef.
Back up BYTECHEF_ENCRYPTION_PROPERTY_KEY from /opt/bytechef_data/.env together with the database. It encrypts the stored connection credentials, so a database restored without it is useless for them.
ByteChef is open-core. Like the official image, this build runs the Enterprise Edition (BYTECHEF_EDITION=EE, the default; CE mode does not start in 0.34.x): the modules under the ByteChef Enterprise License (embedded iPaaS, API platform, AI gateway, SSO and SCIM, custom components, audit log) are free for development and testing, production use of them needs a subscription.
Install and every update compile ByteChef from source (Gradle, around 650 modules, plus the React client), which takes about 15 minutes on 4 cores and needs the 6 GB of RAM. The running server is fine with 2 GB, so the RAM can be lowered after the install and raised again before an update.
Code steps (JavaScript, Python, Ruby) run on the Temurin JDK in GraalVM's interpreter mode, not with the GraalVM JIT of the official image, so they work but run slower.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Activity
github-actions commentedon Oct 3, 2026
The Bytechef script is ready for testing. Run it in the Proxmox VE shell (or on an Incus host) to create a container:
There is no default account. Open http://:8080/login and click Create account: the first sign-up becomes the administrator and closes sign-up, further users are invited from the settings. Anyone who reaches the port can claim it until then, so create the account right after the install.
Webhook triggers and OAuth2 connection redirects are built from BYTECHEF_PUBLIC_URL in /opt/bytechef_data/.env, which points at the container IP. Change it when the IP changes or ByteChef sits behind a reverse proxy or domain, then run systemctl restart bytechef.
Back up BYTECHEF_ENCRYPTION_PROPERTY_KEY from /opt/bytechef_data/.env together with the database. It encrypts the stored connection credentials, so a database restored without it is useless for them.
ByteChef is open-core. Like the official image, this build runs the Enterprise Edition (BYTECHEF_EDITION=EE, the default; CE mode does not start in 0.34.x): the modules under the ByteChef Enterprise License (embedded iPaaS, API platform, AI gateway, SSO and SCIM, custom components, audit log) are free for development and testing, production use of them needs a subscription.
Install and every update compile ByteChef from source (Gradle, around 650 modules, plus the React client), which takes about 15 minutes on 4 cores and needs the 6 GB of RAM. The running server is fine with 2 GB, so the RAM can be lowered after the install and raised again before an update.
Code steps (JavaScript, Python, Ruby) run on the Temurin JDK in GraalVM's interpreter mode, not with the GraalVM JIT of the official image, so they work but run slower.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1556007501231685722