Skip to content

Research becomesreal software.

Scroll ↓
SCENE 03 · THE BUILD CURRENT

Six ways we ship.

This isthe nexus.

Where research becomes product.

SCENE 05 · THE PRODUCTS

Two productsin production.

Research thread · conferences

CMS

Conference lifecycle in one governed system — proposal to peer review to publication. Roles, enforcement, and an audit trail on every privileged action.

Development thread · clinics

DrChamber

Chamber and practice software for doctors and clinics — live, and built for how a clinic day actually runs.

The whole story, in one map.

// 13 threads · 1 nexus · 2 products
Data ScienceAINLPImage ProcessingComputer VisionIoTEmbedded SystemsSoftware DevWeb DevMobile DevIoT Device DevEmbedded EngLogo DesignCMSconferencesDrChamberclinics
Every thread above is real work — the map is the company.Explore both products →

Publications

The work behind the products.

Technical writing from the team — the thinking behind the products.

Working with us

How an engagement runs.

How it starts
A conversation, then a written scope. No proposals dressed as sales decks.
How long
You get the real number before you commit — not the optimistic one.
Who owns it
You do. Code, data, and infrastructure live in your accounts.
After launch
We stay. Support and iteration terms are agreed before we start, not after.

FAQ

Straight answers.

Including the ones about money. Privacy policy covers the data questions in full.

Are you a studio or a product company?

Both, deliberately. We build for clients, and we run our own products — CMS and DrChamber. The products are how we prove the studio works.

What does a project cost?

Scope drives it. You'll have an honest range from the first conversation, not the fifth.

How long until something is live?

It depends on how much governance the system carries — roles, permissions, audit. We'll say the real number upfront, and we'd rather lose the project than misstate it.

Who owns the code?

You do. Repositories, infrastructure, and data live in your accounts.

What happens after launch?

We stay. Support and iteration terms are agreed before we start, not after.

Do you work with regulated or sensitive data?

Yes. DrChamber is built for clinical records in production, and our privacy policy covers how we treat data across the site and both products.

SCENE 06 · THE FOURTEENTH THREAD

Bring us thehard problem.

You’re the fourteenth thread. Tell us what you’re trying to build — we’ll say honestly whether it’s a fit, within two business days.

What are you trying to do, and what makes it hard? Specific beats polished.

Used to reply to you. Nothing else — there is no list.