Before you start
You need Docker Engine or Docker Desktop with Docker Compose v2, an Internet connection and a Linux AMD64 or ARM64 host. For a small initial deployment, allow 4 GB of memory and enough disk space for your database, execution history and backups. Increase capacity as your workflows grow. The supported configuration runs the application and worker together, with separate PostgreSQL with pgvector and Redis services. A single-container embedded database and Kubernetes deployment are outside this release’s tested installation path. Configured apps and AI providers need their own network access and credentials. Third-party provider API costs are not included.Download the configuration
Create a folder and download the complete, secret-free templates:deployment/compose.yaml
deployment/compose.yaml
deployment/.env.example
deployment/.env.example
Set your secrets and address
Generate three separate values:deployment/.env. Put the first value in AP_ENCRYPTION_KEY, the second in AP_JWT_SECRET and the third in AP_POSTGRES_PASSWORD. Keep this file private and outside version control.
For local evaluation, keep AP_FRONTEND_URL=http://localhost:8080 and the loopback binding. For your server, set the intended HTTPS application address, configure a reverse proxy and follow HTTPS setup. Your browser needs WebSocket access. External webhook providers must be able to reach the public address.
Optional account email
To send password-reset and account-invitation emails, setAP_SMTP_HOST, AP_SMTP_PORT, AP_SMTP_USERNAME, AP_SMTP_PASSWORD and AP_SMTP_SENDER_EMAIL in your private environment file. All five values are required. SMTP authentication and certificate validation are enforced. Use port 587 with STARTTLS or port 465 with direct TLS; other ports also require STARTTLS. The image contains no configured SMTP credentials: supply your own at runtime. Without SMTP, the owner can copy invitation links manually; password-reset email is unavailable.
Start your installation
From thesydekyks folder:
What this release includes
Visual workflows, execution history, connections, integration discovery, tables, files, owned Syd assistance and saved AI agents are included for free. Unlimited user accounts can use personal workspaces; the owner can invite accounts to the platform. Unavailable controls are hidden in 1.0.6. The new upstream AI Tiers screen remains hidden until the independently implemented Syd chat contract supports it. Member sharing, quotas, provisioning and a restore screen remain unavailable. Additional creator-owned Command Centers and their administration are supported. Other unavailable features include custom roles, aggregate/global connections, Gadget Sets and selector customization, platform template management, SSO/SCIM, Secret Managers, Audit Logs/Event Streaming, API Keys, embedding, Worker Groups, Git/environment/releases/approvals, upstream billing/usage, Impact and custom logo/color/favicon settings. Community template browsing/sharing, gadget installation, platform invitations, project connections and variables remain available. Open-source component notices remain in the image.Restart, update and preserve your data
Restart without changing the configuration:.env, encryption/JWT keys and volumes. Back up PostgreSQL and stop the old application and workers before selecting ibassoftware/sydekyks:1.0.6. Start the same version on every app and worker. Released initial schema and blocking migrations are retained. Version 1.0.6 adds a background-migration tracking table; its background list is empty. Existing data and connected-account encryption remain unchanged. Old license state is ignored. Check migration logs, application health and a small mission before resuming normal work. Keep the prior image digest and backup available for recovery.
Before an update, back up the database and volumes and record the current image digest. Read the next release’s migration instructions before changing SYDEKYKS_IMAGE; do not use an unreviewed moving tag for unattended production updates. Never use docker compose down --volumes on data you need to keep. See backup and recovery.
All available features remain accessible without a license or recurring entitlement checks. Authentication and workspace permissions still apply.