At Daktela, we follow a structured development lifecycle to keep our platform stable, secure, and feature-rich. This approach allows us to consistently release new versions, ensuring customers always benefit from the latest improvements.
Transparency is at the core of our relationship with partners and customers. We want them to fully understand our philosophy and customer-centric approach, as we recognise that any potential issues can have a significant impact on business operations and partner relationships.
Our priority is to minimise disruptions while delivering a reliable, secure, and continuously evolving platform. If you have any questions, please don’t hesitate to reach out, because:
Customers matter
Development & Release Cycle
We operate on a major release cycle of approximately 3 to 4 months, allowing us to introduce new features consistently. This means we typically release 3 to 4 major versions per year.
- Major Versions are labelled according to the year and release number (e.g., 2025.1, 2025.2).
- Development is structured in two-week sprints, ensuring continuous progress.
- At the end of each cycle, our QA team performs extensive testing to ensure stability, security, and functionality before deployment.
In addition to major releases, we also provide minor updates and patches in the form of build versions (e.g., 300701), which include bug fixes and smaller feature enhancements.
For more details on version updates, visit our changelog:
🔗 Daktela Changelog
Accessing New Version Information
Information about new versions and their features is always available on the Daktela website under Resources & Documents:
🔗 Daktela Resources & Documents
Customer Version Management
To ensure a smooth upgrade process, we divide customers into batches based on their upgrade preferences and operational needs:
Production (Prod)
- The current production major version used by most customers.
- The goal is to gradually transition all customers here.
LTS (Long-Term Support)
- One major version behind Production.
- Intended for larger customers or those sensitive to changes that might occur between major versions.
Custom
For customers with specific operational needs (e.g., 24/7 availability), we provide a custom upgrade solution tailored to their business requirements.
Upgrade Scheduling & Execution
Upgrade Timing
- Prod and LTS upgrades take place Sunday to Thursday (scheduled one day earlier) and are executed 30 minutes after business hours defined by the customer during the onboarding process (can be updated at any time).
- Custom upgrades are scheduled on a specific day and executed at a specified time, which may vary for each instance.
Upgrade Notifications
- Customers receive an email notification about the upcoming upgrade only if they have subscribed to it.
- Subscription to upgrade notifications can be requested during the customer onboarding process or at any time via Support or Sales representatives.
Upgrade Cancellations
- If a scheduled automatic upgrade is cancelled, subscribed customers are notified that the upgrade will not take place.
Upgrade Failures & Rollback Mechanism
- If an upgrade fails to complete, the instance is automatically reverted to the snapshot taken before the upgrade (valid for Daktela cloud-based instances only).
- An internal ticket is raised for the appropriate Support team to analyze the logs and determine the root cause of failure.
- If necessary, the L1 – Partner Support Team may be involved to assist with further investigation.
Why Keeping Daktela Updated is Important
Regular upgrades are crucial for maintaining stability, security, and compatibility across the entire Daktela ecosystem and its integrations.
Key Benefits for Customers:
- Enhanced security – Protection against vulnerabilities.
- Improved stability – Fewer issues and better performance.
- New features & optimizations – Access to the latest tools and functionalities.
- Faster support & troubleshooting – Our support and development teams can respond more effectively to incidents when customers are on the latest production version.
Daktela API & Version Compatibility
Daktela’s API platform is an inseparable, crucial part of the system, and API changes may occur with new major versions.
Comparing API Versions & Checking Current Version
Customers using API integrations, API calls, or event-based automation should regularly check for changes to ensure continued compatibility and prevent potential disruptions.
- To quickly compare their current version with the latest available version, customers can use the version comparison tool:🔗 Compare API Versions
- The current version of a customer’s system can be found in the bottom right corner of the footer in their instance.
🔴 Customers are responsible for monitoring API changes and updating their integrations accordingly.
Daktela Cloud Infrastructure & Maintenance
Just as we regularly upgrade customer instances, we also continuously maintain and update our cloud infrastructure.
Our Core Infrastructure Team manages one of the largest private clouds in Central and Eastern Europe (CEE) to ensure high availability, performance, and security.
Keeping Partners or Customers Informed:
- We notify customers about planned infrastructure upgrades in advance to minimize disruption.
- For real-time updates on maintenance and service status, we provide a dedicated status page:🔗 Daktela Status Page
This page is not only for scheduled maintenance but also serves as a central hub for tracking any ongoing disruptions to Daktela services.
Key Features of the Daktela Status Page:
- Service Disruptions – Partners or customers can check real-time service status for different Dakela components.
- Planned Maintenance – Announcements of upcoming maintenance are posted here in advance.
- Historical Uptime Data – Each component’s uptime history is recorded for transparency.
To stay informed about maintenance and service status, partners or customers can subscribe to updates via the Daktela Status Page through various channels. Our aim is to minimise disruptions and ensure that every customer is prepared in advance for any planned changes.
Upgrade Automation & Scale
Our auto-upgrade system processes over 1,500 upgrades per month across more than 1,000 instances, eliminating the need for manual intervention and ensuring that every customer benefits from the latest, most stable version of Daktela.
