Skip to content

Functional history

This page summarizes the major recent functional efforts that shaped the current TRINITY surface. It does not attempt to list every cosmetic adjustment. It documents the changes that materially affected the website and the services exposed through it.

Stronger customer account

The customer account evolved into a real follow-up surface:

  • Clearer order details
  • Better payment status distinctions
  • Subscription tracking
  • Easier access to invoices and references
  • Stronger consistency between order, payment and operations

Invoice overhaul

Invoicing was consolidated around cleaner and more credible PDFs:

  • TRINITY Visual identity
  • More readable invoices
  • Better handling of net, VAT and total amounts
  • Stronger legal wording and collection notices
  • Regeneration of older invoices

Unified payment experience

Payments were reworked around a common experience principle:

  • Collection of the right billing information first
  • Explicit payment return states
  • Consistent visual statuses
  • Resume path for pending payments
  • Support for several providers and methods

The exposed methods already include card payment, PayPal, bank transfer and Litecoin, depending on the order type.

Expanded support scope

TRINITY support was expanded to include:

  • Alpine Linux
  • Xen
  • UnyDesk
  • UnyPort

This changed both the public offer pages and the overall positioning of the site.

Chat evolution

The assistance chat moved from a modal to a dedicated page with history:

  • Persistent conversations
  • Better readability
  • Quick suggestions
  • History kept for non-authenticated visitors
  • Reconciliation when an account is created

The site also evolved on compliance:

  • Dedicated cookie policy
  • Expanded privacy policy
  • Stronger terms of use and sale
  • Custom consent panels

The goal was to make the platform more usable publicly without weak legal or UX blind spots.

VM, console and operations visibility

Finally, several efforts indirectly improved the public surface:

  • VM restart and recovery behavior
  • State visibility
  • Console robustness
  • Clearer link between orders and environments

TRINITY should now be understood as a complete operational platform where the website, account area, support, invoice and service access all belong to the same product surface.