Selected work.

Enterprise engagements delivered by Ionosof, directly or contracted through partners of the Atlassian ecosystem to serve the end client.

Clients across 11 countries in Europe, North America and Asia. 100% remote delivery record.

Engagements

  • Financial services · Switzerland

    Phase 2 · direct

    Period
    Jun 2023 – present
    Delivered via
    direct client of Ionosof, no agency
    active engagement

    Chosen directly. Then asked for a team.

    • The client selected Ionosof's architect out of a global consultancy's team on technical merit and engaged the company directly, then extended the relationship by contracting an Ionosof project manager to run the CMDB programme (Jan 2025 – May 2026), turning an unstructured backlog into direction, cost and integration planning aligned to DORA, the EU AI Act and NIST, with a planned exit once the programme was on rails.
    • Architected and governs the Atlassian Assets CMDB formally defined as the organisation's source of truth, enabling six data-centre migrations and the migration of the organisation's ITSM.
    • Architected the CMDB and asset-data solutions enabling DORA requirements to be fulfilled using CIs stored and governed in Assets.
    • Migrated Atlassian Server to Cloud with purpose-built scripting, including the conversion of a Comala Metadata dependency in Confluence to native Content Properties and Content Properties Report.
    • Established the architecture pattern where Jira Automation captures the event and triggers logic hosted in Azure Functions, with Terraform deploying cloud resources and Assets Discovery covering the data centres.
    • Evolved the platform into an Enterprise Asset Management capability, integrating LeanIX, OneTrust and Workday.

  • Financial services · Switzerland

    Phase 1 · via TCS

    Period
    Jun 2022 – May 2023
    Delivered via
    Ionosof engaged via TCS (Tata Consultancy Services) to serve the end client

    The organisation's first CMDB, designed from scratch.

    • The organisation had no CMDB. Ionosof designed one from scratch in Atlassian Assets, covering six data centres, part of the cloud estate, business applications and metadata such as users.
    • Architected the automated daily discovery of the infrastructure, feeding the CMDB for use inside Jira Service Management.
    • Integrated Entra ID, Intune, AWS and further tooling, with Assets Discovery covering on-premise infrastructure daily.
    • Delivered as senior consultant: a backlog with daily progress shown to the client, architecture and implementation versioned in Bitbucket.

  • Public sector · EU institution

    Period
    Mar 2024 – present
    Delivered via
    Ionosof engaged via Proximus to serve the end client
    active engagement

    Configuration architecture at 21M+ CI scale.

    • CMDB Architect embedded in the institution's CMDB squad, designing the configuration solutions the rest of the institution's teams consume, in an environment exceeding 21 million CIs.
    • Architects the CMDB standard the institution adopts (the base model teams install when they need their own capability) and governs how it is operated, how images are distributed and how a central inventory of those instances is maintained.
    • Works as a solution architect independent of the implementation medium: the design comes first, then the fitting means: plugin, Node-RED automation, Python or Docker images, handed to engineering squads to build. The institution's configuration system is NetBox.
    • The same configuration-architecture discipline Ionosof applies on Atlassian Assets, exercised at institutional scale.

  • Banking · Baltics

    Period
    Nov 2025 – present
    Delivered via
    direct client of Ionosof, no agency
    active engagement

    A bank's full ITSM inside 300 agent seats.

    • Designed and implemented an enterprise ITSM operating model serving 1,000+ users while limiting paid Jira Service Management agent licensing to 300 seats, avoiding the need for approximately 700 additional agent licences.
    • Migrated ITSM and Assets from ServiceNow to Atlassian Cloud on a two-project architecture: portals raise requests, incidents and problems in the Jira Service Management project, while automation copies each item into the Jira project where every agent resolves it without consuming an agent licence.
    • Designed the identity, team and domain model: groups governed in Entra ID, connected to Atlassian Teams, each Team linked to an Assets object representing services, areas and domains, a CMDB mapped to the organisation, not only to hardware.
    • Built the AWS ingestion that keeps the cloud CMDB alive: AWS Config records the inventory, Athena queries it, and a purpose-built Python application on Kubernetes (EKS), deployed by GitLab CI, credentials in AWS Secrets Manager, transforms and publishes it into Assets through the Atlassian import API. Declarative per-resource mapping makes it portable across environments; the daily cycle marks whatever disappeared as retired or inactive.
    • Served as the primary technical liaison between the bank and Atlassian for platform issues and strategic decisions.

  • Aviation · Ireland

    Period
    Sep 2025 – present
    Delivered via
    Ionosof engaged via Eficode to serve the end client
    active engagement

    ITSM and ITAM out of ServiceNow, then kept alive by discovery.

    • Migrated the company-wide ITSM out of ServiceNow (request types, forms and automation moved into Jira Service Management without users ever losing the ability to raise IT requests) and led the migration of the entire ITAM and CMDB estate into Atlassian Assets.
    • Established Atlassian Assets as a living CMDB across several schemas, populated by daily discovery, with discovered objects surfaced inside Jira Service Management forms so requests are raised against real, current configuration data.
    • Integrated Assets with Entra ID, Azure, Intune, AWS, Google Cloud Platform, CrowdStrike and further providers to keep asset and configuration data current.
    • Automated the service-to-asset cycle: equipment loans, how long a device is out, the emails that fire, when it comes back, and the dashboards around it.
    • Architected and migrated the three Jira Service Management projects underpinning the company-wide ITSM operation, then provided three months of full post-cutover hypercare to protect operational continuity in a 24/7 airline environment.

  • Consumer goods · global organisation

    Period
    Jan 2023 – Dec 2024
    Delivered via
    Ionosof engaged via SQLI to serve the end client

    Two years of the full Server-to-Cloud cycle.

    • Owned the complete platform cycle end to end: operating and developing on Atlassian Server, consolidating multiple Jira and Confluence Server instances into one, and executing the migration to Cloud with the ITSM rebuilt.
    • Administered the infrastructure, not only the application: the Jira and Confluence servers ran on Azure, with Ionosof responsible for executing cloud infrastructure changes, database work and platform upgrades.
    • Rebuilt what could not simply move (automation, SLAs and forms) and rewrote ScriptRunner behaviours and scripts in Python against Assets, because Server logic does not travel to Cloud unchanged.
    • Delivered 13 full integrations connecting JSM with enterprise development, knowledge and operational tooling.
    • Worked on the group's global Jira Service Management platform, supporting ITSM delivery within an organisation of approximately 271,000 employees worldwide, with weekly demos, retrospectives and sprint plannings safeguarding delivery quality.

  • Technology · international group

    Period
    Jun 2026 – Sep 2026
    Delivered via
    Contracted through the incumbent partner chain, serving entities of the same group after the acquisition
    currently in execution · three-month extension requested

    Platform consolidation after an acquisition.

    • Migrating the acquired company's projects out of FreshService into the group's Atlassian instance: automation, Assets, customer notifications, SLAs, forms and whatever else the move requires, including Python scripting.
    • Supporting the group's Atlassian platform as administrator: permissions, projects and governance of the group instance.
    • A further phase is planned once that migration completes: consolidating a second Atlassian Cloud instance into the group's.

Further engagements.

The same architecture discipline at a smaller scope, each one contracted, delivered and attributed the same way.

  • Betting & gaming

    United Kingdom & Ireland

    With 1,000 agent licences already in use and no budget for more, designed a model on Atlassian Data Center that lets an additional team serve the Jira Service Management portal from Jira Software without consuming agent licences, and connected an inert CMDB to joiner/mover/leaver and asset-retirement processes.

    Delivered via: Ionosof engaged via Clear Hub (now Eficode) to serve the end client

    Related capability

  • Energy

    Germany

    ITSM platform on Jira Service Management after a migration from ServiceNow: 20+ request types, 15 automation rules, a 3,000+ object CMDB in Assets and 10 Power Automate flows across Entra ID and Microsoft tooling, with ticket routing to third parties that consumes no Atlassian agent licence.

    Delivered via: Ionosof engaged via HAYS to serve the end client

    Related capability

  • Healthcare

    Denmark

    An organisation-wide Jira standardisation framework (one shared workflow made team-adaptable through configurable fields) plus a coexisting ServiceNow-to-Jira integration routing customer tickets to the right team with comments synchronised both ways.

    Delivered via: Ionosof engaged via Interex to serve the end client

    Related capability

  • Technology

    United Kingdom

    A ServiceNow-to-Jira Service Management transformation prompted by the client's acquisition: seven departmental ITSM projects architected inside a hard Cloud Standard automation ceiling, plus a Zendesk integration built with Google Apps Script.

    Delivered via: Ionosof engaged via Digitech to serve the end client

    Related capability

  • Recruitment

    Spain

    An ISO/IEC 27001 audit with no CMDB to show for it: designed and built the CMDB schema on Atlassian Assets, integrated SCCM, Entra ID and the corporate network, and deployed Assets Discovery across servers.

    Delivered via: direct client of Ionosof, no agency

    Related capability

  • Enterprise software

    Luxembourg

    Configuration data scattered across NetBox, CrowdStrike, AWS and physical servers consolidated into a single CMDB in Atlassian Assets, in a multi-instance Data Center environment, and the ownership model itself diagnosed, where servers were owned by IP range rather than by team.

    Delivered via: Ionosof engaged via European Recruitment to serve the end client

    Related capability

  • Personal care

    United States

    An organisation with no CMDB at all: the full capability stood up on the client's chosen platform, NetBox, and populated by discovery from Google Cloud Platform, AWS and CrowdStrike.

    Delivered via: direct client of Ionosof, no agency

    Related capability

  • Fintech

    Japan

    Engaged as the Atlassian expert to architect the target work platform on Jira Service Management and Jira, then migrate the information across from Monday.com and automate what followed.

    Delivered via: direct client of Ionosof, no agency

    Related capability

  • Food production · rail transport · semiconductors · consulting

    Spain · United Kingdom

    Tiered adoption programmes rather than one-off classes: a 25-hour advanced Jira programme distributed over six weeks for a public rail operator, a train-the-trainer model with a plenary assessment and a bounded support pool, advanced training combined with implementation advisory for a multi-organisation group, and ITSM consulting delivered across a consultancy's client portfolio.

    Delivered via: One engagement via Treinta Learning; the rest direct clients of Ionosof

    Related capability

Enterprises come back. So do their partners.

A financial services client engaged Ionosof again directly after a first phase through a global consultancy. A delivery platform re-engaged it in 2026, after an earlier engagement, for a larger assignment across the group. A betting and gaming client passed Ionosof on to its partner, which has kept contracting it, and an aviation engagement came from that. A bank extended a three-month contract until it offered a year.

Contact

One call, with the architect who would do the work.

No form, no inbox, no gatekeeper. Pick a time that suits you and we will talk about the platform you actually have.

  • Thirty minutes, video, with the principal architect. Not a discovery call run by someone else.
  • Bring the platform you are on today. The useful part of the conversation starts there.
  • A straight answer on whether this is work we should take, including when it is not.
Victor Parera on LinkedInIonosof on LinkedIn

European and United States time zones. There is no inbox and no phone number on this site on purpose: the calendar is the only channel that is watched.

Pick a time

30 MIN · VIDEO CALL

The calendar is hosted by Calendly. Loading it lets Calendly see your IP address and set its own cookies.

Or open the calendar on calendly.com