Continuously export audit logs as newline-delimited JSON to a dedicated logs/audit/ folder in instance object storage, for SIEM forwarding and archival.

Trigger scripts and flows in response to Azure Event Grid events from custom topics, system topics, domains, and Event Grid Namespaces.

Workspace forks now include data tables, and the new wmill workspace merge command enables merging forks back to the parent.

Store Windmill secrets in AWS Secrets Manager as an alternative to the database, HashiCorp Vault, or Azure Key Vault.

Store Windmill secrets in Azure Key Vault as an alternative to the database or HashiCorp Vault.

Dedicated worker scripts sharing the same workspace dependency and language now automatically run in a single long-lived subprocess.

Create workspace-scoped automation identities that cannot log in directly, for CI/CD pipelines and API integrations.

SCIM PATCH with active:false now disables users at the instance level instead of deleting them. Admins can also manually disable users.

Add per-step debouncing to flow nodes to consolidate repeated executions of a specific step within a flow.

Self-managed GitHub App support for GitHub.com and GitHub Enterprise Server instances, enabling Git sync without relying on the Windmill-managed GitHub App.

Persistent volumes for scripts via code annotations, per-script sandbox annotation for Python and TypeScript, and AI sandbox for running coding agents with isolation and persistent state.

Approval steps in workflows as code now expose a selfApproval flag (TypeScript) and self_approval (Python) to control whether the user who triggered the workflow can also approve it, matching the visual flow editor toggle.

MS SQL Server resources can now authenticate using Azure AD (Entra) OAuth tokens through the aad_token field, alongside username/password and Windows Integrated Authentication. Uses the Windmill Azure OAuth setup with the database.windows.net scope.

Configure private package registries for npm, Maven, and Cargo from instance settings. Supports .npmrc for npm/Bun/Deno, settings.xml for Maven/Java, and config.toml for Cargo/Rust.

Manage Windmill instance configuration declaratively with YAML files, a Kubernetes operator, or the CLI. Version-control, review, and reproduce your setup across environments.

Enforce governance policies on workspaces by disabling direct deployments or workspace forking. Configure bypass permissions for specific users or groups.

Kafka triggers now support message filtering. Define key/value pairs to filter messages before they trigger a job. Uses JSON superset matching — the message value at a given key must contain all fields from the filter value.

Capture HTTP requests made by job scripts as observability spans

DuckDB scripts can now write data to Azure Blob Storage in addition to reading. Supports Parquet, CSV, and JSON formats when Azure Blob is configured as workspace storage.

Configure a script to run automatically when jobs complete successfully in the workspace. The counterpart to the workspace error handler — receives the job result, path, and metadata. Cached with a 60-second TTL.

Windmill autoscaling now supports native Kubernetes integration, providing easier setup, improved reliability, and enhanced security compared to custom script-based solutions.

Windmill now supports using AWS OIDC for instance object storage configuration.

Install the Windmill GitHub App instead of using a long lived personal access token (PAT) to authenticate with GitHub for Git sync

Support for NATS triggers to run jobs when messages are received.

Windmill now supports Oracle scripts.

Cloud and enterprise users can now set a custom public URL for their app.

Enterprise users can now search jobs and logs using our new indexer service powered by the rust search engine Tantivy.

Enterprise users now have access to a dedicated dashboard for tracking feature requests and issues.

Support for Kafka triggers to run jobs when messages are received.

Critical alerts notifications are now displayed in the UI.

Windmill AI now supports Mistral's Codestral and Anthropic's Claude 3.5 models.

Support for WebSocket triggers to run jobs when messages are received.

Worker autoscaling automatically adjusts the number of workers based on your workload demands.

Critical alerts for jobs waiting in queue.

Windmill supports custom HTTP routes to trigger a script or flow.

Get a notification everytime on critical events such as when a job is re-run after a crash.

We have released our new Windmill Billing Portal https://portal.windmill.dev/.

You can access your Portal from your Instance settings, in the "Core" tab. Or by visiting https://portal.windmill.dev/, entering your email and then accessing the link sent via email. Update contact information, billing details and subscription (seats & workers) from the portal. From there, you can also enable/disable any time automatic renewal and automatic debit (therefore payment by invoice).

In the Usage section, you can find the seats of workers usage of your Prod instance, and check whether your use of Windmill corresponds to your subscription. There is a ‘Report an error’ button, please use it if reported usage is incorrect.

It's also an opportunity for us to explain our new way of managing license keys for self-hosted instances.

As you know, when you subscribe to Windmill, you receive a license key to enter in the instance settings. Now, this key automatically updates every day as long as the subscription is valid. A key is valid for 35 days and expires as soon as an updated key replaces it. This system relieves you from having to worry about your key expiring. Now everything is automatic as long as your subscription is valid. You can still contact us for exceptions.

If configured, users who are operators in this workspace will be redirected to this app automatically when logging into this workspace.