FR Client area Tell us what you need Contact
contact@sooatek.com Client area FR Français
Tell us what you need

Case studies

The client’s name is published only with written approval. Otherwise, the case is anonymized. Each case follows the same format: context, constraint, solution, outcome.

  1. 01Context
  2. 02Constraint
  3. 03Solution
  4. 04Outcome
Illustration: a street corner as a scale model, five shops with lit windows, lined by a glowing thread.
FIG. 01 — A street of shop windows, linked by the thread · Illustration, not a client screenshot

§ 01 / The cases

The case studies

Case 01 · Federation system

Client case · anonymized

Migration to microservices, adaptive two-factor authentication and passkeys.

Context
The information system of a national sports federation.
Constraint
Five connected applications to evolve together: management, mobile, members’ portal, competitions, payment.
Solution
Migration to microservices, adaptive two-factor authentication, passkeys.
Outcome
Audit findings handled according to the plan; adaptive two-factor authentication in production.

Stack

  • Microservices
  • Adaptive 2FA
  • Passkeys

Case 02 · AI · Voice

Sooatek project · public

A Malagasy speech recognition model, published with its measurements.

Context
Malagasy is a low-resource language: little annotated data, and models measured mostly on long recordings.
Constraint
Stay reliable on the short utterances a voice assistant receives, measured on speakers never heard in training.
Solution
A fine-tuned w2v-BERT 2.0 model, a language model, punctuation restoration and a version that runs on a CPU.
Outcome
12.7% word error rate on 11,625 unseen short utterances (with a language model; 14.3% without), against 21.5% for our previous model, a Whisper medium fine-tuned on the same data.

Stack

  • w2v-BERT 2.0
  • Language model
  • CPU version

Case 03 · Mobile

Client case · anonymized

iOS and Android apps published with in-app purchases.

Context
iOS and Android apps to be published on both stores, with in-app purchases.
Constraint
Strict publishing rules, specific to each store.
Solution
In-app purchases on iOS and Android, compliance fixes after a rejected submission.
Outcome
Apps published on the App Store and Google Play, in-app purchases live.

Stack

  • iOS
  • Android
  • In-app purchases

Each case links to its full case study. No figure without a source.

A similar project? Let’s talk.

A 30-minute scoping call to understand your context and constraints, then a written reply.

Tell us what you need contact@sooatek.com

A 30-minute call? Suggest two time slots in your message