Product Roadmap
Tracking releases, features, and our long-term trajectory toward local-first database autonomy.
Tauri Local Desktop Runner v1.2
Introducing desktop visual monitoring interfaces, SQL playground terminal widgets, and automatic background CSV/JSON exports for external business analysts.
200+ Embedded Marketplace APIs
Expanding standard extractors to support regional Middle East (Noon, Salla), APAC (Lazada, Shopee), and specialized ERP connectors (SAP, NetSuite).
DPDPA Enforcement Hardening
One-click encryption-at-rest key cycling, secure local audit trail logging, and automatic metadata labeling to satisfy Indian state digital inspectors.
Our Development Philosophy
Every feature on the Sensyze roadmap is guided by a single principle: give users maximum control over their data infrastructure with minimum operational complexity. We deliberately avoid building features that create vendor lock-in or require proprietary cloud services to function. Instead, we invest in open standards, portable storage formats, and deployment patterns that work across bare metal, virtual machines, Docker containers, and Kubernetes clusters. Our release cadence balances stability with innovation, shipping incremental improvements every two weeks while reserving larger architectural changes for quarterly milestone releases. We believe that transparency in our development process builds trust with the enterprises that depend on our platform for mission-critical data pipelines.
Open-Source Commitment
Sensyze is built on an open-source core, and we are committed to keeping it that way. Our source code is publicly available, and we accept contributions from the community through a structured pull request process. We follow the Red Hat model: the platform itself is free and open, while revenue comes from support subscriptions, compliance packs, and marketplace templates. This structure ensures that our incentives remain aligned with our users. We will never artificially restrict features behind proprietary licence gates that force upgrades. The open-source core includes the full visual pipeline builder, all standard connectors, the code editor, and the local deployment toolkit. Enterprise-specific features like compliance packs and priority support are clearly separated as paid add-ons.
Community Input and Feature Prioritisation
Our roadmap is not created in isolation. We actively solicit input from our user community through Discord discussions, GitHub issue tracking, quarterly roadmap surveys, and direct conversations with enterprise clients. Feature requests are tagged, categorised, and ranked by impact and feasibility. High-demand features are promoted to the public roadmap so the community can track progress and provide feedback during development. We publish detailed release notes with every milestone, explaining the reasoning behind prioritisation decisions and acknowledging community members who contributed ideas or code. Our goal is to build the data infrastructure that our users actually need, not the features that are easiest to market.