Latest Release Notes
Key themes in this release 2.0.051 include broader support for advanced compliance and pooling scenarios, reduced dependency on external inputs through manual maintenance tool, improved traceability and usability in transaction and financial workflows, foundational delivery of a more capable report builder, better observability, automation, and environment readiness and targeted bug fixes in allocation, risk, timeline, and date-handling logic
Release label: 2.0.0.51 (05/09/2026)
Scope: 123 tasks and fixes
Primary impact areas: FuelEU, Custom Report Builder, EU ETS and Financial Workflows, Trading Algorithms and Deal Logic, Risk & Analytics, Infrastructure, Monitoring & Platform Operations.
Executive Summary
Release 2.0.0.51 centers on three broad outcomes: expansion of regulatory and compliance workflows, major progress in internal reporting and analytics capabilities, and a set of infrastructure and usability improvements intended to make the platform more stable, observable, and efficient to operate.
The largest body of work appears to fall into compliance-heavy operational modules, especially around vessel, contract, pool, transaction, and calculation workflows. In parallel, the release establishes important building blocks for a richer custom reporting experience, including new charting, lookup logic, semantic linking between datasets, and report persistence. Supporting these product-facing changes is a layer of operational work in monitoring, deployment preparation, and workflow automation.
Functional Summary by Module
1. Fuel EU
A substantial portion of the release is focused on extending compliance functionality for operational and regulatory use cases. The work suggests a shift from basic record handling toward more complete lifecycle support across vessels, contracts, pool participation, and compliance balances.
What was added or improved
Pool management enhancements: Users can identify a pool leader, distinguish between assigned and unassigned vessels, and manage surplus handling in a more structured way.
Surplus carry-forward logic: The release introduces logic to bank excess surplus from a pool onto a selected vessel for use in the next compliance cycle.
Manual maintenance capabilities: Users can manually create and edit employments and time-charter-related contract records directly in the application.
Automatic right-year calculation: Certain compliance-related year values are now calculated automatically from underlying contract dates.
Transaction workflow support: A dedicated transactions area was added for compliance trading, including validation and column management.
Multi-currency storage handling: Trading-related values are stored consistently in USD while still accounting for exchange-rate-driven source inputs.
Permission model expansion: Access control was aligned with existing module patterns, supporting separate view, edit, create, and delete permissions.
Refresh and navigation quality-of-life improvements: Refresh actions were added across sub-tabs to help users reconcile screen state with recent changes.
Public API coverage: Additional endpoints were introduced to retrieve compliance-related contract and employment data, including support for more custom fields.
Why it matters
These enhancements reduce manual workaround effort, improve consistency between operational records and compliance calculations, and make the module more capable for organizations managing varied vessel and contract scenarios. The introduction of explicit transaction handling and more structured permissions also suggests the module is maturing from specialist usage toward broader controlled adoption.
2. Custom Report Builder Development
This release contains important groundwork and feature expansion for a reporting solution intended to give users more control over data exploration and presentation. The scope includes both user-facing capabilities and underlying architectural investment.
What was added or improved
New visual types: Support was introduced for line charts, KPI cards, and matrix-style reporting with hierarchical nesting.
Column and value controls: Users can select and clear groups of fields more efficiently and apply value aggregations such as sum, average, and count.
Lookup functionality: Distinct datasets can now be linked, enabling richer reporting across previously separate data domains.
Semantic relationships: Relations between data structures allow cross-filtering behavior between visuals, making dashboards more interactive and analytically useful.
Column-type detection: The system can infer data types automatically, improving configuration speed and reducing setup errors.
Calculated columns: Users can create derived values using an expression-building workflow.
Save and rename support: Reports can be persisted and managed more like reusable assets than one-off views.
Refresh-all behavior: A consolidated refresh action improves the user workflow when multiple visuals or datasets are involved.
Error handling improvements: Better behavior was introduced for API-based data sources when data retrieval or transformation does not go as expected.
Engine migration: Reporting infrastructure was moved to DuckDB, indicating a focus on faster in-memory or embedded analytical processing.
Delivery and environment setup: Container and permission work was completed to support deployment and execution in controlled environments.
Why it matters
This work significantly strengthens the platform’s self-service analytics direction. The combined introduction of relationships, calculations, matrix views, and persistence points to a transition from static tabular reporting toward interactive business intelligence capabilities embedded in the product.
3. EU ETS and Financial Workflow Improvements
The release includes a set of refinements to financial and emissions-related workflows, especially where operational activity must be translated into invoice, exposure, or compliance-relevant views.
What was added or improved
Breakpoint visibility in deals: Users can expand and inspect how volumes are distributed over specific periods.
Invoice number automation: Invoice numbering was automated using structured operational inputs, reducing manual numbering effort and inconsistency.
Billing period auto-update: Billing periods can now be refreshed from the most recent relevant timestamps in physical trade activity.
Auto-allocation of existing allowances: A new automated action helps link volume and exposure more efficiently.
Advanced filtering: Users gained stronger filtering support around commence and complete dates as well as custom additional fields in key financial and net position views.
Why it matters
These changes reduce friction in daily financial operations, improve visibility into period-based allocations, and help ensure downstream invoices and exposure records reflect source activity more accurately. The release also appears to improve auditability by reducing opaque manual steps.
4. Trading Algorithms and Deal Logic
Several items in the release address algorithmic handling of time-charter and physical deal records. These changes are important because they improve correctness at the business-rule layer rather than only at the user interface layer.
What was added or improved
Unified time-charter algorithm: A single workflow was developed to handle multiple deal variants such as inbound, outbound, indexed, and owned-asset scenarios.
Overlap prevention: Logic was added to stop invalid voyage overlaps.
Hire-period adjustment: Hire timing now aligns more tightly with delivery and redelivery dates.
Cross-linking field in physical deals: A dedicated code field was added to improve linkage between physical deals and related trading instruments or datasets.
Peg date bug fixes: Timeline adjustment issues were corrected so that modifying end dates does not unintentionally create gaps.
Why it matters
Algorithm-level fixes tend to have outsized impact because they influence consistency across many records and workflows. The work here reduces the risk of broken timelines, invalid overlap states, and incorrect connections between related trading objects.
5. Risk, Analytics, and Snapshot Processing
The release also addresses reporting and analytics accuracy, especially in risk calculations and data extraction workflows.
What was added or improved
VaR notification workflow: Automated email notifications were added for successful completion or failure of risk calculations.
Risk calculation bug fixes: Cases where certain contracts produced zero-risk outcomes for historical draw dates were corrected.
Snapshot filtering: Snapshot request filters were expanded to reduce data volume and improve export performance for downstream analytical use.
Why it matters
These changes improve trust in analytical outputs and reduce operational uncertainty when long-running or failure-prone calculations are involved. Performance-sensitive filtering also makes the system more practical for large data extractions.
6. Infrastructure, Monitoring, and Platform Operations
Not all work in this label is user-facing. A meaningful portion strengthens the operational base required to support feature growth reliably.
What was added or improved
Monitoring rollout: Grafana dashboards and Prometheus/Loki alerting were established or expanded to observe system health and baseline performance.
Session policy adjustment: Default logout timing was extended from one hour to three hours.
User onboarding option: Welcome email sending was made optional during user creation.
Environment preparation: Containers and virtual machines were prepared for additional deployment environments.
Legacy monitoring cleanup: Older monitoring agents were removed from virtual machines.
Why it matters
Operational maturity work like this improves resilience, speeds troubleshooting, and reduces the maintenance burden of mixed legacy and modern tooling. It also enables smoother scaling of newly introduced product capabilities.