Self-host Sydekyks with Docker

Understand the Docker, PostgreSQL, Redis, HTTPS and backup requirements for running the free Sydekyks workflow platform.

A free platform on infrastructure you control

Self-hosting means your team operates the Sydekyks installation: its server, updates, backups and access. The software is free, while your infrastructure and connected providers have their own running costs.

What you need

  • A Linux environment with Docker and Docker Compose.
  • PostgreSQL with pgvector and Redis. The supported Compose template defines both.
  • Private configuration for your database password, encryption key and JWT secret.
  • HTTPS and appropriate network access for a server deployment.
  • Connections and any provider subscriptions required by the missions you build.

The public image ibassoftware/sydekyks:1.0.6 supports AMD64 and ARM64. In the supported Compose setup, the application and worker run together. The initial port binding is local to the host; configuring public access is a separate operator responsibility.

Install the supported release

Use the Docker Compose installation guide for the complete configuration and commands. The source repository also contains the matching root Compose file and a setup helper that generates private secrets without replacing an existing environment file.

Keep the data needed for upgrades

Back up your database and application volumes, and keep your encryption key and JWT secret. Use the same release across app and worker processes. Read the upgrade instructions before changing an existing installation.

Installations through 1.0.5 used the earlier activation system. The unrestricted 1.0.6 release ignores old license records and does not require license renewal. Your normal account and workspace access rules still apply.

Self-hosting and data destinations

A self-hosted server can still send data to services used by a mission. Review email, AI, OCR and other provider destinations, credentials and permissions before enabling a workflow. See the data and telemetry guide.

When to ask for help

If your team would prefer help with the infrastructure, ongoing support or workflow setup, hosting and support are available as optional services. Agree the responsibilities and service scope before committing.