Product Roadmap

Year 2024

Key Features
Expected Release
Current Status

Q1, 2024

Beta Released - On Hold

Application Redesign: Layout, Fonts, and Colours Updated

Q2 & Q3, 2024

Workflows Optimizations & Improvements

Q2 & Q3, 2024

Infrastructure Stability Improvements

Q3, 2024

Improving Analytics and Reporting

Q4, 2024

In Progress

Flows to Workflows Migration

No Deadline - Ongoing

In Progress

Security Improvements

No Deadline - Ongoing

In Progress

Q4, 2024

Started

Workflows AI

Q4, 2024

Yet to Start

User Onboarding Features

Q2, 2024

Moved to next year

User/Duration-based Logs Retention

Q2, 2024

Moved to next year

Year 2023

Key Features
Expected Release
Current Status

Q1, 2023

Q1, 2023

Q2, 2023

Q4, 2023

Q4, 2023

On Hold

Improve Logs Page Performance using ElasticSearch

The log and detailed log pages are now serving with Elasticsearch and the performance has been improved. We will continue to monitor the performance to keep the log pages faster.

Simplifying Integrations

With our goal to improve the customer experience, we are working on simplifying the steps across all the pages. As a first step, we merged systems and API into one screen in the release v3.4.1

As a second step, in release v3.4.3, we merged credentials into the same screen, to group all system-related entities in one place and to manage it easily. We have received positive feedback from the customers and developers on this design change.

In phase 2, release v3.4.4, we redesigned the project screens, account/project settings and improved accounts switching approach.

As a final step, we have introduced workflows which revamped the structure and design of the flows and merged with pipes to simplify the integration. This was a major change and we released the beta version on October 18, 2023.

Phase 3 - workflows is completed in multiple stages in releases from v3.4.5 to v4.0.0.

Region-based Synchronizations

The pipe synchronizations are now executed in the same region with the help of multiple worker pools. As a next step, we plan to run the synchronizations in the respective regions of the customers.

Failure Record Reprocessing

Currently, we allow the customers to reprocess in some particular systems if the synchronization fails. We plan to expand to all the systems and improvise the reprocessing algorithm. This experimentation is put on hold.

Last updated