Journal · Logbook
Building in public: what Ryze shows and how to read its figures
Building in public means showing how a company progresses while it is being built, instead of waiting until it is finished. On katiaryze.com it takes three forms: live products presented as case studies, dated activity figures, and this journal. This site publishes neither revenue nor a number of customers: this article explains what is shown, where it comes from, and what it does not prove.
Before you read: Katia Ryze is an AI-generated persona. She is not a real person. This article is written by the Ryze team, not by the character, and only uses information already displayed on this site.
What is building in public?
It is a way of working: you regularly publish what you are making, what is moving forward and what is still missing. Readers can follow, compare one date with another and form their own opinion.
The method is only worth something if what is published can be checked. A figure without a date or a source teaches nothing. That is why we always separate three things: what is online and anyone can open, what is collected automatically, and what is simply declared by the team.
What katiaryze.com publishes today
Here is what the site displays, and where to read it. The figures below are those of the site as of 30 September 2026.
| What is published | What the site says | Where to read it |
|---|---|---|
| The products | Seven products since May 2026, each with its case study: the problem, what was built, why it works. | Portfolio |
| Overall activity | 3,558 commits, 562 merged pull requests and 1,889 deployments, as of 30 September 2026. | Profile |
| Markers per product | Start date, number of commits and merged pull requests, tools used. | Each case study |
| The internal tool | RyzeOS: 10 databases, 20 deployed projects, 15 code repositories, with a reading every morning. | RyzeOS case study |
| The nature of the character | Katia Ryze is an AI-generated persona, and it is written on every page. | Header and footer |
Where do these figures come from?
The site says so under the figures on the profile: they are self-reported, or pulled automatically every morning. The RyzeOS case study adds that automatic daily readings (projects, repositories, databases) are published on katiaryze.com, and that public figures are dated.
- Collected automatically. The figure is read every morning by the internal tool, with no manual step.
- Declared. The figure is entered by the team, with its date. It is worth what a declaration is worth.
When you read a figure on this site, look at its date. A figure from 30 September describes 30 September, not today.
What these figures do not say
A commit is a recorded change in the code. A merged pull request is an approved batch of changes. A deployment is a release to production. These three figures measure work done, not a commercial result.
- They do not say how much the company earns. This site does not publish revenue.
- They do not say how many customers use the products. The site only states, for Ryze ProBat, that a heating installer in France is the first customer in production.
- They say nothing about quality: many commits do not make good software. To judge, open the products.
We prefer to write this limit down rather than let a large number pass for proof of success.
Who builds, and where does AI fit in?
The software is built by the Ryze team. It relies on RyzeOS, which the site describes as the internal AI brain of the ecosystem: skills, a memory, databases and agents that build the products, collect the figures and manage the leads of each vertical. RyzeOS is not for sale: it is an internal tool.
AI agents execute, real people decide and answer for the company. Katia Ryze presents the ecosystem: she is a character, not an executive. We explain that choice in Creating an AI persona for a brand or a personal brand.
Our rule for publishing in public
- Date every figure. Without a date, a figure cannot be compared with anything.
- Say where it comes from. Collected automatically or declared: the reader must be able to tell the difference.
- Show the product. A link to a live site is better than a description.
- Write down what is missing. What is not published, what still needs improving.
- Do not let a character testify. An AI persona presents; it does not tell a lived success story. The details are in Openly AI influencer: why and how to disclose it.
Frequently asked questions
What does "build in public" mean?
Building in public means showing how a company progresses while it is being built: what is done, what is moving, what is missing. The method is only worth something if what is published is dated and can be checked.
Which figures does katiaryze.com publish?
Activity figures: seven products since May 2026 and, as of 30 September 2026, 3,558 commits, 562 merged pull requests and 1,889 deployments. Each case study also gives its own markers.
Are these figures verified?
The site states that they are declared by the team or collected automatically every morning by RyzeOS, the internal tool. They are dated. They are not figures audited by a third party.
Does Ryze publish its revenue?
No. This site publishes neither revenue nor a number of customers. The figures displayed measure work done, not a commercial result.
Is the company run by AI agents?
AI agents build the products, collect the figures and manage the leads inside RyzeOS, the internal tool. Decisions and responsibility remain with real people in the Ryze team.
Read also: the portfolio, product by product.
The Ryze ecosystem
Four universes, one way in.
Digitise your company, move to AI, start a business or earn money with Ryze: the home page points you to the right universe.
Sources
- Activity figures and the note on their origin: Profile page
- Case studies and markers per product: Portfolio
- RyzeOS, daily readings and origin of the figures: RyzeOS case study
This article contains no information that is not already displayed on this site. Last updated: 7 October 2026.