26 posts tagged with "Enterprise"
View All TagsPersistent 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.
New features
- Volumes: persistent file storage attached to scripts via comment annotations, synced to workspace object storage.
- Dynamic volume names with $workspace and $args[...] interpolation.
- Per-worker LRU volume cache (10 GB) with exclusive leasing for concurrency safety.
- Per-script sandbox annotation (#sandbox / //sandbox) now supported for Python and TypeScript in addition to Bash.
- AI sandbox: sandboxing + volumes pattern for running AI coding agents (Claude Code, Codex, OpenCode) with persistent state.
- Built-in Claude Code template using the Claude Agent SDK with volume-backed session persistence.
- Volumes UI in the Assets page for browsing, exploring, and deleting volumes.
- Community Edition volume limits: max 20 volumes per workspace, 50 MB per file.
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.
New features
- .npmrc support for npm private registries, compatible with Bun (1.1.18+), Deno 2.x, and npm proxy.
- Maven settings.xml configuration for private Maven repositories, written to {JAVA_HOME}/.m2/settings.xml.
- Cargo config.toml for private Cargo registries, written to .cargo/config.toml in the job directory.
- All private registry configurations are Enterprise Edition features.
Manage Windmill instance configuration declaratively with YAML files, a Kubernetes operator, or the CLI. Version-control, review, and reproduce your setup across environments.
New features
- Declarative YAML configuration for global settings and worker groups.
- Kubernetes operator with ConfigMap-based continuous reconciliation and drift detection.
- sync-config CLI command for Docker Compose and VM deployments.
- Secret references via envRef (environment variables) and secretKeyRef (Kubernetes Secrets API).
- Export current instance configuration as YAML from the UI or CLI.
Enforce governance policies on workspaces by disabling direct deployments or workspace forking. Configure bypass permissions for specific users or groups.
New features
- Disable direct deployment to enforce review workflows
- Disable workspace forking to control development environments
- Configure bypass permissions for users or groups
- Works with Git Sync and Deploy to Prod workflows
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.
New features
- Key/value-based message filtering for Kafka triggers
- JSON superset matching for flexible filtering
- Shared filter component with WebSocket triggers
- Filter preview in the trigger editor UI
Capture HTTP requests made by job scripts as observability spans
New features
- View HTTP request traces (method, URL, status, timing) in the job details UI
- Auto-instrumentation for Native TypeScript, MITM proxy for other languages
- Integrates with external OpenTelemetry collectors
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.
New features
- DuckDB write support for Azure Blob Storage
- Works with Parquet, CSV, and JSON formats
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.
New features
- Workspace-level success handler triggered on job completion
- Receives job result, path, email, job_id, and metadata
- Configurable from workspace settings with template support
- 60-second cache for handler settings
Windmill autoscaling now supports native Kubernetes integration, providing easier setup, improved reliability, and enhanced security compared to custom script-based solutions.
New features
- Native Kubernetes autoscaling without custom scripts.
- Automatic worker-group, namespace and credentials inference.
- RBAC-based security with deployment scaling permissions.
- Health check validation for proper configuration.
- Seamless integration within existing Kubernetes clusters.
Windmill now supports using AWS OIDC for instance object storage configuration.
New features
- Added AWS OIDC support for instance object storage
Install the Windmill GitHub App instead of using a long lived personal access token (PAT) to authenticate with GitHub for Git sync
New features
- No need for long lived GitHub personal access token
- Improved controls over repo access from Windmill using the App installation scope
Support for NATS triggers to run jobs when messages are received.
New features
- Add support for NATS triggers to run scripts and flows when messages are received from NATS subjects
- NATS triggers run on the server side without consuming worker resources
Windmill now supports Oracle scripts.
New features
- Write your Windmill script in Oracle.
- Run your Oracle scripts locally or in the cloud.
Cloud and enterprise users can now set a custom public URL for their app.
New features
- Set a custom public URL for your app
Enterprise users can now search jobs and logs using our new indexer service powered by the rust search engine Tantivy.
New features
- Updated helm charts to run the indexer service and enable full text search
- Search jobs from anywhere, querying path, args, results or even job logs
- Minimal grafana-like tool to explore service logs
Enterprise users now have access to a dedicated dashboard for tracking feature requests and issues.
New features
- Private issue tracking dashboard
- Feature request tracking
- Automatic email and Slack/Discord notifications
- GitHub integration for issue tracking
- Release tracking and notifications
Support for Kafka triggers to run jobs when messages are received.
New features
- Add support for Kafka triggers to run scripts and flows when messages are received from Kafka topics
- Kafka triggers run on the server side without consuming worker resources
Critical alerts notifications are now displayed in the UI.
New features
- Critical alerts notifications are now displayed in the UI
Windmill AI now supports Mistral's Codestral and Anthropic's Claude 3.5 models.
New features
- Added support for Mistral Codestral model
- Added support for Anthropic Claude 3.5 model
Support for WebSocket triggers to run jobs when messages are received.
New features
- Connect to WebSocket servers and trigger scripts/flows when messages are received
- Support for both static WebSocket URLs and dynamic URLs generated by scripts/flows
- Configure initial messages for authentication or subscriptions
- Filter incoming messages using JSON path matching
- Server-side listening without consuming worker resources
Worker autoscaling automatically adjusts the number of workers based on your workload demands.
New features
- Automatic worker scaling based on workload demands
- Configurable min/max worker limits
- Support for custom scaling scripts
- Occupancy-based scaling decisions
- Cooldown periods to prevent scaling thrashing
- Detailed autoscaling event logging
Critical alerts for jobs waiting in queue.
New features
- Add functionality to monitor job queues and trigger alerts for waiting jobs, with UI for alert management in enterprise feature.
- The "cooldown" parameter determines the minimum duration between two consecutive alerts if the number of waiting jobs are fluctuating around the configured threshold.
Windmill supports custom HTTP routes to trigger a script or flow.
New features
- Trigger a script or flow via a custom HTTP route.
- Use a preprocessor to transform the request before it is passed to the runnable.
Get a notification everytime on critical events such as when a job is re-run after a crash.
New features
- Get email or Slack notifications for critical events such as everytime a job is re-run after a crash.
- You can set an alert to receive notification via Email or Slack when the number of running workers in a group falls below a given number.
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.
New features
- Windmill Billing Portal available at https://portal.windmill.dev/
- See info on subscription and usage.
- Update contact info from your portal.
- Update subscription and billing details.
- Automatic license key renewal.
If configured, users who are operators in this workspace will be redirected to this app automatically when logging into this workspace.
New features
- Set an app to pop up when an operator logs into the workspace.
- Make sure the default app is shared with all the operators of this workspace before turning this feature on.