zenvara/server repository overview

⁠Zenvara

AI-native automation platform. Define flows in YAML and run them as directed acyclic graphs of actions that move and transform data across S3, HTTP/SOAP, SFTP, Redshift, and the filesystem. Ships with a browser-based Studio for building, running, and monitoring flows — served by the same container.

• Image: zenvara/server
• Architectures: linux/amd64, linux/arm64
• Base: .NET 10 (aspnet:10.0), runs as non-root UID 1000

⁠Quick start

docker run -d --name zenvara \
  -p 5000:5000 \
  -v zenvara-data:/data \
  zenvara/server:latest

• Studio (web UI): http://localhost:5000/studio/⁠
• REST API: http://localhost:5000/api/v1/⁠
• Health check: http://localhost:5000/health⁠

Or with Compose:

services:
  app:
    image: zenvara/server:latest
    ports:
      - "5000:5000"
    volumes:
      - zenvara-data:/data
    restart: unless-stopped
volumes:
  zenvara-data:

⁠⚠️ Before you expose this publicly

Authentication is OFF by default, and with auth disabled every caller has full admin access. This is convenient for local evaluation but unsafe on a public network — never bind the port to the internet without enabling auth.

Enable authentication and put the container behind a TLS-terminating reverse proxy (the app itself serves plain HTTP):

docker run -d --name zenvara \
  -p 127.0.0.1:5000:5000 \
  -e Auth__Enabled=true \
  -e Auth__Jwt__SecretKey='<a random string of 32+ characters>' \
  -v zenvara-data:/data \
  zenvara/server:latest

On first start with auth enabled, a bootstrap admin credential is generated — check the container logs. See the documentation for provider setup (Local, API Key, LDAP, OIDC) and hardening.

⁠Configuration

Configure via environment variables using __ (double underscore) as the section separator. Common examples:

All state persists under the /data volume:

/data/storage   flows, environments, connections, secrets, auth
/data/backups   scheduled backups
/data/cache     ephemeral cache
/data/logs      text + ndjson logs

Back up /data to preserve your configuration and history.

⁠Tags

• latest — most recent stable release
• X.Y.Z — a specific release (e.g. 3.0.0); prereleases carry a suffix (e.g. 3.0.0-rc1)

⁠Links

• Documentation: docs.zenvara.ai⁠
• GitHub: github.com/zenvara-platform/server⁠