Home / Companies / Kestra / Blog / Post Details
Content Deep Dive

Plugins Aren't Just Integrations Anymore

Blog post from Kestra

Post Details
Company
Date Published
Author
François Delbrayelle
Word Count
4,151
Company Posts That Month
10
Language
English
Hacker News Points
-
Post removed?
No
Summary

Kestra 2.0 expands its plugin system beyond task integrations, surpassing 2,000 plugins and introducing extensible policy rules, log data stores, file preview renderers, queue implementations, and UI artifacts that let plugins provide rich in-platform visualizations. Enterprise policy rules replace flow-level pluginDefaults, requiring users to migrate affected flows before upgrading, while configurable log stores can move execution logs out of the main database and support optional historical migration. Plugin authors can now create custom previews for formats such as Parquet or Avro, supply Vue-based UI components through the Artifact SDK, and organize large task forms with property groups, while the new slim container image reduces the default installation size and can automatically fetch plugins during local open-source use. Kestra maintains intentional backward compatibility with most 1.x plugins despite core changes such as Java 25, although several core execution-management tasks have moved to API-based replacements in the Kestra plugin SDK. The release also adds numerous cloud, AI, infrastructure, security, storage, and task-runner integrations, reflecting Kestra’s broader focus on orchestrating private infrastructure and operational workflows as well as data pipelines.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Kubernetes 2 956 75 30 -73%
Secrets Management 2 451 99 43 -80%
Serverless 2 156 54 28 -80%
Vector Search 2 265 57 33 -89%
MCP 1 2,241 148 72 -74%
Observability 1 472 102 54 -85%
Real-time 1 649 155 80 -85%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.