Topics

Less dependence on individual software providers

Rising licence costs, discontinued services or data-processing requirements may make a switch necessary. We assess which components can be replaced, self-hosted or substituted with custom software.

When provider dependence becomes a problem

A provider changes its pricing model and your calculations no longer work. A feature moves to another package. You want to process data in a specific environment. A service is discontinued. A necessary change is technically possible but unsupported by the chosen model.

Not every situation requires a complete replacement. What matters is the functionality you need and the freedom that is important to your business.

Three possible approaches

Make it replaceable. An interface or clearly defined component can enable switching services without rebuilding the entire application.

Run it on your own infrastructure. Suitable software and models deliver a function in your own environment. This provides different control over data flows, operations and development.

Replace a component. When the existing foundation no longer works, we rebuild the part needed. Compatibility with other systems is a key requirement.

We compare these approaches by required functionality, operational effort, cost and freedom to make future changes.

Two decisions from our work

Our own business logic for on-board chat. With Replira, we implemented the required chat functionality as independent software. Key interfaces remain aligned with existing clients. This lets us extend guest communication with workflows such as service chats and shape the technical foundation ourselves.

When keywords became broader image assessment. Our earlier image recognition supplied keywords from a cloud service. Today, assessment runs on our own hardware and considers more complex subjects. We can refine the criteria and control where images are processed.

Replira focuses on our own business logic and compatibility with guest services. Image assessment combines broader criteria with control over processing.

Dependence on us matters too

We document what we build and use technology others understand. We consider third-party operations and development in the architecture, documentation and agreed usage rights. The options should be clear in the specific proposal.

What this means for AI

Cost per operation is only part of the decision. The task, desired quality, processing location and ability to change models or assessment criteria matter just as much.

We assess which operating model fits and what responsibility it brings. A local model needs reliable operations; an external service needs suitable integration. The chosen approach should meet requirements and allow future changes.

The first step

Tell us which dependency concerns you and what you want to make possible. We will assess the available approaches, their prerequisites and implications.

Read more

03

Product

Replira

Cabin chats, personal QR invitations and quick conversations with the on-board service team.