How many people does a business application take? The redb ecosystem and a short answer The redb project, an open .NET ecosystem, provides data storage, an integration engine, a module host and a login server so developers can define entities as plain C# classes and integrations as route definitions rather than hand-writing schema, migrations and plumbing. In a benchmark on an employee model spread across 41 tables, redb Pro on PostgreSQL averaged 189 ms across 98 EF Core-compatible tasks versus 703 ms for EF Core, though the project notes EF Core wins on flat data and many small single-object saves. The ecosystem offers 30 transport packages and 53 address schemes for connecting external systems. Half of a team writes not the business but everything around it. How redb takes that half off your hands, and why with it an analyst with AI can build an integration. How many people on your team write the wrapping around the business? The broker connection, the database migration, the zero-downtime deployment, the dashboard, the login. It has to be done, it costs money, and it is the same everywhere. You pay for that work again in every project, and now you pay for it in tokens too: the AI writes the same plumbing, gets it wrong and rewrites it on your bill. redb has already written that part. It is an open .NET ecosystem: data storage, an integration engine, a host for modules and a login server. This article is about how many people and how much AI work are left when everything around the business is already there. Three rules. Data is a class. You write a plain C class, put an attribute on it, and redb stores it in PostgreSQL, SQL Server or SQLite: RedbScheme "employee" public class EmployeeProps { public string FirstName { get; set; } = ""; public decimal Salary { get; set; } public string ? Skills { get; set; } } A process is a route. For example: pick up XML files from a folder, check them against a schema and send them to Kafka. A good file moves to done , a bad one to error , where a person can look at it: