Romain Bourbon Studio
RBS / ACCESSIBILITY

Reading comfort

These settings are saved on this device.

Theme
Text size
Motion
Contrast

RBS LAB

Build products to test the principles before recommending them.

RBS Lab is the studio’s product field. It creates complete applications, confronts architectural choices with reality and turns lessons learned into reusable building blocks for business and entertainment.

RBS / CONTEXT

The Lab is not separate from service work. It continuously tests model choices, UX, deployment and maintenance decisions on real products.

AMBITION

Different products, one architecture laboratory.

01

Business

Create applications that make AI understandable, local and useful in everyday workflows.

02

Creation

Explore storytelling, music, media and interfaces to learn how to hide complexity without hiding how the system works.

03

Reuse

Design each product as a testbed for components, methods and architectures that can be transferred elsewhere.

GOLDEN RULES

Power is not the objective. Controlled efficiency is.

The Lab tests a technical doctrine: do more with less, keep components replaceable and avoid making a simple feature dependent on unnecessarily heavy architecture.

01

Local-first

Run locally what can reasonably be run locally and keep architectures able to work without a permanent external-cloud dependency.

02

Open source by default

Prefer open models, libraries and components when they meet the need and preserve control of the system.

03

Token frugality

Reduce unnecessary calls, limit context, choose the right model for each task and measure efficiency before adding power.

04

Efficiency before prestige

A small well-integrated model can be more useful than an oversized general model. The criterion is the work completed.

05

Human sovereignty

Important decisions, validations, corrections and exceptions remain identifiable and attributable to a person.

06

Replaceable architecture

Avoid irreversible dependencies: models, providers and components should evolve without rebuilding the whole product.

07

Accessible UX

Technical complexity may disappear from the interface, but not the understanding of what the system does.

08

Useful traceability

Keep the traces needed to explain an action, diagnose an error and improve the product.

PRODUCTS

Three current product testbeds.

OMAOKI · PRODUCTTEMP
Learning · governance · autonomy

Omaoki®

Understand and work with AI.

An environment designed to support AI use from understanding the need to project governance. Desktop and Administrator.

Open product website
SOMYUREN · PRODUCTTEMP
Local-first · models · workflows

Somyuren®

Turn media into usable information.

A local application for transcription, translation and audio/video processing, built around guided workflows and models running on the machine.

Open product website
RONDIENZA · CREATIVE LABTEMP
Interaction · audio · experience

Rondienza®

Explore interactive systems differently.

A creative laboratory around music, storytelling and user experience where technical complexity should disappear behind play and discovery.

Open product website

LEARNING LOOP

A product should produce more than its own code.

Every difficulty becomes reusable knowledge: an architecture decision, deployment procedure, test method, UX rule, performance measure or documentation model.

The Lab therefore also turns real product experience into methods that can be used in RBS engagements.

LET’S TALK ABOUT THE PROCESS

Looking to turn an idea into a controllable product?

Describe the need