Why we don’t merge our products into one app

It is tempting, when one group runs several products, to fold them into a single “super app” with one login, one database and one codebase. We deliberately do not.

Different users, different promises

A Shopify merchant using MerchNivo, a school administrator using EduRelia and a consumer reading their chart on ZodiVela have nothing in common as users. Each product makes a different promise about what it does with their data. A single app would blur those promises.

Different lifecycles

A marketplace ships on a different rhythm than a school platform. A consumer app experiments constantly; an education product must be conservative. Separate repositories and release cycles let each company move at the right speed without breaking another.

A company must be able to stand alone

Any company in the group could one day raise capital, bring in a partner or be sold. That is only realistic if its code, data and infrastructure can be separated cleanly. We design for that from day one.

What we do share

• Brand-neutral UI primitives and design tokens.
• Authentication wrappers, validation, logging and security headers.
• An AI gateway client for model access, budgets and monitoring.
• Deployment, DNS and access-management standards.

What we never share

• Product user databases and customer data.
• Prompts, private knowledge bases and business rules.
• Brand voice and marketing audiences.

The line is simple: share the plumbing, not the people.

Published by Oryvelon · About the group · Our companies