Cloud & On-Premises

Three paths. One platform.

talenttrends runs in three clearly defined hosting variants — as SaaS with talessio, in your own cloud subscription or entirely in your data centre. The choice determines data residency, responsibilities and time-to-value. The platform stays the same.

talenttrends logo horizontal light gray

Hosting models

You choose, we deliv­er accordingly

Which path makes sense for you depends on data clas­si­fi­ca­tion, cloud strat­e­gy and oper­a­tions matu­ri­ty. We’ll help you make the right deci­sion — and, if in doubt, also help you switch between the models.

SaaS with talessio

We oper­ate the plat­form, you use it. Fastest time-to-value.

Hosting regions
  • Azure Ger­many West Cen­tral (Frank­furt) — stan­dard for DACH enterprise
  • STACKIT (Schwarz Dig­its) — sov­er­eign cloud vari­ant, for pub­lic sec­tor and very sen­si­tive industries
Who operates what?

You have a sin­gle con­trac­tu­al part­ner: talessio. We oper­ate infra­struc­ture, plat­form, data­bas­es, back­ups, updates and mon­i­tor­ing. You have user access via web UI and API.

Strengths

Fastest roll­out (weeks instead of months), no oper­a­tions effort of your own, guar­an­teed host­ing com­pli­ance path (ISO 27001 /​ BSI C5 for STACKIT, SOC 2 for Azure).

Suitable for

Most DACH enter­prise cus­tomers who want to process HR data in the EU and have no cloud strat­e­gy of their own for this workload.

In your cloud

You pro­vide the cloud sub­scrip­tion, we deliv­er the platform.

Hosting options
  • Microsoft Azure
  • Ama­zon Web Services
  • Google Cloud Platform
  • Open­Stack
Who operates what?

You con­trol the cloud sub­scrip­tion, the net­work topol­o­gy and the con­nec­tion to your source sys­tems. We deliv­er the plat­form as a con­tain­er, help with the set­up and pro­vide sup­port in ongo­ing oper­a­tions — either as a man­aged ser­vice or as a con­sult­ing service.

Strengths

Full con­trol over net­work, data res­i­den­cy and encryp­tion. Inte­gra­tion into your exist­ing cloud gov­er­nance, your iden­ti­ty man­age­ment, your cost allocation.

Suitable for

Cus­tomers with an estab­lished cloud strat­e­gy who want to process HR data in the same cloud envi­ron­ment as their oth­er workloads.

On-Premises

The plat­form runs in your data cen­tre, entire­ly under your control.

Prerequisites
  • Con­tain­er run­time (Dock­er, Kuber­netes, OpenShift)
  • Data­base: Microsoft SQL Serv­er or PostgreSQL
  • Egress con­nec­tion to Cor­ner­stone and, if applic­a­ble, to the LLM end­point (for Ask)
Who operates what?

You oper­ate every­thing — infra­struc­ture, plat­form, data­bas­es. We deliv­er con­tain­er images, update pack­ages, instruc­tions and sup­port. Option­al­ly, we take over parts of oper­a­tions under a ded­i­cat­ed man­aged ser­vice contract.

Strengths

Max­i­mum con­trol, air-gap capa­ble, no cloud depen­den­cy, no exter­nal data pro­cess­ing. For reg­u­lat­ed indus­tries, defence, very restric­tive secu­ri­ty policies.

Suitable for

Cus­tomers who must or want to avoid cloud work­loads for reg­u­la­to­ry, organ­i­sa­tion­al or strate­gic reasons.

Decision support

Which path suits your context?

A quick overview of the key cri­te­ria. In the work­shop, we’ll go through every point with you specif­i­cal­ly for your situation.

Criterion
SaaS with talessio
In your cloud
On-Premises
Data residency

EU (DE, Frankfurt)

You choose

With you

Time-to-production

~2 – 3 weeks

~4 – 8 weeks

After the set­up phase

Operations

talessio

You (with support)

You (with support)

Compliance path

ISO 27001 /​ BSI C5 (STACKIT) or SOC 2 (Azure)

Com­pli­ance of your cloud

Entire­ly in your hands

Contractual partner

One part­ner (talessio)

Two (talessio + cloud provider)

One part­ner (talessio), your own infrastructure

Scalability

High, by design

High

Depend­ing on your infrastructure

Update frequency

Con­tin­u­ous, by us

Sched­uled, jointly

You decide

Suitability for

Most DACH enterprises

Cloud-first strat­e­gy

Reg­u­lat­ed indus­tries, very sen­si­tive data

Who does what

Clear bound­aries, clear responsibilities

Once the host­ing choice has been made, a respon­si­bil­i­ty matrix gov­erns who oper­ates which lay­er. The fol­low­ing overview is a start­ing point — the spe­cif­ic split is defined in the con­tract per customer.

Layer
SaaS with talessio
In your cloud
On-Premises
Infrastructure (compute, network, storage)

talessio

You

You

Operating system /​ container runtime

talessio

You (with sup­port from talessio)

You

Database administration

talessio

You (with sup­port from talessio)

You

Application (talenttrends platform)

talessio

talessio

You (with sup­port from talessio)

Configuration

You or talessio

You or talessio

You or talessio

Backup creation

talessio

You

You

Backup and restore tests

talessio

You

You

Security patches for the application

talessio

talessio

You (with update packages)

Monitoring

talessio

You and talessio

You

AI Infrastructure

AI com­po­nents have their own host­ing path

tal­ent­trends Ask and oth­er LLM-pow­ered fea­tures use lan­guage mod­els whose host­ing can be con­fig­ured inde­pen­dent­ly of the plat­form. You can run the plat­form and the LLM in dif­fer­ent clouds, regions or with dif­fer­ent providers.

AWS Bedrock (Frankfurt, eu-central‑1)

Stan­dard for EU data res­i­den­cy with Claude mod­els. No train­ing access to your data, con­trac­tu­al­ly excluded.

Azure AI Foundry (Sweden Central)

If you have an estab­lished Azure rela­tion­ship and want to keep the work­load there. EU host­ing, EU data processing.

Your own model (BYOL)

If you run your own LLM — with a hyper­scaler of your choice or on-premis­es (e.g. Lla­ma, Mis­tral). We adapt the integration.

The LLM host­ing path is sep­a­rate from the plat­form host­ing path. You can, for exam­ple, run the plat­form on STACKIT and use Bedrock Frank­furt for LLM infer­ence. Details on the AI data path — what the LLM sees, what it does not see, how your data is pro­tect­ed — can be found under Secu­ri­ty & Com­pli­ance.

Operation

What we promise, we set out in the contract

Ser­vice Lev­el Agree­ments (SLAs) and scal­ing char­ac­ter­is­tics depend on the cho­sen host­ing mod­el and the agreed sup­port tiers. The exact com­mit­ments are defined indi­vid­u­al­ly per cus­tomer — the fol­low­ing overview shows what we’re talk­ing about.

Availability SLA

Defined per host­ing mod­el and cus­tomer in the con­tract. Depend­ing on region, pre­mi­um options and high-avail­abil­i­ty configuration.

Response-time SLA

Tiered by sever­i­ty (Crit­i­cal, High, Nor­mal, Low) and sup­port tier. Spe­cif­ic response times and pre­mi­um sup­port options are defined contractually.

Scaling characteristics

Sev­er­al mil­lion records per ten­ant with­out an archi­tec­ture change. Hor­i­zon­tal scal­ing across sev­er­al pods for high load or high avail­abil­i­ty across zones.

Recovery time objectives

RTO and RPO are defined per cus­tomer in the con­tract — depend­ing on your risk assess­ment, your host­ing mod­el and the under­ly­ing infrastructure.

20230323 135850 092 talessio scaled

Ready for modern HR?

Talk about the host­ing that suits you

60 min­utes, struc­tured. We’ll go through the deci­sion matrix with you in con­crete terms — based on your data clas­si­fi­ca­tion, your cloud strat­e­gy and your oper­a­tions real­i­ty. With a rec­om­men­da­tion and next steps.

Arrange a call

hello@​talessio.​com